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!83Views0likes5CommentsPhantom Ethernet Connection
Bit of a head scratcher here. I've been trying to port-forward for my desktop's minecraft server via its ethernet connection, but while I've managed to set up DHCP for my computer & port forward to it, the (3.0) hub continually insists that there are no devices connected via ethernet... Given that I can turn off my computer's wifi connection and still access the internet via the ethernet adapter, and ipconfig reports I'm happily bound to 192.168.0.112 (as I defined in DHCP settings) I'm somewhat stumped. Ordinarily this would be a minor curiosity and little more since I am -in fact- still connected to the net, but people connecting to the minecraft server via the external ip seem to have massively strangled connections. They can find the server and connect, but then experience phenomena demonstrative of an unworkably sketchy connection (connection time-outs, infinite loading). Are these things connected? Is there some setting I've missed somewhere that might be choking my connections? I've got firewall rules set inbound & outbound for both TCP & UDP on the relevant port... So what's going on? Why does my ethernet connection seem intent on pretending it doesn't exist?449Views0likes2CommentsUnable to access ntlworld emails this week
Hello, I've been unable to access my ntlworld inbox since yesterday afternoon. When I log into the Virgin Media Mail via the website I get a 'Forbidden' message. I mainly access my emails via Outlook on Windows 11 - do I need to do anything or is the VM server down? Thanks!981Views0likes4CommentsHigh latency in valorant to London server
Hi, I've reached out a few times to both Riot and Virgin 150 support numbers and not had much luck. I get passed back and forth. I'm trying to resolve ping issues im getting. Currently I ping 40 to London, 30 to Frankfurt and then 40 again to Paris when trying to play VALORANT despite living in the UK. I'm trying to see what I can do or ask or who I can ask to try bring better routing so that my London server UK ping is way down. I play with a wired ethernet directly into the router. I've done a full reboot via the pin as suggested. I have also tried doing everything from Riots side they recommended, which was diagnostic tools and DNS flushing. Desperately need some help and advice as its tied to my income slightly and want to be playing on the lowest ping possible for it1.1KViews1like1Comment