Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

PR_END_OF_FILE_ERROR

  • 4 ответа
  • 3 имеют эту проблему
  • 30 просмотров
  • Последний ответ от cor-el

more options

Hello Team, Recently after our Firefox browsers updated to version 69.0.3 (64-bit), we are unable to open some of our internal sites - the error received is Secure Connection Failed - PR_END_OF_FILE_ERROR. With other browsers like Chrome or Edge the issue is not presented - only with Mozilla. We tried creating new profile in Mozilla, checked the SSL and TLS settings of Mozilla also. Can you help us troubleshooting this ? Screenshot attached.

Hello Team, Recently after our Firefox browsers updated to version 69.0.3 (64-bit), we are unable to open some of our internal sites - the error received is Secure Connection Failed - PR_END_OF_FILE_ERROR. With other browsers like Chrome or Edge the issue is not presented - only with Mozilla. We tried creating new profile in Mozilla, checked the SSL and TLS settings of Mozilla also. Can you help us troubleshooting this ? Screenshot attached.
Приложенные скриншоты

Изменено radostin.todorov

Все ответы (4)

more options
more options

The internal site was opening without problems - in Mozilla, before the latest update of the browser. And as I described - its opening without problem in other browsers - that makes me think that the ISP maybe has nothing related with the issue ?

more options

Did you check out the Bing link?

more options

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..