• 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 Debian 13 sources.list

klowet

Basic Pleskian
Server operating system version
Debian 13.2
Plesk version and microupdate number
Plesk 18.0.74 #1
Hi

Plesk on Debian 13 is still using the old /etc/apt/sources.list.d/plesk.list style. This should be changed to the DEB822 style which is now the default in Trixie.

Thanks
 
As @scsa20 mentioned, DEB822 is not yet enforced and .list is still supported. Anyhow, I will confirm with our team why it is used over DEB822 and follow-up with more details.
 
DEB822 was released in APT 1.1, some 10 years ago. It is now the default in Debian 13, but indeed it is not yet enforced. But I think it's best to follow the new standards.
 
@klowet , the reason for sticking to the old format is to use unified approach for all supported Debian-based OSes. Is there any real issue you have experienced? I can log an internal task for further check if you can provide some additional details on the impact. Thank you in advance.
 
We execute
Code:
apt modernize-sources
by default on all Debian 13 systems via Ansible. It removes the plesk.list file. When Plesk would update the plesk.list file, than the sources will be duplicated / point to different repo's.
 
Thank you for the additional details, @klowet . I was able to replicate the issue and forwarded it to our engineers for further review. At this point, they recommend to avoid converting our repositories through apt modernize-sources. In case that has been already performed, the workaround is to replace trusted GPG with keyrings GPG:

Code:
rm -f /etc/apt/trusted.gpg.d/plesk.gpg


# cat /etc/apt/sources.list.d/plesk.sources
Types: deb
URIs: http://psabr.aws.plesk.tech/stable/pool/PSA_18.0.74_17968/
Suites: trixie
Components: extras
Signed-By: /etc/apt/keyrings/plesk.gpg

Types: deb
URIs: http://psabr.aws.plesk.tech/stable/PHP83_17/
Suites: trixie
Components: all
Signed-By: /etc/apt/keyrings/plesk.gpg

Types: deb
URIs: http://psabr.aws.plesk.tech/stable/PHP84_17/
Suites: trixie
Components: all
Signed-By: /etc/apt/keyrings/plesk.gpg

The remaining warnings after applying the workaround can be safely ignored, they don’t affect Plesk installer's functionality. An additional task has also been created (ID PPPM-15232) to further track the matter. There's currently no ETA for the task. I will follow-up when there are more details.
 
Back
Top