4 ms·
I was expecting this to be posted by mholt. :) I use Caddy in my production systems with one exception, websockets. Yes it works, yes it is easier to configure
by therein 5y ago
I was expecting this to be posted by mholt. :)
I use Caddy in my production systems with one exception, websockets. Yes it works, yes it is easier to configure compared to nginx. But there is this one bug that I can't really put my finger on that is hard to debug and create an issue for.
Under high load, it seems there are messages that are dropped and then the connection gets lost. It even affects the origin host because it keeps the connections alive and they keep piling up. Killing Caddy brings the upstream service back to life.
With nginx I am not having these issues and the websockets are more stable. It is just harder to set up and needs multiple moving pieces for autossl instead of it being taken care of by Caddy.
- mholt 5y agoCan you open an issue with more details? I don't think this has been reported before. So that's why it hasn't been fixed yet. But we'd like to look into it.
- therein 5y agoWill do, thanks. It has just been this phantom issue that I haven't had a chance to compile enough convincing evidence to open an issue with.