Please help, I changed the login settings for admin access to HTTPS on the LAN/WAN. Everything worked fine when set to HTTP only. I get the following error on Edge and Chrome.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Hide details
Unsupported protocol
The client and server don’t support a common SSL protocol version or cipher suite.
What ciper / tls version is the Peplink offering - any further details in that error?
What model / firmware of Peplink and what version of Edge / Chrome?
I wonder if the Peplink is for some reason only offering TLS1.0 / 1.1 which are long deprecated and removed from modern web browsers.
Can you also check you are hitting the Peplink IP with HTTPS specifically and on the correct port? Maybe try in a private browsing window incase there is some odd caching happening too - the “unsupported protocol” bit of this would suggest you are perhaps trying http:// rather than forcing https://
Do you have the Peplink registered on InControl2 - if so perhaps try getting in via the WebGUI proxy there?
That’s just your browser warning you that you have not trusted the default SSL cert that ships with the device. I recently went through and generated my own SSL certs, set up DHCP entries for my Peplink products, and trusted my new cert in Chrome and Edge. Here’s the steps I saved to repeat this process again in the future:
Install the most recent Windows version of OpenSSL on your machine and ensure the binary is in your path, or reference the exe by the full path.
Where youdomain.com is, replace with whatever local domain you want to use and will enter local DNS records for. Also, update the IPs to match your local devices.
Import peplink.crt to Chrome Cert Store: chrome://settings/security?search=certificate
Cert must be imported into the “Trusted Root Certificate Authorities” tab.
Open Peplink router config, goto Network > Misc Settings > Certificate Manager > Web Admin SSL.
Click Edit (pencil) button.
Upload contents of peplink.key into “Private Key”
Upload contents of peplink.crt into “Local Public Key Certificate”
Now the SSL warnings will finally go away and things will work as expected, vs having to click a few extra things to bypass the cert warnings in the browser.
The mismatch between TLS versions or cipher suites, the ERR_SSL_VERSION_OR_CIPHER_MISMATCH error can occur due to “n” a number of other reasons which are as follows:-
Outdated browser or operating system
Use of old TLS versions, significantly older than TLS 1.2.
Web servers employ the outdated RC4 cipher suite.
Corrupted SSL state within the browser.
SSL certificate issues like mismatches or incorrect installations, etc