You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Always, when I research something via my favourite search engine regarding ProFTPd, I find some https://forums.proftpd.org/ links, which have some interesting texts in the preview, but the forum is unreachable since months for me from any device, so I'm wondering, if this forum is still active or not.
All my browsers are reporting the following error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
If it's not active anymore, it would maybe make sense to remove it from the search engines and report a better HTTP status code. :-)
The text was updated successfully, but these errors were encountered:
Working here from Linux Firefox 121.0. Not working from Linux Chromium 120.0.6099.199.
This site can’t provide a secure connection
forums.proftpd.org uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
I think Chromium deprecated some security protocols. I have other sites that Windows Chrome won't connect to that work in Firefox, for now. Eventually Firefox will do the same.
The primary issue is that the web server hosting the forums is using extremely outdated software and config. It only supports SSLv3 (yikes) and TLSv1.0, along with some very dangerous ciphers (I won't share too much). Modern browsers started disabling TLSv1.0 and thus block access to the site.
A workaround for Firefox (but far from ideal) is to set the security.tls.version.enable-deprecated preference to true under about:config
Always, when I research something via my favourite search engine regarding ProFTPd, I find some https://forums.proftpd.org/ links, which have some interesting texts in the preview, but the forum is unreachable since months for me from any device, so I'm wondering, if this forum is still active or not.
All my browsers are reporting the following error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
If it's not active anymore, it would maybe make sense to remove it from the search engines and report a better HTTP status code. :-)
The text was updated successfully, but these errors were encountered: