Skip Navigation

Nginx finally clicked for me

I have been trying to wrap my head around Nginx proxy manager by reading guides. I tried using the linuxserver docker-compose to set it up and I couldn't figure it out. Finally I checked out the office Nginx image...

I don't know why I didn't try that one first. The linuxserver images are usually easier to set up, but not this one.

All of this was for Overseerr/Plex. Here was the progression:
"Tell me what you want and I'll get it."

"Whenever you're on my WiFi, go to INTERNAL.IP:5055 and you can request whatever."

"Go to PUBLIC.IP:5055 and you can request stuff."

"Go to lastname.duckdns.org and you can request stuff."

And now... I'm still on DuckDNS but it's managed by Nginx and it's through HTTPS!

What should I do next?

4
4 comments
  • I moved to nginx from Apache for Lemmy. Overall, I like it, I think. Though I do cheat and have ChatGPT generate the config for me and I tweak it from there.

    I could do Apache config by hand, but I'm nowhere near adjusted to nginx config yet.

    • Nginx is fast and light. Apache is granular AF. You can set up more intense security with Apache, but if you're not trying to do really crazy shit, nginx is a huge simple win. Port proxy is like 3 lines.

  • This helped me quite a bit when i started diving into more advanced capabilities.

    https://github.com/nginx/njs-examples