Practical recording process of adding SSL certificate to WDCP panel (Apache) site

It’s 2018. At the beginning of the first article of the new year, I wish everyone a happy new year. This article was originally recorded last week, but due to time delay, last week a netizen used the WDCP panel when setting up Weiqing and saw that his engine only used Apache and did not use Nginx, so There are not many documents that you can refer to when configuring SSL. There are many Nginx SSL configurations recorded in the Snail Blog. Some time ago, the Pagoda Panel Apache configuration SSL was also shared (the Pagoda Panel installs a custom SSL certificate (Apache/Nginx) for the site).

Although the development and updates of WDCP panels have indeed been slow in the past two years, the number of users is still relatively large. Perhaps the official has not found a suitable profit model, so the progress of development and updates has slowed down. Snail has not been exposed to the WDCP panel for a long time. When I logged in to this netizen's panel background, I saw the UI changes in the background, but the functions are still similar. Here try to see how to configure SSL in the WDCP panel Apache engine.

First, preliminary preparations

1. Site addition

If our domain name and site have already been added to the panel, skip it. And the domain name needs to be resolved to the IP address of the current VPS and server. Because the resolution takes time to take effect, we need to do it in advance.

2. Data security

If there is important data in our server and you are not particularly confident about solving the problem by yourself, then make a snapshot or data backup. Because I have encountered many netizens who accidentally deleted some system files during simple file editing. This is really not a problem. I don’t know which file I deleted when I look back.

3. Certificate preparation

We need to prepare the SSL certificate. Generally, the certificates we apply for are in four environment folders. We only need to find the one in the Apache folder. Because here we are installing based on the Apache environment.

Second, upload the certificate file

In the left menu of WDCP background\\"Website Management\\"-\\"SSL Certificate Management\\". We need to upload locally prepared Apache certificate files, three in total.

Select Apache, and then upload three files based on our locally prepared certificates.

Here is a trick. In \\"Save file name\\", you need to set the domain name when adding our site, so that it will be corresponding after uploading the certificate. Otherwise, it will not start if it does not match.

Third, startup certificate

Here we go to the site list, find the site that needs to enable SSL, and enable it.

Fourth, follow-up problem solving

Theoretically, the above method can be used to open the website normally via HTTPS, but it failed here. The problem may be caused by the wrong operating posture of the snail. Since the panel is difficult to handle directly, let's deploy it manually. Refer to the general method of "General Linux Apache Web environment configuration SSL certificate method" and manually modify the certificate and configuration of the two files.

Here we need to pay attention when operating by ourselves. We need to back up the two files. In case of failure, we can restore to the original feasible situation. After manual deployment, force startup is set in the third step, and it is barely done.

Fifth, summary

1. Using the WDCP background to add the Apache engine certificate is a twist and turn, and it is not so smooth. It was not as smooth as the Pagoda panel, and it was later solved by manually modifying the file. Therefore, if we are cautious about users who are not familiar with modifying configuration files, we need to make a backup before modifying the files.

2. Snail’s personal suggestion is that if we must use the WDCP panel, then use NGINX, because there are fewer configuration files to modify and it is easier to configure SSL. It is not clear whether it is a wrong posture or a built-in problem. After the certificate is automatically added in the background, it exists There are some problems, so adding it manually is simple and reliable.

Recommended site search: 1g US virtual host, domain name and space, free domain name registration, foreign PHP space, Hong Kong server defense, Hong Kong server rental, IP address, vps foreign server, anti-complaint vps host, mainland China registration-free host,