I’m new to Nginx Proxy Manager (NPM) and I’m struggling to make my Navidrome server accessible from outside my home network. I’ve got everything set up on a Raspberry Pi 4 running the 64-bit OS. My router is an Arris DG3450A with the necessary port forwarding in place.
Here’s what I’ve done so far:
Set up Navidrome on port 4533
Installed NPM and created a proxy host
Configured a DDNS with DuckDNS pointing to my public IP
Both Navidrome and NPM are on the same Raspberry Pi
The proxy works fine when I’m on my local network. But when I try to access it from outside, the site just times out. If I enter my public IP directly, I see the default NPM page saying no proxy is set up.
I’m wondering if the issue might be because Navidrome is in a separate Docker container. I tried putting them on the same Docker network, but it didn’t help.
Has anyone encountered this before? Any tips on troubleshooting or fixing this issue would be greatly appreciated. Thanks!
I’ve encountered similar issues when setting up external access for self-hosted services. One thing to check is whether your ISP is blocking incoming connections on port 80/443. Some providers do this for residential connections. Try changing the external port in NPM to something non-standard like 8080 or 8443 and update your port forwarding accordingly.
Another potential issue could be your Docker network configuration. Ensure that NPM can reach Navidrome’s internal IP. You might need to use the --network host option when running NPM’s container to allow it to see other containers as if they were on the host network.
Lastly, double-check your NPM proxy host settings. Make sure the scheme, hostname, and port for the destination are correct. Sometimes a small typo can cause connection issues.
If none of these solve the problem, examining NPM’s logs might provide more insight into what’s going wrong during external access attempts.
hey bro, i had similar trouble. make sure ur firewall isn’t blocking the ports. also, try using navidrome’s IP instead of container name in NPM. check if ur ISP allows incoming connections too. sometimes they block em. if nothin works, maybe try a VPN to test. good luck man!
I’ve been through this exact headache with Navidrome and NPM. Here’s what finally worked for me:
Check your Docker network. Make sure NPM and Navidrome are on the same network. I had to create a custom bridge network and explicitly attach both containers to it.
In my NPM proxy host config, I used Navidrome’s container name as the hostname instead of an IP. This solved some weird DNS issues I was having.
Also, double-check your SSL settings in NPM. I initially had issues because my cert wasn’t valid for external access.
One last thing - try accessing your setup using cellular data instead of another wifi network. Sometimes ISPs or network configs can interfere with testing external access.
If all else fails, temporarily expose Navidrome directly (without NPM) just to rule out any Navidrome-specific issues. Good luck!