Resolved Laravel Toolkit breaks after renaming domain

[mediengestalter]

Server operating system version

Ubuntu

Plesk version and microupdate number

current

As already posted here,
after renaming a domain in plesk, Laravel Toolkit complains about not finding artisan:

Execution /opt/plesk/php/8.3/bin/php has failed with exit code 1, stdout: , stderr: Could not open input file: artisan

 

[Sebahat.hadzhi]

Hello, @mediengestalter . I am unable to replicate the reported issue by renaming a domain name, the Laravel application operates without issues. Could you please try running the repair utility for the domain name you are experiencing issues with:

plesk repair fs domain.tld

 

[mediengestalter]

Thanks for the reply! What does this command do exactly? The application is in production.

 

[Sebahat.hadzhi]

It checks the integrity and structure of the file system - files/directories ownership and permissions of the domain name in question. Here's the documentation on this particular repair utility:

• Plesk Repair Utility: File System

 

[mediengestalter]

Okay. Running `plesk repair fs mydomain.tld` returned `Error messages: 0; Warnings: 0; Errors resolved: 0`

But I get a new message now:

Execution /opt/plesk/php/8.3/bin/php has failed with exit code 1, stdout: filemng: Failed to change directory to /var/www/vhosts/mydomain.tld/old.mydomain.tld/web: No such file or directory System error 2: No such file or directory , stderr: filemng: Failed to change directory to /var/www/vhosts/mydomain.tld/old.mydomain.tld/web: No such file or directory System error 2: No such file or directory

Where old.mydomain.tld should actually be new.mydomain.tld to work.

 

[Sebahat.hadzhi]

Thank you for the update. There could be some inconsistency in the Laravel Toolkit database. Could you please check it out by executing the following command:

sqlite3 /usr/local/psa/var/modules/laravel/laravel_toolkit.sqlite
select * from applications where id = 1;

Please make sure to replace the ID in the command with the one corresponding to the Laravel application you have having issues with. You can confirm it in the URL address when you access the application in the Laravel Toolkit.

 

[mediengestalter]

Thanks. Fixed it manually in the .sqlite3 file.
Would be nice if plesk would take care of that automatically.

sqlite3 /usr/local/psa/var/modules/laravel/laravel_toolkit.sqlite3

select * from applications


UPDATE applications
SET deploymentPath = 'new.mydomain.tld/web'
WHERE id = 9;

 

[Sebahat.hadzhi]

I am glad to hear you were able to sort out it out. According to our developers the issue likely occurred because the Laravel toolkit database was locked in the moment the domain was renamed. Unfortunately, since this is conditional event and it cannot be reproduced it is difficult for our team to propose a universal solution.