Issues accessing internal server services after Hub 5 upgrade

Hi there,

I recently upgraded from a Hub 3 to a Hub 5 due to ongoing network issues with the Hub 3, which was dropping in and out throughout the day, making websites difficult to load. My connections were checked, refurbished, and cleaned to ensure there were no underlying issues.

After the Hub 5 was installed, I manually updated my server’s static IPs to match the new subnet, since the Hub 5 doesn’t allow changing the subnet. Since doing this, I’ve been unable to access any of my server services via their internal proxy. I initially thought it was a software issue and tried an alternative proxy solution, but the problem persisted. As a result, several services cannot communicate with each other, as their URLs appear down.

To rule out my server being at fault, I tested with another inexpensive travel router. When plugging my server into it, everything worked immediately with no configuration changes required, confirming that the issue is caused by the Hub 5.

I also performed troubleshooting with nslookup and found the following:

On my network, queries to my server fail with:

communication error to 8.8.8.8#53: timed out no servers could be reached

This is unusual because the Hub 3 never caused issues like this. When I enable a VPN with local network access, nslookup works on the first attempt, and all reverse proxies function correctly.

Despite this, I still cannot access services via their URLs on the internal network, and services cannot communicate with each other using these URLs.

Screenshot of nslookup results: top shows queries over normal Wi-Fi (failing), bottom shows queries over Wi-Fi with VPN + local network access (succeeding).

Has anyone else experienced similar issues after upgrading to a Hub 5? Could there be a Hub 5 setting or restriction causing this internal DNS/proxy problem? Any advice would be greatly appreciated.

Thanks in advance!