Dear web developers, we have long argued about the SSL protocol in general and the HRAFT one in particular. And we decided to try to somehow help you with it (charms). We present you a list of four main reasons why the SSL connection in your web browser doesn't work:1. You disabled SSL in the browser. This is obvious. You can't do without it. SSL is an integral part of the web and it's not for me to tell you don't need it. The point is that you can't trust that the site you're visiting will work properly. It's not like it was designed for this purpose. The author of SslProtector should be ashamed of himself. He hasn't worked with anything like this since high school.2. You disabled SSL in the browser. If you don't know anything about SSL, then please read the manual from the manufacturer. It will tell you everything you need to do to enable it in your server. If you don't know anything about SSL, then please read the manual from the manufacturer. And if you are not sure about something, then this option should be on your website.3. You asked Google, but Google doesn't provide it. If you don't want to take responsibility for your website, then don't create it. Google does not provide SSLv3 support, so you just need to make sure that you can connect to the project and make changes without any error, without any security concerns.4. You are not a developer, so you just need to leave it and do not bother. If you ask Google, they will probably just ignore you and do it, that is, if you ask Google for help, then they will probably just give you the list of sites that you are already familiar with, and not the final result, which, of course, is not what you expected.