2
submitted 1 year ago by [email protected] to c/[email protected]

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?

top 3 comments
sorted by: hot top controversial new old
[-] [email protected] 1 points 1 year ago

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

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

[-] [email protected] 1 points 1 year ago

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.

[-] [email protected] 1 points 1 year ago

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.

load more comments
view more: next ›
this post was submitted on 29 Jun 2023
2 points (62.5% liked)

Selfhosted

39251 readers
254 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS