You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not necessarily an issue, but at least uncertainties regarding setup.
The SMP Docker Container does crash when there's no SSL certificate files in /etc/opt/simplex/.
But if i got that right, this will only be used for Status page, so it would be better not to require these files to be present, so people can point their reverse proxy to it, or disable the status page if not needed.
As for Port 5223, the only way is to open a TCP forwarding stream on that Port in nginx, correct? Is that considered save, only using the self generated certs?
The text was updated successfully, but these errors were encountered:
We will update the doc, and possibly the container. This is not going to be used only for server information page - in the near future all invitation links and addresses will be short, and would use server hostname instead of simplex.chat. So without this page supported by the server this link won't open in the browser, and it would create friction for the new users to connect. That's the reason we made it opt out rather than opt in - to amend deployment process/docs as necessary based on this feedback.
Not necessarily an issue, but at least uncertainties regarding setup.
The SMP Docker Container does crash when there's no SSL certificate files in /etc/opt/simplex/.
But if i got that right, this will only be used for Status page, so it would be better not to require these files to be present, so people can point their reverse proxy to it, or disable the status page if not needed.
As for Port 5223, the only way is to open a TCP forwarding stream on that Port in nginx, correct? Is that considered save, only using the self generated certs?
The text was updated successfully, but these errors were encountered: