• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue Error message with WP update process "wrong directory" after move

itval

New Pleskian
Hi,

we had domain example.de with WP on vserver1 and moved it with Plesk Migrator to vserver2 and changed domain to example.com. The main directory on vserver2 however was still ..../example.de/... , the old one.

The site example.com works now for 3 months however on a daily basis we now get an error mail from Plesk showing:




Plesk
For following elements no updates have been installed:

1. Website "/httpdocs/wp/wp" (example.com): Failed to reset cache for the instance #1: filemng: Failed to change directory to /var/www/vhosts/example.com/httpdocs/wp/wp: No such file or directory

System error 2: No such file or directory
filemng: Failed to change directory to /var/www/vhosts/example.com/httpdocs/wp/wp: No such file or directory

System error 2: No such file or directory​

Therefore my questions:

1) Is this Plesk related or Wordpress? Our WP developer says Plesk....

2) If Plesk, how can I fix it and where?

The situation came from a missing parameter in the Plesk Migrator tool, so this is a recommendation to implement that as well.

thx,
Lino
 
If you're using the WordPress tool for each location, try scanning for them again. You should likely see a "broken" instance for the source one that you can remove if you're not using it or its files/database and the new one should pick up its new "home" regardless of directory change.
 
Back
Top