Its likely a known issue with nginx + docker.
When a docker container crashes it gets a new IP address, but nginx has cached the upstream hostname resolution as the old IP, so it thinks the upstream is gone.
Or it could be a million other issues, that’s just one that I run into a lot. ¯\_(ツ)_/¯
I also get “502 Bad Gateway” every now and then. Today it happened with https://lemmy.ml/post/330390. Nothing is printed to the Firefox console (except for Quirks Mode because of missing <!DOCTYPE html> of course). Reloading the page fixes the issue.
Its likely a known issue with nginx + docker.
When a docker container crashes it gets a new IP address, but nginx has cached the upstream hostname resolution as the old IP, so it thinks the upstream is gone.
Or it could be a million other issues, that’s just one that I run into a lot. ¯\_(ツ)_/¯
I havent noticed such an error in a long time. Can you give more details, like any errors from browser console?
I also get “502 Bad Gateway” every now and then. Today it happened with https://lemmy.ml/post/330390. Nothing is printed to the Firefox console (except for Quirks Mode because of missing
<!DOCTYPE html>of course). Reloading the page fixes the issue.Will do next time :)