this post was submitted on 09 Nov 2023
6 points (87.5% liked)

Selfhosted

37442 readers
43 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
6
Nginx Proxy Manager on TrueNAS SCALE Gateway Time-out (lemmy.dbzer0.com)
submitted 7 months ago* (last edited 7 months ago) by Tywele@lemmy.dbzer0.com to c/selfhosted@lemmy.world
13 comments fedilink hide all child comments
 

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.

all 14 comments
sorted by: hot top controversial new old
[–] goatsarah@thegoatery.dyndns.org 1 points 7 months ago (1 children)

@Tywele as in, you get the NPM config site?

On my docker install, that’s on port 81. My router forwards ports 80 and 443 to NPM. You probably shouldn’t be able to get to the config site through a firewall.

[–] Tywele@lemmy.dbzer0.com 1 points 7 months ago (1 children)

For me the config site is configured to port 10582 and I'm trying to access it locally.

[–] PipedLinkBot@feddit.rocks 1 points 7 months ago

Here is an alternative Piped link(s):

https://www.piped.video/watch?v=qlcVx-k-02E

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source; check me out at GitHub.

[–] Oisteink@feddit.nl 1 points 7 months ago (2 children)

Is this your internal domain name of the nas box, or are you trying to reach your gw’s ip though NAT?

If you do a lookup of the domain name you try to enter - does that give the same IP as you use when successfully connect?

[–] Tywele@lemmy.dbzer0.com 1 points 7 months ago (1 children)

I also setup a proxy host to connect to the TrueNas WebUI just to try it out and that is working perfectly fine.

[–] Oisteink@feddit.nl 1 points 7 months ago (1 children)

I’m not very familiar with nginx, I use haproxy for my reverse proxy or load balancing needs.

Do the 504 get logged on the proxy? From your screen grabs it seems that nginx have a working connection to the upstream server.

Maybe that website needs special settings that nginx can’t handle or is not set up for?

[–] Tywele@lemmy.dbzer0.com 1 points 7 months ago

I figured it out and added the solution to the OP.

[–] Tywele@lemmy.dbzer0.com 1 points 7 months ago (1 children)

When I do a nslookup it returns the entered IP address from the proxy host.

And that's also the same IP I use when I successfully connect as you can see in my 2nd screenshot in the OP.

[–] Oisteink@feddit.nl 1 points 7 months ago (1 children)

So this domain resolves to the server you are proxying, not your proxy?

[–] Tywele@lemmy.dbzer0.com 1 points 7 months ago (1 children)

I don't quite follow? The domain resolves to IP address I want it to resolve. My TrueNAS server has the IP 192.168.178.167 and on it I have NPM installed as an app. The admin page of NPM is accessible via the same IP on port 10582. Syncthing is also installed and accessible via the same IP address and port 8384. I have both of them configured in NPM so that theoretically subdomain.mydomain.com should resolve correctly and that I can access their respective admin pages. For Syncthing and any other app this is working except for the admin page of NPM itself. I'm trying to figure out why that is.

[–] Oisteink@feddit.nl 1 points 7 months ago (1 children)

Right - so the upstream server is a docker container on the same machine, and you proxy the connection to the servers up on the port forwarded through the magic docker iptables thingy. It might be here that you get the connection closed - maybe check logs on that. Don’t recall if it’s logged by default or you have to set it up

There’s also the possibility of the web service not being proxy friendly

[–] Tywele@lemmy.dbzer0.com 1 points 7 months ago

I figured it out and added the solution to the OP

[–] Decronym@lemmy.decronym.xyz 1 points 7 months ago* (last edited 7 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
IP Internet Protocol
NAT Network Address Translation
nginx Popular HTTP server

4 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.

[Thread #271 for this sub, first seen 10th Nov 2023, 10:45] [FAQ] [Full list] [Contact] [Source code]