• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue Problems with fresh install Plesk and Laravel

Killug

New Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
18.0.74.3
Hello,

I am having an issue with a fresh installation of Plesk and Laravel. When I attempt to install Laravel, I receive the following error message:

I then logged in via SSH and entered the following:

The task "ext-laravel-task\laraveldeployskeletontask" has failed.
Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Package operations: 0 installs, 0 updates, 35 removals
> Illuminate\Foundation\ComposerScripts::prePackageUninstall
- Removing theseer/tokenizer (1.3.1)

plesk bin extension --upgrade composer & plesk bin extension --upgrade laravel

Both times I received a message saying that the extension had been successfully installed. When I try to install Laravel, I still get the same message as described above. Unfortunately, I don't know what to do next and hope you can help me.
 
Hello, @Killug . Could you please confirm the version of the Composer extension? If it is below 1.3.4, please try updating it to the latest version.
 
Hi, thank you very much for your message. I know I've had this problem before and I found my older post. Unfortunately, I wasn't able to reproduce and fix it. I've sent a screenshot. The version is 2.8.12, a fresh new installation of Plesk.

I wish you and the team a Merry Christmas.


Bildschirmfoto 2025-12-24 um 19.04.59.png
 
Thank you for the confirmation. I was able to replicate the behavior and forwarded the report to our team for further review. I will follow-up with more details as soon as possible.

Merry Christmas!
 
Hello, @Killug. The issue should be sorted in Laravel extension version 1.5.5-6301. Please update the extension and make sure that the data of the failed installation is removed from the document root of the domain name. Let us know if you face any further issues.
 
Back
Top