Troubleshooting to TLS Error - ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Troubleshooting to TLS Error - ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Troubleshooting to TLS Error - ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Troubleshooting to TLS Error - ERR_SSL_VERSION_OR_CIPHER_MISMATCH
2024-08-30 03:12:50 - last edited 2024-08-30 03:18:44

Background:

 

When attempting to log into an old router, you encounter the error ERR_SSL_VERSION_OR_CIPHER_MISMATCH in your browser. This usually indicates that the SSL/TLS encryption protocol version or cipher suite used by the router is outdated and incompatible with modern browsers. Here are some steps to resolve this issue.

 

Troubleshooting Steps:

 

1. Try Using HTTP Instead of HTTPS


In the browser’s address bar, change https:// to http:// and then try accessing the router’s IP address again. For example, enter http://192.168.1.1.
Many old routers do not support HTTPS or use an outdated SSL/TLS version, while HTTP is an unencrypted connection that may allow successful access.

 

2. Temporarily Lower the Browser's Security Settings


You can try temporarily lowering the browser’s security settings to allow it to connect to insecure sites, though this carries significant security risks and is not recommended as a regular solution. Here’s how you might do it in Chrome:
Type chrome://flags/ in the browser's address bar.
Search for "TLS" or "SSL" to see if you can enable support for older TLS/SSL protocols.
Be aware that this is risky, and it’s advisable to revert the security settings back to their original state immediately after configuring the router.

 

3. Use an Older Browser


Newer browsers may enforce higher SSL/TLS protocols, blocking access to insecure connections. Try using an older browser (like an older version of Internet Explorer or Firefox) that might allow access to pages using outdated protocols.

 

Update Logs:

 

Aug 30th, 2024:

Release of this article.

 

Recommended Threads:

 

Fail to Connect to the Omada Router as OpenVPN Server

What If My Windows Computer Is Not Accessible or Pingable Over the VPN/VLAN Interface

mDNS Repeater on the Router Doesn't Take Effect

 

Feedback:

 

  • If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
  • If there is anything unclear in this solution post, please feel free to comment below.

 

Thank you for your support and contribution to TP-Link Community!

 

------------------------------------------------------------------------------------------------

Have other off-topic issues to report? 

Welcome to > Start a New Thread < and elaborate on the issue for assistance.

 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0      
  0      
#1
Options

Information

Helpful: 0

Views: 339

Replies: 0

Related Articles