Solve the problem of adding authorization to the whitelist of Western Digital Cloud Server

Tonight Snail was helping a netizen solve a server problem. He moved Western Digital's virtual host to the Western Digital cloud server. The cloud server also installed the WEB environment normally, but there was no problem with the relocation data and database parsing, but the website could not be opened. So I came to Snail to solve this problem. I simply checked that there is no problem with his server. The ROOT is accessible, the PING speed is OK, and port 80 is also OK.

I feel like this server vendor has a security group that needs to be set up. However, general merchants open ports. Is it still necessary to add a whitelist? Because Snail has never used or seen Western Digital's cloud server products before. So I logged into his Western Digital cloud server backend.

Snail can see that there is whitelist management. Let's see what it is

We can see that the server’s IP address needs to be authorized to the website. This is the first time we have encountered this situation, so follow the prompts to add his website domain name. But when adding it, it prompts that it has been bound to the virtual host, so it needs to be unbound first.

We need to first go to the virtual host host domain name to bind and unbind, and then we go to the whitelist to bind the domain name. In this way, if we look at it again, the website can be accessed normally.

The problem was solved successfully.

Recommended site searches: server purchase, icp registration number, registration space, independent ip, overseas virtual host space, dynamic ip dial-up server, free php mysql space, website registration number query, Hong Kong server rental, foreign trade space,