Solved! Go to Solution.
Hello all,
We've made network adjustments to account for how the Treasury Direct site is configured, so all can access the site normally without any need for workarounds. Thank you for bringing this to our attention!
-Liz
mkglish,
Thanks for reaching out, and welcome to the Community! We strongly recommend power cycling your modem by unplugging it from the power supply, and leaving it unplugged for at least a minute before reconnecting. This has resolved known treasurydirect.gov issues in the past. Please let us know if this resolves the issue!
Thanks,
Remy
@Remy ,
I tested this and I was able to replicate Mike's issue. Power cycling the modem didn't work. I then used a proxy and the page loaded.
Sorry I wasn't around to reply to you, Mike, about the proxy. I used the first thing that popped up, which was hide.me, and it worked. If you're going to do personal/private stuff, I'd investigate proxies some more and use a quality one that has a good privacy policy (there might be a fee for the better ones).
Glad you were able to access the page.
I am on a Mac, the link works fine for me.
The issue may be a beam issue or an IP issue. It's likely not an OS issue.
@fox12 wrote:I am on a Mac, the link works fine for me.
I don't know if this would make a difference, but it might be worth it to try an alternate DNS, like Google's.
I don't think it's them. As you may have seen, Fox12 can get to the site just fine, using the same ISP, so it's not an ISP issue. @GabeU suggested changing DNS, but you may also want to try clearing the DNS in your system. Here's the procedure:
1. Turn off all of the devices using the modem directly or via wifi (all phones, iPads, computers, etc.)
2. Unplug the modem's power from the wall socket.
3. Wait a minute, then plug the modem back in.
4. After all the lights on the modem are back on, wait an extra 5 minutes, then turn all your devices on one-by-one
5. Try the site again.
EDIT: I ran a traceroute and the request dead ends in LA due to what appears to be a dead CenturyLink server. Changing your DNS using the procedure above may reroute the request around the dead server (which is not a HughesNet server).
Hi folks,
Thank you for your patience while our engineers investigate. Hughes has identified that the Treasury Direct website claims to support IPv6, but is not configured correctly. Since HughesNet does use IPv6 where possible, connection attempts are failing. Using a provider or VPN that does not support IPv6 will automatically use IPv4 and is likely to work. Hughes is working on a workaround so that customers attempting to reach this site automatically fall back to IPv4 and has alerted the website developer to the issue. Independent tests such as https://ipv6-test.com/validate.php and https://ready.chair6.net can be used to verify the web server's misconfiguration.
As maratsade pointed out, using a proxy like hide.me can be used to access the site, and alternatively you can reboot your PC to try accessing the site.
Once I have any other news to share, I'll post back.
-Liz
This problem occurred before and there are other questions about it if you search. Hughes must have fixed the problem before. I asked about the problem in 2018 if I remember right. Now it came back on two of my computers but one works OK.
As Liz wrote, "Hughes has identified that the Treasury Direct website claims to support IPv6, but is not configured correctly. "
The problem is with the configuration of the Treasury Direct website. HughesNet is working on a workaround for customers affected by the Treasury Direct website's misconfiguration issue (which is not a HughesNet issue). Another workaround is to use a VPN to access the specific site.
The issue may likely occur again with other websites that have a misconfiguration, and just like now, it won't be a HughesNet issue.
@pankr003 wrote:This problem occurred before and there are other questions about it if you search. Hughes must have fixed the problem before. I asked about the problem in 2018 if I remember right. Now it came back on two of my computers but one works OK.
Mike, it's not a HughesNet issue. Running a tracert shows that the problem is with a CenturyLink server in LA, not with HughesNet. When you use a VPN you bypass that server.
I hope your issue gets solved.
Good morning folks,
Thank you for sharing your findings. I've escalated this internally to management and they have our network infrastructure team investigating. I'll post back once I have any news to share.
Your patience and understanding are much appreciated.
-Liz