[[Support] Nginx Proxy Manager (NPM) Official]

After many issues with not being able to reach my external domains from inside my local network, I found your NPM container, which allows me to set port 443 and Host.

This solves my issue, and Nginx Reverse Proxy is working both externally and internally.

 

My idea was to set only port 443 for NPM and use port 80 for Unraid WebUI. This way I can reach my Unraid WebUI with "NAS.lan" and everything else with it's external domain/subdomain.

 

But even if I set NPM to 443 and 8080, and let Unraid WebUI use port 80. It won't start NPM:

bind() to 0.0.0.0:80 failed (98: Address already in use)

It seems like it will only use port 80 whatever I set?

 

Is this a bug?

[Dynamix WireGuard VPN]

On 10/25/2019 at 11:01 AM, bonienl said:

I did (a lot of) testing and made line traces to monitor what is happening exactly.

 

1. If you have docker containers with a custom IP address assigned to br0 (the management interface of Unraid) then containers will never be reachable thru WG. The reason: the tunnel terminates on the host, but docker doesn't allow communication between host (Unraid) and containers. The solution: create a separate interface or VLAN for docker containers

 

2. When the setting "Local gateway uses NAT" is set to YES, it will cause Unraid to use its own LAN address as source for communication to other devices on the LAN network. I am going to change the name of this setting, because it has nothing to do with the local gateway (router). With NAT enabled on the Unraid server, all devices respond directly to Unraid (i.e. not via the default gateway). In my testing, however, the NAT setting causes issues when talking to containers with custom IP addresses. These reply wrongly and consequently are not reachable, but any other device in the LAN works correctly, just not containers.

 

3. When the setting "Local gateway uses NAT" is set to NO, it will cause Unraid to use the WG tunnel address as source for communication. In this case the default gateway (your router) needs a static route added to point tunnel addresses back to the Unraid server. With this set up both docker containers and other devices are reachable.

 

4. I have issues when using UPnP on my router (Ubiquiti) and ended up making manual forwarding port rules instead. User mistake, UPnP is working correctly with Ubiquiti.

 

 

I have an Unraid server setup with services like WireGuard VPN, Home Assistant, Nginx Proxy Manager. The setup is as follows: WireGuard is running as "Remote tunneled access" with DNS server (192.168.1.1) which is my router. Home Assistant is running as a Docker on the same server. Nginx Proxy Manager is running as a Docker (Host) on the same server, here I have Nginx Reverse Proxy for Home Assistant (home.example.com).

I can without any issues reach Home Assistant when I am in my local network and when I use an external network. It is reachable from anywhere, as I want it to be.

But as soon as I connect to my WireGuard VPN tunnel it is no longer possible to reach the domain (home.example.com). It just times out.

From what I read in your post the issue is similar to what you describe. But I run my Home Assistant docker as Host, not Bridge. How come I have the same issue?

Is there any solution to this?

[Cannot reach my external domains when connected to WireGuard VPN?]

Any ideas how to solve this?

[Cannot reach my external domains when connected to WireGuard VPN?]

I have an Unraid server setup with services like WireGuard VPN, Home Assistant, Nginx Proxy Manager. The setup is as follows: WireGuard is running as "Remote tunneled access" with DNS server (192.168.1.1) which is my router. Home Assistant is running as a Docker on the same server. Nginx Proxy Manager is running as a Docker (Host) on the same server, here I have Nginx Reverse Proxy for Home Assistant (home.example.com).

I can without any issues reach Home Assistant when I am in my local network and when I use an external network. It is reachable from anywhere, as I want it to be.

But as soon as I connect to my WireGuard VPN tunnel it is no longer possible to reach the domain (home.example.com). It just times out.

Is there any way to solve this issue?

[[Support] Nginx Proxy Manager (NPM) Official]

14 hours ago, mgutt said:

Some possible reasons:

1. Your domain does not resolve to the public IP. Instead it uses the local IP, which bypasses your router port forwarding (which means 443 hits nothing as NPM listens only on 4443)

2. You router das not support hairpinning / nat loopback. Such a router does not support accessing a domain with it's public IP.

3. You have enabled IPv6 (does not allow Port forwarding)

Sorry about my previous post. I just realised that the issue is different from what I thought. There is no issue when using my local network to connect to my external domains (home.example.com). The issue is when I am connected via WireGuard (that's why I thought it did not work locally). If I am connected via WireGuard to my Unraid server, which also runs Home Assistant and Nginx Proxy Manager, I cannot reach my external domains (home.example.com) as long as I am connected. Everything works great if I am not connected to WireGuard.

WireGuard is configured as Remote Tunneled Access.

How do I solve this?

[[Support] Nginx Proxy Manager (NPM) Official]

Just setup Nginx Proxy Manager on Unraid, have been using Nginx Reverse Proxy previously on my OpenMediaVault server without any issues. I have the docker setup to use port 8080 and 4443, these ports are port forwarded in the router from 80-8080 and 443-4443. It works great to access things like Home Assistant from my external domain.

For some reason I cannot use the external domain (home.example.com) to connect to services like Home Assistant when I am in my local network (same as the Unraid server).

It will not connect. As soon as I leave my network it works great.

 

This never happened when I used Nginx Reverse Proxy on my OpenMediaVault server, so I don't understand why I have issues when using Unraid for this?