SSL_ERROR_INTERNAL_ERROR_ALERT/err_ssl_protocol_error [Solved]

  • Home   /  SSL   /  
  • SSL_ERROR_INTERNAL_ERROR_ALERT/err_ssl_protocol_error [Solved]

SSL_ERROR_INTERNAL_ERROR_ALERT/err_ssl_protocol_error [Solved]

Comments Off on SSL_ERROR_INTERNAL_ERROR_ALERT/err_ssl_protocol_error [Solved]
SSL_ERROR_INTERNAL_ERROR_ALERT

I ran into this error with my site FunnelXpert: ssl_error_internal_error_alert (on Firefox) / err_ssl_protocol_error (on Google Chrome).

At the same time the website was working fine through a VPN connection.

I used a free VPN called SetupVPN.

This is what the error looks like:

Secure Connection Failed

An error occurred during a connection to www.mydomainhere.com. Peer reports it experienced an internal error. Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

– The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
– Please contact the website owners to inform them of this problem.

Doing a traceroute in Windows command line saved the day.


C:\Users\Peter>tracert funnelxpert.com

Tracing route to funnelxpert.com [185.224.137.75]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 192.168.1.254
2 5 ms 4 ms 5 ms lo1.meroasr0-gyor.net.telekom.hu [145.236.238.13]
3 11 ms 12 ms 11 ms 81.183.3.6
4 11 ms 11 ms 11 ms 81.183.3.6
5 12 ms 11 ms 11 ms 81.183.3.139
6 7 ms 8 ms 7 ms 81.183.2.213
7 43 ms 42 ms 43 ms hu-bud03a-rc1-ae-12-0.aorta.net [84.116.137.1]
8 34 ms 47 ms 38 ms de-fra02a-rc1-ae-8-0.aorta.net [84.116.136.214]
9 * * * Request timed out.
10 42 ms 41 ms 41 ms nl-ams04a-rb2-ae-0-0.aorta.net [84.116.139.126]
11 40 ms 37 ms 37 ms 213.46.186.26
12 35 ms 36 ms 38 ms 185.8.179.39
13 36 ms 35 ms 35 ms 5.255.95.65
14 * * * Request timed out.
15 38 ms 37 ms 37 ms 185.224.137.75
Trace complete.

The last IP, 185.224.137.75 was the problem, which is (AS47583 Hostinger International Limited. 

The DNS cache was resolving to Hostinger, where I had hosted my site 1.5 years earlier.

My browser was trying to get the site served from an old server, therefore the error.

The problem occurred because the nameserver for the domain was suddenly changed from CentOS Web Panel name server to NameSilo‘s nameserve. NameSilo, which still had the old settings, reactivated them.

To make things worse, the TTL value was set to 172817, which is 2 days. Therefore despite the fact that I updated the settings, it took 2 days to take effect.