Forum Discussion
mkglish
4 years agoFreshman
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 local business and used their public wi-fi and the connection works just fine. Do I need to switch to a new ISP to access this particular site or is Hughesnet aware of the problem and working on a fix?
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
- RemyModerator
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
- mkglishFreshmanAs requested I Unplugged modem, let sit for 5 minutes, plugged back in. No joy. Problem still exists. No change in error message. "Secure Connection Failed An error occurred during a connection to www.treasurydirect.gov. PR_CONNECT_RESET_ERROR" Your help on resolving this will be appreciated. Mike Glish
- mkglishFreshmanAlso, I saw a workaround to this problem by disabling Web Acceleration. My modem has Web acceleration shown as not supported so I can't try that workaround. Just an FYI. Mike Glish .
- mkglishFreshmanI tried the suggested power the modem off/on. No change , I am still unable to connect to treasurydirect.gov. Hughesnet appears to be ignoring fixing this problem or even acknowledging it is their problem. I'll take this inaction as their indication I should just find a new ISP. For the record here is the error message I receive. "Secure Connection Failed An error occurred during a connection to www.treasurydirect.gov. PR_CONNECT_RESET_ERROR"
- maratsadeDistinguished Professor IV
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.
Related Content
- 3 years ago
- 6 months ago
- 2 months ago
- 10 months ago