#1216 "prosodyctl reload" doesn't clear cache or revalidate connections on cert change
I'm using prosody 0.10.2-1~stretch1 with latest Conversations 2.2.9 clients and a cert signed domain by letsencrypt.
Some weeks ago, I created new letsencrypt certs and used "prosodyctl reload" afterwards.
This worked for clients to be able to reconnect to prosody and continue chatting.
However, the cache was faulty, because when I wanted to send an old GIF again, the cache seemed to hit and tried to reuse the old, but now obsolete cert/connection resulting in TLS connection errors because of the cert timeout.
"prosodyctl restart" helped to solve this issue. I think this cleans the cache uses the new cert from now on.
I think "prosodyctl reload" should also clean the cache from old objects from obsolete TLS connections.
Perhaps prosody should compare prev and next certs: if they're the same clear cache, otherwise keep it (or something like that).
Hello, thanks for the report.
Are you trying to say that HTTPS certificates are not reloaded?
This is known, currently only certificates for XMPP/STARTTLS are reloaded on `prosodyctl reload`.
As a work-around, mod_http can be reloaded (must be a global reload) using either the telnet console or ad-hoc commands.
> Are you trying to say that HTTPS certificates are not reloaded?
No, I'm not.
If I replace certificates and don't tell prosody anything, the certs expire and clients aren't able to connect and post anything afterwards.
Current settings are:
c2s_require_encryption = true
s2s_require_encryption = true
s2s_secure_auth = true
Thus I used "prosody reload" after a cert change in order to reload https certificates.
This works as far as clients were able to reconnect to the server and post stuff again.
The cache, however, doesn't seem to be cleared on "reload": If clients post cached items, the old cert or connection parameter was used (since posting limit was 512KiB and the file was 496KiB, it *could* be that mod_http was used).
It seems that connection parameters in conjunction with the old certificate still seem to be upheld after "reload" - what shouldn't be.