• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

debian 3.1 + plesk7.5.3 - considerations?

P

perler

Guest
hi,

being new to plesk but quite senior to debian i would like to get an idea from the insiders, what considerations in regard to administration we should make.

for intance:

- should we hold back in apt some packages crucial to plesk?

- what happens if there are security vulnerabilitys in, let's say, phpbb. is plesk backporting the patches ( i see version 2.0.11 right now in the application fault, a version i definietly wouldn't install onmy servers)

are there documents to be read in this regard beside the administrators handbook?

thanks in advance,

PAT
 
You must log in or register to reply here.

Similar threads

F
Input Critical security updates need technical details
Replies
17
Views
4K
danim
D
T
Question How to Detect and Mitigate Next.js / React Vulnerabilities on Windows Plesk Server
Replies
0
Views
4K
teletek
T
S
Resolved Dovecot 2.4.1-4 and 2.4.2 silently ignore administrator-scoped mailbox { sieve_script } blocks for IMAP events
Replies
3
Views
3K
stephan.kurz
S
I
Question Plesk firewall and preventing clashes with firewalld
Replies
5
Views
3K
iainh
I
R
Resolved CVE-2026-42945 Nginx Rift and older Wordpress Toolkit heads up
Replies
14
Views
12K
rhall
R
Back
Top