Got an SSL certificate, why doesn't https access work?

Question

Apache HTTP Server

Hello. Received and installed an SSL certificate. But when you go to your site, it still does not connect via https.
Ubuntu 14.04. Vesta.
In the terminal, after receiving the message "Congratulations! You have successfully enabled https://santria.ml ", did nothing else. MB what else do you need?
Along the way: /etc/apache2/sites-available/ file 000-default-le-ssl.conf was created, didn't work, tried to change the name to domain name-le-ssl.conf didn't help.
When going to the site, it gives the message ERR_SSL_PROTOCOL_ERROR.
If you check the link https://www.ssllabs.com/ssltest/analyze.html?d=san...
"Assessment failed: No secure protocols supported
Known Problems
There are some errors that we cannot fix properly in the current version. They will be addressed in the next generation version, which is currently being developed.
No secure protocols supported - if you get this message, but you know that the site supports SSL, wait until the cache expires on its own, then try again, making sure the hostname you enter uses the "www" prefix (eg, "www .ssllabs.com", not just "ssllabs.com").
no more data allowed for version 1 certificate - the certificate is invalid; it is declared as version 1, but uses extensions, which were introduced in version 3. Browsers might ignore this problem, but our parser is strict and refuses to proceed. We'll try to find a different parser to avoid this problem.
Failed to obtain certificate and Internal Error - errors of this type will often be reported for servers that use connection rate limits or block connections in response to unusual traffic. Problems of this type are very difficult to diagnose. If you have access to the server being tested, before reporting a problem to us, please check that there is no rate limiting or IDS in place.
NetScaler issues - some NetScaler versions appear to reject SSL handshakes that do not include certain suites or handshakes that use a few suites. If the test is failing and there is a NetScaler load balancer in place, that's most likely the reason.
Unexpected failure - our tests are designed to fail when unusual results are observed. This usually happens when there are multiple TLS servers behind the same IP address. In such cases we can't provide accurate results, which is why we fail."

Answer 1

in the settings of the server itself, you need to enable access via https

Answer 2

On apache, you did not enable ssl access in the configuration files.
What to prompt, it is necessary to look configs. They need to post them.
In short, it should be approximately - conditionally such a design
ServerName site.ru
DocumentRoot /var/www/apache/data
SSLEngine on
SSLCertificateFile ssl/cert.pem
SSLCertificateKeyFile ssl/cert.key
t>
and from port 80 I would redect
ServerName site.ru
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
The simplest case without additional sites
help.ubuntu.ru/wiki/apache_%D0%B8_https
But in general it would be time to switch to nginx, here is a finished article with a properly configured config for
ssl