Ssl is configured on apache of centos6.5 but still cannot be accessed with https …

  html5, question

I applied for the free SSL of Tengxun Cloud: Trustasia DV SSL CA-G5, and then downloaded the relevant documents of the certificate. There are altogether three documents: 1_root_bundle.crt, 2_www.domain.com.crt and private key file 3 _ www.domain.com.key.
According to various blogs searched on the internet, I have already configured them completely in apache, and the relevant settings in etc/httpd/conf.d/ssl.conf have been configured. then the https cannot be accessed by the internet.
This is an error message accessed with chrome:

This website cannot provide a secure connection.
 The response sent by www.example.com is invalid.
 Try running Windows Network Diagnostics.
 ERR_SSL_PROTOCOL_ERROR

Then I couldn’t connect wget https … on my server. The error message is as follows:

--2017-02-13 10:24:04--   https://www.example.com/
 Resolving www.example... 119.********
 Connecting to www.example.com|119.********|:443... connected.
 OpenSSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
 Unable to establish SSL connection.

Then I checked apache’s error log and found that ssl had no error message, only apache’s own error message:

[notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
 [notice] caught SIGTERM, shutting down
 [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
 [notice] Digest: generating secret for digest authentication   ...
 [notice] Digest: done
 [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
 [error] [client  59.172.151.203 ] File does not exist: /var/www/html/favicon.ico
 [error] [client  180.153.214.200 ] File does not exist: /var/www/html/1.html
 [notice] caught SIGTERM, shutting down
 [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
 [notice] Digest: generating secret for digest authentication   ...
 [notice] Digest: done
 [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
 [notice] caught SIGTERM, shutting down
 [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
 [notice] Digest: generating secret for digest authentication   ...
 [notice] Digest: done
 [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
 [notice] caught SIGTERM, shutting down
 [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
 [notice] Digest: generating secret for digest authentication   ...
 [notice] Digest: done

Then I got the following error message from https on the server by curl command:

curl: (35) SSL connect error

Moreover, I can open the Internet for such access.http://www.example.com:443

The following are articles that I refer to and set up according to my actual environment:
https://www.qcloud.com/docume …
http://www.cnblogs.com/liaoji …
There are still many articles about configuring conf.
Please help me look at it, but I can’t solve it now.

To add, I checked the usage of ports and found that ports 80 and 443 are both occupied by httpd, but I clearly wrote in the ssl.conf file that 443 uses https, which may be the key to the problem, but I don’t know how to solve it. .

I am also Aliyun, CentOS 7+lnmp
Centos comes with openssl, so there is no need to install it.
Ariyun has a free certificate application with tutorials. Download the certificate and set listening port 443 in nginx’s configuration file.
One of the servers can be accessed using https after nginx has set listen 433 and ssl on (site:https://feizhaojun.com ).
But the other one is dead or alive.
1. netstat View 433 is also listening state.
2. firewalld is closed.
3, iptables closed also not line
4. Ali cloud security group also opened port 443.
I don’t know how

update

One of the reasons I found that I could not access it was:
My other virtual host configuration xxx.conf also listened to port 443, but did not use ssl on;
So there was a port conflict.
Resolved.