• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Domain aliases not pointing to correct domain

F

flash4tech

Guest
Here is what happened;

Was experiencing some issues with Plesk on a linux (centos 5.2) server. Plesk kept on crashing and we were trying to assist a client with fixing it. We did manage to get it fixed but it kept on going down again.

Client asked us to reinstall Plesk without reinstalling the OS which we did but the problem didn’t go away. We suggested that the best way to get this sorted is to have the system and Plesk reinstalled. At which point the client suggested that we can do it if we are going to be able to restore his data from the backup image. We tried to restore the image onto a test server and get individual folders from the server and put it on a folder on the server.

We reinstalled the server and the OS and grabbed the folders from the test server which we had restored the image of their server onto from their NAS. However, the most recent image was corrupt so did not work properly so the older image was used. However, there had been some changes made from the time the older image was taken to the time that the server was reinstalled which meant the files/folders restore to their previous states. We now had a situation whereby Plesk had the up to date information but the server/file system had old information. This meant that every time Plesk fetched information it wasn’t able to get the right files from the file system. An example of the changes was changing the domain name from .com to .co.uk or the other way round. This only affected a few of the domains and not all of them. Ones that didn’t have changes made worked fine.

Now despite the correct information being entered for the domain aliases, some are still pointing to incorrect domains. Any advice of help greatly received.
 
I can suggest you compare dom_id in domainaliases table with corresponding ids from domains table and try to correct it if you will find incorrect records.
 
Back
Top