Plesk hijacking a valid secure site with a "You see this page because there is no Web site at this address." message

Posted August 31, 2020 834 views

Here is a copied link


from a support request from

It is the summary of my current reason for posting here as Digital

Ocean is my host provider.

The title to this question is the problem I am experiencing.

I have a domain by the name

and it WILL load from all other computers except

from my home laptop on all three broswers (Chrome, Edge, Safari)

The laptop is running Windows 10.

I am running a SelfHosted Wordpress Virtual private server

and have installed a Certbot certificate to the appropriate

nginx config file.

I have flushed the DNS from PowerShell and no change.

I have cleared the browser’s cache numerous times and no change.

In spite of all of this attention to this I am hoping

that you Digital Ocean gurus can help.

Please advise, thank you.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
5 answers

Can you test how it works on your laptop with different internet connection ? E.g. switch from broadband internet connection to mobile, just for test, to eliminate possible ISP’s proxy impact.

Hi @jweinstein86,

I know it’s a long shot but try restarting your router, I’ve had issues in the past where the router had cache and thus I was having some really big cache issues.

Another solution would be to use the same laptop but with a different connection, maybe use your phone’s internet to see if you’ll experience the same issues again.


HI all,

I have tried both suggestions from your replys however there is still

no change in the situation.

When you ping your domain from your laptop, do you get a response from your DO droplet IP ?
If not, please check if there is any entry related to your domain in your laptop’s Windows 10 Hosts file. The path to it is %WinDir%\System32\Drivers\Etc\hosts

Hi Yannek and all who replied,

RESOLVED. There was a much deeper issue at play with this Plesk


Without the properly configured nginx and php configuration files this

problem could never have been resolved as I posted it.

Specifically, the source of this problem was random previously unnoticed

duplicate blocks/snippets of the same code in the

/etc/nginx/conf.d/YOURDOMAINNAME.conf file.

Also, in this same config file was added a line of code to **listen for

port 80 ( in addition to listen to 443 for ssl )**

See below.


server {
    listen 80;
    listen 443;

    ssl_certificate /etc/letsencrypt/live/; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/; # managed by Certbot


I am sure this would never have been addressed but fortunately with my

keeping up with the configuration files by comparing an already

successfully installed other domain with the

in process not yet installed site paid off.

No more Pesky Plesky default page. Hooray.