Of course, after than, whatever you’ve just plugged into it, will most likely not work
502 Bad Gateway
504 Gateway Timeout
X-Forwarded-For
The solution is probably somewhere deep in the bowels of whatever you’re trying to make work
It will look obvious once you’ve figured out, that’s why it wasn’t mentioned next to the bunch of instruction you pasted into your console to install the thing
Just another day walking in the forest of papercuts
I just cp one of the config files in /etc/nginx/site-available when I need to create a new one
Yep, just pick the one closest to what you want, eg static site, reverse proxy, etc. Then remove the ssl stuff and get certbot to regenerate it with your new certificate. (Don’t forgot ipv6 if you have it enabled on your system)
That is only better if you actually know what you are doing. I don’t do it often, and never remember how I should handle the io if nginx is in a docker and the services is in another. So this let’s me try things quickly