Plesk hijacking a valid secure website

Plesk just created the server error page but it is not blocking you from the website!

You’re are also on a Nginx server so, if I’m right about that, then you need to remember Nginx needs the htaccess directives modified some for use in the Nginx config file instead of htaccess.

On my Windows 10 box using Edge I get the site as https://www. but on the same box using Chrome, I get the https:// version without the ‘www.’

I took a look at your DNS, According to the one test, you don’t have an ‘A’ record for the root domain name itself… You do have an ‘A’ record for the ‘www’ domain.

When I looked at the raw records though I see the proper ‘A’ record…

You probably should add a Cname for the ‘www’ into the root domain or a second ‘A’ Record is fine with me.

On the WordPress side, set the site to either the ‘www.’ version or the root depending on your preference. I’m hoping killing any DNS resolver confusion will set this right and a refresh of your browser might help that also after you make these changes.

Let us know how all this goes.

Hi Jerald!

Sorry to hear you’re having this issue!

It’s most likely caused by the browser caching https://bhingssweets.com/ before WordPress was set up on it. Your browser has stored the site before anything was on it. That’s why it says: “You see this page because there is no Web site at this address.” It’s also why the site works on other devices but not your Windows 10 laptop.

You can test this solution as follows:

• Open https://www.bhingssweets.com/ in an incognito or private window, as that should bypass the browser’s cache.
• If the site opens, you can follow a guide on how to clear the browser cache by clicking here.

If clearing the browser cache doesn’t work, another software could be caching the site. If you’re using something like CloudFlare or a WordPress caching plugin, then one of those could be the problem.

Hope this helps! If you have any further issues, please let me know!

Niall, thank you for the suggestion.
I attempted this fix without a change to
the current situation.

Checked my WP Dashboard and I don’t have
any caching plugins installed either.

Jerry

JNashHawkins,

I added a second A record for ‘bhingssweets.com’
and still Plesk problem remains.

Also tried adding a CNAME record but error message
says “cannot share a name with another record.”

Jerry

Jerry,

In that case, could you please trying flushing and resetting the Windows DNS cache? You can follow these instructions, which also explain why it might help fix your issue: How to Flush and Reset the DNS Cache in Windows 10.

Niall

Hi Niall,

This did not change the problem.

At this point I an thinking of
reprovisioning the site.

Have you other suggestions?

Thank you.

Jerry

Jerry, have you tried using your laptop in a different location? Maybe your router or home server (if you have one) is causing some issue. Otherwise, you could try contacting your web host to see if they can help you.

Niall

Niall, I think I will contact Digital Ocean support.

Thank you again.

Jerry

You’re welcome, Jerry. Hope you manage to fix the problem!

Hi Niall and JNashHawkins and all who replied,

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

‘hijacking’.

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.

Here is WHAT NEEDS TO BE AT THE **HEAD OF THE DOMAINNAME.CONF** FILE

server {
    listen 80;
    listen 443;

    ssl_certificate /etc/letsencrypt/live/YOURDOMAINNAME.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/YOURDOMANNNAME.com/privkey.pem; # managed by Certbot

   server_name  YOURDOMAINNAME.com www.YOURDOMAINNAME.com;

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.

If you could enlighten me a little on WHY or HOW Plesk’s default page was directed to

that would be great. Just a general idea would be NTK.

Jerry

Hi Jerry,

Glad to hear you managed to fix your domain and site.

I’m not very familiar with Plesk, so I wouldn’t be able to answer that. You’d be better off asking in the Plesk Forum found here: https://talk.plesk.com/. I’m guessing it serves the error automatically based off a default template.

Niall

For other guys who would face the same problem:

I solved it by assigning ipv6 for the problem domain (before only ipv4 was assigned)