Forum Discussion

calVM's avatar
calVM
Joining in
6 days ago

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!

Hub5
internal
Proxy servers VPNs
Server

5 Replies

  • Client62's avatar
    Client62
    Alessandro Volta
    6 days ago

    Hub 5 has LAN range of 192.168.0.xxx , the Gateway is 192.168.0.1

    If your raspberry device  is not connecting suspect a static network configuration issue, 
    make sure the IP is on the 192.168.0.xxx  range, the gateway is 192.168.0.1,
    and valid DNS IPs are present.

    Google DNS does work ... 

    nslookup hp.com 8.8.8.8
    Server:  dns.google
    Address:  8.8.8.8

    Non-authoritative answer:
    Name:    hp.com
    Addresses:  18.239.50.109
              18.239.50.112
              18.239.50.6
              18.239.50.45

    • calVM's avatar
      calVM
      Joining in
      6 days ago

      I do have network access on the machine, and I can reach external sites fine. However, I am unable to access my internal reverse proxy at 192.168.0.3 unless I enable a VPN and turn on local network access.

      I want to use the domain that points to the reverse proxy to access my services internally, but it seems that the Hub 5 is blocking connections to that internal IP when using the domain directly. The IP and gateway settings are correct (192.168.0.174 and 192.168.0.1), and DNS resolution works externally, so it looks like an internal routing or NAT issue on the Hub 5.

      • Steven_L's avatar
        Steven_L
        Icon for Forum Team rankForum Team
        4 days ago

        Hello calVM,

        Welcome to the Community, and thanks for taking the time to post here on the forums. I’m sorry to hear of the issues that you’re experiencing with your connection. 

        Have you been able to get your issues resolved since you last posted or do you require further assistance? 

        Kind Regards,

        Steven_L

  • legacy1's avatar
    legacy1
    Alessandro Volta
    6 days ago

    Have I experienced similar issues after upgrading to a Hub 5? no why? I use hub 5 in modem mode

    NAT loopback is no supported by VM and you can only get that to work with modem mode only and own router.

  • Roger_Gooner's avatar
    Roger_Gooner
    Alessandro Volta
    4 days ago

    If you set a static IP address for the reverse proxy it should be outside the DHCP reservation range of 192.168.0.10 to 192.168.0,245 (unless you've changed it), otherwise check the DHCP Reserved list to verify the proxy is there with the 192.168.0.174 address. You should be able to ping it as well - is this successful?