this post was submitted on 09 Nov 2023
7 points (88.9% liked)

Selfhosted

39980 readers
603 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
 

Edit: SOLUTION: I had to use 127.0.0.1 and port 81 for the proxy host that points to the NPM admin page

I'm trying to follow this tutorial from Wolfgang's Channel: https://www.youtube.com/watch?v=qlcVx-k-02E but I'm using Nginx Proxy Manager (NPM) on TrueNAS Scale.

I managed to get the SSL certificate working (the challenge is successful) but after setting up the proxy host for NPM I'm unable to reach the WebUI of NPM like he does in the video after setting that up.

This is the setting for my proxy host.

But when trying to access the WebUI through the domain name all I get is 504 Gateway Time-out. Does anyone know what I did wrong?

Nginx Proxy Manager is also properly setup to use ports 80/443. So when I access the IP address without any port I get sent to the default site of NPM.

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

@Tywele How are you trying to access it locally? Are you using its fully qualified domain name and does that resolve to your WAN address? If so, you MAY need to locally override the DNS entry with its LAN address. You need to use the FQDN though.

I had this issue when using a VLAN for this server (as in the server I’m writing this on). “Thegoatery.dyndns.org” resolves to my ip address, the router goes, “oh, that’s me”, but won’t route it because the source and destination are on different VLANs and it has no rules to route via the WAN address.

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

I've setup 2 additional proxy hosts now one for syncthing and one for the web UI of TrueNAS to see if they are working and they are working perfectly fine. It seems like only the NPM admin page itself is not working and giving me a gateway time-out.