• 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 Composer Path Mismatch in Plesk Git Deployment

naseremad

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
18.0.64
When deploying a Laravel project through Plesk's Git integration, there is a path mismatch for the `composer.json` file due to a project structure change. The system is still referencing the old composer path (`/core/composer.json`) instead of the updated path (`folder/composer.json`). This occurs when the "Install composer.json dependencies" option is enabled during Git deployment.

Technical Details
- Original Path: `/core/composer.json`
- New Path: `folder/composer.json`
- Affected Systems**:
- Plesk Git Integration
- Laravel Project
- Composer Dependency Management

Problem Impact
This path mismatch prevents proper dependency installation during the deployment process, as the system cannot locate the `composer.json` file at the expected location.

Any suggestions regarding a solution?
 
Back
Top