搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Secure Connection Failed An error occurred during a connection to www.att.com. PR_END_OF_FILE_ERROR

  • 4 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 FredMcD

more options

If this is a security issue with a website why does it work one day and not the next? Also get this when I try to access troubleshooting, I try to log in and it sends me to google login and I get the same thing. Frustrated about to leave Firefox forever unless someone can explain the issue

If this is a security issue with a website why does it work one day and not the next? Also get this when I try to access troubleshooting, I try to log in and it sends me to google login and I get the same thing. Frustrated about to leave Firefox forever unless someone can explain the issue

所有回复 (4)

more options

Web search: https://www.bing.com/search?q=pr_end_of_file_error

radi.stoyanov said Turns out the option DNS over HTTPS is what caused the problem.

jamesafuf123 said https://support.mozilla.org/en-US/questions/1264659#answer-1237475 my ISP was blocking sites like that

cor-el said This usually means that Firefox wasn't able to find a cipher suites to use to connect to this server and reached the end of the list. There can be two possibilities: one is that the server is outdated and doesn't support modern cipher suites, another might be that the server only supports a few cipher suites and Firefox doesn't support any of these.

You can check your browser and possibly compare this with the server setup. https://www.ssllabs.com/ssltest/viewMyClient.html


https://appuals.com/pr-end-of-file-error/

more options

But if that is the case why does it work one day and not the next when trying to access the same site?

more options

But on the other hand unchecking DNS over HTTPS seems to resolve the problem, Thanks!

more options

Hello,

I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution.

Thank you for contacting Mozilla Support.