Author: Mark
ERR_SSL_VERSION_INTERFERENCE
ERR_SSL_VERSION_INTERFERENCE The ERR_SSL_VERSION_INTERFERENCE is an SSL related error that usually appears in Google Chrome and Firefox when a site (server) uses TLS1.3. The err_ssl_version_interference error can be solved in a number of ways. Some guides suggest disabling TLS1.3 entirely in your browser, however that isn’t the preferred solution as TLS1.3 offers major security and performance benefits over TLS1.2 and lower TLS versions. A possible cause of this error can be a mismatch in TLS1.3 versions supported by the webserver and
Networkwide SSL activation fails on IIS server 7
Sometimes networkwide SSL activation can fail on IIS server 7 setups because the request entity is too large. When this happens, you can increase the uploadReadAheadSize value in your applicationHost.config file. The default value is set too low for some websites, so increasing the value should resolve this issue. For detailed instructions, please refer to http://galhano.com/blog/?p=2135
How to fix the ‘no response from webpage’ warning
Really Simple Security checks if there is a valid SSL certificate, and if it can find the marker from the Mixed Content Fixer in the HTML of your website. In some cases, the plugin’s request does not receive a valid response. There can be several causes for this: Server or plugin security blocks the request If the front-end of your website loads without any issues when visiting it in your browser, this is probably the case in your situation. The
Mixed content when using Divi theme
Once in a while, we come across users who experience mixed content issues when using Divi theme and Divi builder. Divi uses its own built-in caching mechanism. To fix the mixed content the Divi cache has to be cleared. To do this, navigate to the ‘Divi’ menu in the left menu bar in the WordPress admin area and press ‘Theme options’: 1. Legacy versions of Divi If you’re using a newer version of Divi, please navigate directly to #2.
Chrome and Firefox ending support for legacy Symantec certificates
Chrome and Firefox ending support for legacy Symantec certificates From Google Chrome version 66 and Firefox 60 onwards, support for legacy Symantec certificates (certificates issued before 1 June 2016) will be suspended due to a number of issues. If your site uses one of these certificates this will result in the site not having the green lock and a warning being shown to your visitors. This affects certificates from the following providers as well, as they are (former) sub-companies/partners of Symantec: