适用于其他类宝塔面板控制工具
1. Check whether the domain name is bound
- The site deployed in the pagoda supports domain name binding wild-card to ensure that the bound domain name includes the domain name added in the CDN platform
2. Check whether the site has SSL turned on.
- If the pagoda is not configured to force HTTPS back to the source, this step can be skipped.
- If SSL is configured in the pagoda and HTTPS access is forced, then the CDN site needs HTTPS 443 to return to the source, otherwise it will fail (report a 50x error). The 443 return to the source needs to configure the certificate on the CDN platform, you can view如何配置证书
- It is strongly recommended to turn off the mandatory SSL access (and mandatory HTTPS access) in the pagoda. Turning it off can make the CDN 80 return to the source (and HTTP return to the source). The speed of 80 return to the source is faster than that of 443, and there will be many fewer configuration items. Don't worry about the security of the certificate, it is all borne by the CDN. The certificate can be configured with one click on the CDN platform and can be automatically renewed.
3. Check other security restrictions
- The basic security items of the pagoda can be turned off, such as access restrictions, traffic restrictions, etc., which can be controlled on the CDN platform. Configuration in the pagoda may affect the CDN return to the source. If these configurations have not been changed, they are turned off by default.
- If the defense needs to be preserved, then the CDN needs to be allowed to return to the source normally through the whitelist.
4. Special treatment has been done in the configuration file
- Some services need to change Nginx, so the configuration file will be modified. If the CDN cannot be accessed, it also needs to be checked. If it has not been changed, the default is no problem.