• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Issue Laravel Toolkit 1.5.7 fails to detect Laravel 13 instance — artisan list --format=json returns empty output for domain user

Matanzas

New Pleskian
Server operating system version
AlmaLinux release 10.1 (Heliotrope Lion)
Plesk version and microupdate number
Plesk Obsidian 18.0.77.3
Greatings

After the automatic update of Laravel Toolkit to 1.5.7-11846 (applied automatically on May 22, 2026 at 03:46), the toolkit stopped detecting my Laravel 13 application. The toolkit was working correctly on May 21, 2026.

Environment:
- Laravel Toolkit: 1.5.7-11846
- Laravel: 13.4.0
- Symfony Console: 7.4.8
- PHP: 8.4.21
- Plesk: 18.0.77

Symptoms:
- Clicking "Scan" shows "Done" in all steps but the Laravel panel does not appear
- No error is shown in the Plesk UI (bug EXTPLESK-8981)
- The following error appears in panel.log with debug enabled:

array_filter(): Argument #1 ($array) must be of type array, null given
File: Laravel.php:206 → getCommandList() → artisanCommandExist('plesk-ext-laravel:config-source')

Root cause identified:
The command "artisan list --format=json" returns 0 bytes (empty output) when executed as the domain user, but works correctly as root. The toolkit calls this command internally to detect the Laravel instance.

Reproduction:
su -s /bin/bash -c '/opt/plesk/php/8.4/bin/php /path/to/httpdocs/artisan list --format=json 2>&1' domain_user | wc -c
Result: 0

The same command on a different domain with Laravel Toolkit working correctly returns the expected JSON output.

Please investigate why artisan list --format=json produces empty output when executed as the domain system user in Toolkit 1.5.7.

Thank you.
 
Hi, @Matanzas . If the website in question has been compromised, it is very likely for the toolkit to fail with the detection. Can you please scan the website using Imunify or a similar tool? If there are any infected files detected, please either clean them or remove them (if possible).

p.s. we have a registered bug (EXTPLESK-8981) to improve the error reporting of Laravel Toolkit in such cases.
 
Back
Top