You are correct, I should have warned people to use these instructions at their own risk.
Indeed. It is a long way from what you should be doing.
Mine are ephemeral test systems, they are tossed with each new release, not upgraded.
Should be stated, as above.
I see others here saying that they have enabled letsencrypt but are not telling how, like me they are probably tired of the browser warnings and wanting usernames and passwords saved.
If you check there is a new panel. As we have always said, if it doesn't function as intended, open a bug. Same mantra for years. That's how we work and we can then advise how to fix or whatever. The panel is a new feature and IIRC still needs work. And this is Beta and should be expected.
Regrettably here the answers will get picked up by unsuspecting users (or Heaven forbid AI) and postulated as the correct answer.
Personally, I have always gone to forums first to seek answers, feeling they are easier to search than searching a bug reporting database.
But we have always said - if it doesn't work as expected, open a bug. This is particularly true currently as it allows us to track and fix issues. It is how we work.
Search for the letsencrypt ones - if yours is not listed, open a new one please. It does not need your fix. Just what has, or has not happened.
On top of which a lot of the templating you have done should already be there, but as we don't know what version you are running we can't tell. smeserver-certificates-11.0-7.el8.sme.noarch should have most of it.
https://src.koozali.org/smeserver/smeserver-certificatesRocket chat might be great for you developers, but its published knowledge and insights are hidden away from average users like me. So, I post here, where my questions and limited knowledge are shared with the world.
There is no 'them and us'. We are all Koozali SME users first and foremost. I am no dev. I hack a bit. /ends.
So Rocket.Chat is a messaging system that anyone can join and use. It is just a very easy way for people to communicate and fix issues, often in real time.
There is no magic sauce or secret squirrel stuff there. There are ordinary users and devs (the couple that there actually are).
As it was my own test system originally I kept it locked to prevent spammers. That has continued due to limited licence counts etc. If people want an account they can just ask me. There is no fee or qualification required. But you need will need an account to view information.
It is MUCH easier to discuss this sort of thing there and users can be guided rather than making elementary mistakes.
Again, I have said this on countless posts.
We are grateful for testing, but rather than posting workarounds for problems that may not actually even exist, please follow established procedures or you, us, and many others will be in a right mess.
And then people will be asking us to fix the hack of yours we know nothing about that they read about 'somewhere' and then haven't undone........
Thanks.
6 Replies
2800 Views