Forum Discussion
treasurydirect.gov not accessable on Hughesnet
When I try to access treasurydirect.gov using Hughesnet I get this error. Secure Connection Failed An error occurred during a connection to www.treasurydirect.gov. PR_CONNECT_RESET_ERROR Went to a loc...
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
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.
