Struggling with NPM - Can't reach services
Clearly in over my head, but determined to get this working. I'm trying to troubleshoot my NGINX Proxy Manager installation, which I moved from a Docker container on Raspberry Pi to my Firewalla Gold SE, following this guide: https://help.firewalla.com/hc/en-us/community/posts/1500000874242-NGINX-Proxy-Manager-Docker-Setup-on-FWG
I'm running a Plex server on an Ubuntu 22.04 machine, and running some *arrs and testing Jellyfin on my Pi.
I got NPM installed and am able to reach the admin UI and create Proxy Hosts. I can reach my services using my internal IP addresses (192.168.x.x:7878, 192.168.x.y:8096, etc).
I set up some DDNS with DuckDNS and no-ip, and got an SSL cert from Lets Encrypt for the DuckDNS address. Both machines are shown as online and publicly available.
When I enter the myplex.duckdns.org or no-ip address, I get "this site can't be reached." I wanted to see if the Firewalla was blocking, but in the logs I just see the IP addresses being blocked, but they aren't identified as the duckdns or no-ip services. I also unblocked one of them, but I still wasn't able to reach my services.
I'm unsure where to troubleshoot next. As I said, I got this all up and running on the Pi, so I'm guessing I need to look toward the FWG, but stuck where to look next. If NPM were running on another machine, I'd have thought it was a port forwarding issue, but I dont know how that would work for services running on the router.
Any advice is greatly appreciated.
Please sign in to leave a comment.
Comments
0 comments