How to configure the website in the Pagoda panel to be compatible with the SSL TLS1.3 protocol

Have some of our netizens discovered that the websites that they have been using and running normally are also configured with SSL certificates to implement HTTPS encrypted access? But sometimes the browser compatibility is not very good, mainly because it currently needs to support the SSL TLS1.3 protocol, while the TLS 1.2 protocol was basically used in the past. Some insecure encryption algorithms have been removed starting with TLS 1.3, and in this article we have compiled a tutorial on how to configure support for TLS 1.3 in the regular Pagoda panel.

ssl_protocols TLSv1.2 TLSv1.3;ssl_ciphers TLS13-AES-256-GCM-SHA384:TLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-128-CCM-8- SHA256:TLS13-AES-128-CCM-SHA256:EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+ECDSA+AES128:EECDH+aRSA+AES128:RSA+AES128:EECDH+ECDSA+AES256:EECDH+aRSA+AES256: RSA+AES256:EECDH+ECDSA+3DES:EECDH+aRSA+3DES:RSA+3DES:!MD5;

We check the SSL configuration of the current site.

If we used the old Pagoda panel configuration, we can see that there is no TLS1.3 protocol. If we see that there is already a TLS1.3 protocol, then do not modify it.

Similarly, if we do not use the panel but use other one-click LNMP environments, the process will be similar. However, what Snail recommends is that as time goes by and the WEB environment becomes older or the software becomes older, we actually recommend reformatting or optimizing the system within a year or so, just like cleaning at home, we also need to slightly optimize the server. .

Recommended site searches: overseas virtual host space, overseas host, virtual host rental, virtual host rental, Hong Kong host high defense, registered cn domain name, Hong Kong virtual host space, website IP address query, US unlimited content host, domain name registration Price,