Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
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.
No issue, DEB822 style is still fairly new being introduced first in Ubuntu 24.04 last year and tbh I don't think Plesk is using it on that version either lol. Since the old version is still working I'd say this is a non issue. You can submit it as a feedback over at Plesk Obsidian for Linux or https://features.plesk.com/
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.
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.