The pagoda panel solves the problem of automatically jumping to websites without SSL certificates

Original link:

written by fishing

Which one do you hear first, bad news or good news? The good news is that this site also uses integrated CDN acceleration, including its sub-sites: QQ instant, picture site, file site, navigation site, etc. The bad news is that because Moyu disconnected the FRPC client, I wanted to update umami to the latest version. As a result, the FRPC client was disconnected due to misuse, so it needs to be recovered after returning home from get off work.

The title of this article is also the actual problem that the boy encountered yesterday when he was tossing about the integration of CDN acceleration, so I will record it here. Let me talk about the actual environment first. The project on the local NAS shakes hands with the FRPS server on the local Docker through the FRPC client on the local Docker and the FRPS server on the Hong Kong Chicken, and then uses the port forwarding function of the integrated CDN to directly map and analyze the Hong Kong Chicken [ Public network IP]+[port]; in this way, there is no need to use the Nginx reverse proxy on the pagoda panel, ps: before using the integrated CDN, the domain name access is realized through Nginx reverse proxy .

It was mentioned in the “Easiest Way to Realize the Coexistence Tutorial of Pagoda Panel and Frp Server” blog post before, and friends who want to toss are welcome to bookmark it.

Problem Description

Back to the topic, it only takes four steps to solve the Pagoda panel Solve the problem that the website without the SSL certificate is automatically redirected to the website with the SSL certificate enabled Or even if the SSL certificate is enabled, you have not set the default site on the Pagoda panel and use other products to resolve to the Pagoda When the public network IP where the panel is located, it will automatically jump to other websites on the same public network.

Solve the problem

1. Open your pagoda panel and create a new static website at will (it can be a sub-domain name or fill in randomly) , as shown in the figure below, take as an example.

2. Find the website directory and delete the default index.html file, or replace it with a static navigation page/403, 404 and other pages . Here the kid directly chooses to delete.

3. Next, open the website and set it to add an SSL certificate (like the above domain name, you can find a non-matching domain name certificate and fill it in/expired ), but the kid uses an expired domain name certificate.

Fourth, set the site as the default site , so that it can take effect.

Call it a day! It is worth noting that an SSL certificate must be added so that it can come in handy when “a website without an SSL certificate jumps to another website configured with an SSL certificate”, and the purpose of deleting index.html is to make yourself more intuitive Know whether the DNS resolution of the added website is successful.

Just like the situation mentioned above by the kid, it is affectionately called a strange phenomenon.

This article is reproduced from:
This site is only for collection, and the copyright belongs to the original author.