• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Plesk Site Preview works, but domain does not show updated website

Tobi232

New Pleskian
Server operating system version
CentOS 7.6 (64-bit)
Plesk version and microupdate number
18.0.72
Hi everyone,


I’m running a website on Plesk. When I use the “Preview” option in Plesk, the website loads correctly with the latest changes from httpdocs.


But when I try to open the site using the domain name (mediaone.cz), the old version is shown (or nothing changes at all).


  • Plesk server IP: 80.211.223.130
  • Domain mediaone.cz currently resolves to: 46.28.106.202
  • In Plesk Preview everything is up-to-date, but on the public domain it’s not.

It looks like the domain DNS might not be pointing to the correct server. Could someone confirm if this is a DNS misconfiguration, or if there’s another setting inside Plesk I should check?


Thanks in advance!
 
It is possible to have multiple IPs assigned to your server then assign a specific IP to a domain in Plesk BUT if you only have one IP address on your Plesk server (which you say it's 80.211.223.130) but the domain's A record is pointing to a completely different IP (46.28.106.202 in this case), then yes you have a DNS configuration issue, you need to update your DNS A record to point to the correct IP address.
 
Thanks for reply, that seems to me as the right answer, but there is still a question: how the hell did the IP change after about 3 years when everything was working fine and there were no issues before?
 
That's a question to ask your hosting provider (the people who gave you your IP address for your server).
 
Back
Top