Skip to main content

Hello all, 

 

Odd one that I’m hoping people here can help me troubleshoot. I’ve got some services (Jellyfin, Nextcloud, etc) running on a home server behind a reverse proxy. Normally, I access these servers at rservice].vmydomain].com. Currently, on my LAN, this is not working. If I try to access the services outside of my LAN at the reverse proxy domain, they are working, and if I access the services directly by IP and port, they are working on my LAN. However, within my LAN, they are not accessible at the domains. Since the services work and the reverse proxy works outside my network, it seems I’ve got an issue in the network itself. I’m using a SURFboard G34 which I’ve only had for a few weeks. I have looked in the router WebUI and nothing seems amiss, but I really don’t know what I’m looking for. Would appreciate any suggestions. Thanks!

In this case we would suggest you to try accessing server without Reverse proxy. If you are using Static IP try Port Forwarding the port numbers. If you are using the Dynamic IP then port Triggering by following the article mentioned on the below link

http://arris.force.com/consumers/articles/General_FAQs/G34-G36-Port-Forwarding-Setup

http://arris.force.com/consumers/articles/General_FAQs/G34-G36-Port-Triggering-Setup

Hello, 

Thanks for the reply. I currently am using port forwarding, forwarding ports 80 and 443 to my home server, which is then accessed by a DuckDNS address allowing leaving it with a dynamic IP. To be clear, accessing services at the domain name on the LAN was working before, it just stopped working abruptly. 

Please try on different LAN ports to access internet or try using different LAN cable.

Hey RebelLion, I found this while dealing with the same sort of issues with the same gateway. I’m not positive, but I think what we’re having issues with is called NAT loopback.

I also wanted to let you know that I found a workaround by using pi-hole. There is a local DNS option that will let you point service.domain.com to the local IP of your server. If everything on your local network is served DNS from the pi-hole, then they’ll get your local IP instead of your WAN IP at the DNS level, thus circumventing the issue.

Reply


Terms & ConditionsCookie settings