An err_ssl_protocol_error message indicates that a website cannot be accessed securely over HTTPS. HTTPS is a secure protocol based on HTTP but with improved and high security. The websites that are accessible over HTTPS have valid SSL certificates. Even if you install a valid SSL certificate, you may still get the err_ssl_protocol_error.

In the next paragraphs, we will give an explanation and possible solutions for fixing the error SSL protocol.

Reload the Web server

After you renew the SSL certificate, restart the Web server. This is due to the latest changes to take effectivity. This can often fix the issue because the Web server has not restarted since the last installation or certificate renewal. Note that if you are a website owner you can easily do this. Otherwise, you would have to contact your hosting provider.

Verify the SSL certificate

If you have a free Let’s Encrypt SSL certificate, that’s about to expire, we recommend that you renew it. If you paid for one, make sure that you successfully pasted the certificate code or files into the right directory. Check the lines in your Web server configuration to see if the certificate is properly loaded.

Check the DNS

If you own the domain and have access to the DNS zone of the domain, you can revert any changes. Changes you made recently, or allow some time for the DNS changes to propagate through the Internet. If you are aware that DNS changes need time, wait a couple of hours and then access the website again.

Disable CDN

If you are using a content delivery network, the first step is to temporarily disable it. If there is no issue, and the website is loading, then you need to clear the CDN cache. Should the issue persists, then you can reenable the CDN and proceed with the investigation.

Clear the Web browser cache

From the client aspect, in most cases, the website is cached in the browser. It is a good practice for us to clear the web browser cache on time. If you do not want to clear the web browser cache, then access the website with a different web browser. Alternatively, access the website in incognito mode. Do note that clearing the web browser cache and cookies will log you out from everywhere. This means that you will have to log in to every site again.

Disable your VPN

If you are using a VPN you can disable it temporarily, to see if the issue persists. If there is no issue then you can stop using the VPN and try to find a new one.

Disable Browser Extensions

If you are using some new browser extensions that you installed recently, disable them. See if they were causing the website to be inaccessible. If everything is the same, enable them again and proceed with the investigation.

Update your Browser

Running older versions of web browsers can cause ERR_SSL_PROTOCOL_ERROR. Updating the browser to the latest version available can make the website accessible again.

System Updates

We recommend that you update your OS to the latest version available. We do this through the GUI of the operating system.

Contact the Hosting Provider

If you are the website owner, and cannot resolve the issue, contact your hosting provider. Your hosting provider is best suited to help you resolve any CDN issue.

If you are a client and unable to solve the issue, contact the website owner. The issue may be on the server level rather than locally on your computer.

You’ve fixed the err_ssl_protocol_error

These were some basic steps to solve the ERR_SSL_PROTOCOL_ERROR error. If you have an active service with us, you can always contact our technical support. We will help you with any aspect of your website. We are available 24/7.

If you liked this post on how to fix the err_ssl_protocol_error, share it with your friends or comment below.

The post How to fix “err_ssl_protocol_error” appeared first on LinuxHostSupport.

A 405 error is an HTTP not allowed error that prevents visitors from accessing the content of your website. The result of this error is a blank page and can be caused due to several reasons. If not resolved on time this can cause visitors to leave. Inevitably this damages your website reputation which may lead to a loss of sales.

In the next paragraphs, we will explain the reasons and possible solutions for fixing this error.

The 405 Not Allowed error can be tricky to identify quickly. Typically there’s only a blank page with the message at the top. We need to go through some checks which may take ten minutes to get our website up and running again.

Wrong URL

It’s easy to enter a long URL incorrectly which may lead to a 405 Not Allowed error. Try accessing the website homepage first. See if it is accessible and if so try to access the specific page you need. Checking the URL is so simple that sometimes we forget to do it, but it can solve our issue immediately.

Database Changes

If you use CMS websites with plugins such as WordPress, Drupal, or Joomla plugin updates can change your database. Before updating, it is necessary to have a database dump. In most cases, the database tables are changed by some plugins with full access to our database. Even if you uninstall the plugins, the database changes would not be reverted. One possible solution would be for the developer to modify them manually. It is recommended to have a database backup before doing anything to prevent such a scenario.

Web server configuration

If are using Apache as a web server, check the configuration of .htaaccess. We should consider the rewriting rules, limited directives, and who can access the website. If you are using Nginx, the configuration is in the Nginx virtual host file. You should check the Nginx location blocks, and the error page directives. This way you can make the changes, restart the web services, and see if that will fix the issue.

Files and Folder permissions

Uploading files in your website’s root directory with the root user can cause it to be inaccessible due to permissions. Always upload files and folders with the user who is the owner of the website’s root directory. However, if there are incorrect files and folder permissions we can fix them with the following commands:

chown www-data:www-data  -R .         # If the Apache or Nginx are owners
find . -type d -exec chmod 755 {} \;  # Directory Permissions
find . -type f -exec chmod 644 {} \;  # Files Permissions

Check the Code

You have to check if there are any hard-coded lines in your code. In addition, you should check your submitting forms, the GET, and the POST requests. Finally, check if some of the libraries in the website framework are using inconsistent methods rejected by the server. The developer should enable the debug mode and perform unit tests to find the issue.

Rollback any Updates

If your website was accessible before any plugin updates, the 405 Not Allowed method may be caused by the update. You should roll back the plugin update and see if that will fix the issue. If the issue is due to changed code, simply revert the lines of the changes and restart your web service.

Restore the whole Website

Finally, you can restore the website from our daily, weekly, or the whole backup made before any minor changes. This way we are sure that we will not lose time for debugging, and will fix the issue immediately. If your hosting provider offers managed services, contact their support to restore the website from a backup. If you have a bare-metal unmanaged server, you can always contact our technical support. We will help you with any aspect of your website. We are available 24/7.

These were some basic steps to solve the 405 Not Allowed error. If you liked this post on how to fix the 405 error, please share it with your friends. You can also leave a comment below.

The post How to fix “405 error” appeared first on LinuxHostSupport.