I was hoping to test that this weekend as I host a webserver on a different ISP listening on a non standard port. I even specifically opened up port 2087 so I can test the exact same port. Unfortunately, I'm not on Hughes at my primary residence and was not able to make it to my Hughes based location over the holiday to test. Maybe this weekend... Anyhow, while it is possible that this is a router level setting, it may not be. For instance, Hughes blocks port 25 and that's done across their network, not at the router. Generally routers would not, by default, block traffic like that. It isn't inherently unsafe to send http(s) over non standard ports, especially outbound. So if it is at the router, it's a little non-standard, but definitely possible. At the router, a Firewall config may block stuff like that, but you disabled the firewall so I'd expect that traffic to flow right out. In doing some research about Hughes and ports, most links refer back to port mapping, which again probably isn't applicable to your case. I did find an old post from Liz that stated Hughes only blocks port 25 and that post referenced another source. Unfortunately, that was a very old post (like 2016 I think) and the link to the source post was broken. It's possible things have changed. In the meantime, you could try using an external proxy server or maybe try the TOR Browser (I think TOR uses an external proxy behind the scenes for you), though I'm not super familiar with it, but it's probably worth a shot.
... View more