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
{{ message }}
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.
Oof. The same old problem where when the certificate gets updated, the signalling server doesn't reload the cert file. I've restarted the server, but this should be fixed. Updating issue name.
nirbheek
changed the title
Certificate expired today
signalling server doesn't reload cert file when it's updated, requires a manual restart
Nov 8, 2018
Well, I tried the suggestion in https://stackoverflow.com/a/43875481 to re-instantiate the asyncio server, but it didn't really work (ssl connections started just failing after the reload). Going to try and investigate that a bit more and if it doesn't work, will just implement a restart + inotify behind an option.
Most production deployments I know of put the signalling server behind an nginx proxy anyway.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
for https://webrtc.nirbheek.in:8443
The text was updated successfully, but these errors were encountered: