this post was submitted on 28 Aug 2023
52 points (98.1% liked)

Selfhosted

40173 readers
650 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
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
52
Noob NGINX / self-host question (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
22 comments fedilink hide all child comments
 

Hi all. Noob question/s here. I want to be able to access my Immich server (docker) externally and maybe set up some others (e.g. Mealio). My understanding is that I need (should) use NGINX reverse proxy for this. My questions are:

  1. Do I need to set up NGINX on a VPS (or similar cloud based server) to send the queries to my home box?

  2. Do I need to purchase a domain (randomblahblah.xyz) to use as the main access route from outside my house?

Thanks a lot.

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

I'm still relatively new to NGINX Proxy Manager myself, but I'll give your questions a shot. It doesn't matter how (or where) you host your proxy instance, what matters is that the requests can get to it so that it can forward them to the correct resources. So simple answer to question one is no you can host locally.

If you host it locally you need to make sure that you forward requests that come into your network on to the proxy to be routed correctly. This is where port forwarding comes into play. You'll need to set your router to take any requests that come in on port 80 or 443 (HTTP and HTTPS) and send those to your proxy.

As for question two do you need to purchase a domain. You can use a free domain name or you can pay for one that part doesn't matter. The domain isn't a technical requirement until you want to start hardening your instances with SSL. To get a cert you'll need a domain. But if you set up your port forwarding and a proxy you could send a request to some_subdomain.123.456.789.123:80 (your external IP) and the proxy server will take thar request and translate it to the local server mapped to some_subdomain.

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

Thanks, I'm going to try the port forwarding part. That seems like the simplest step. NPM looks very useful though.