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

you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 1 year ago* (3 children)

Nginx config is pretty quick to cobble together in a text editor, personally I'd just bin off whatever this tool is and save the hassle.

There's always the risk of frontend tools like this being abandoned, so you might as well just learn the actual config format for the thing you're configuring

  • source
  • hideshow 3 child comments
  • [–] 3 points 1 year ago* (2 children)

    I just cp one of the config files in /etc/nginx/site-available when I need to create a new one

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago (1 child)

    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)

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    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

  • source
  • parent