Articles in this section

How to update Plesk Obsidian to the latest build
MariaDB upgrade via Plesk interface fails: curl: (28) Operation timed out after 15000 milliseconds with 0 bytes received
Plesk Update fails with errors: Integrity constraint violation: 1062 Duplicate entry db_name db\_name' for key 'PRIMARY'
Package update fails on a Plesk server: ERROR: Transaction test error: Index.xml from install of mysql-common conflicts with file from package MariaDB-common
Unable to install Microsoft Web Deploy on Windows 2025 with Plesk: Feature name MicrosoftWindowsPowerShellV2 is unknown
The "plesk repair" utilities show warnings on Debian-based systems: Cannot find deb-archive for package
Plesk updates on Debian 10 fail due to missing packages in repo: 404 Not Found
Does Plesk support AlmaLinux 10?
Does Plesk support Debian 13 (Trixie)?
How to deploy a VM with Plesk on the IONOS Cloud platform using official Plesk images?
See more

Is it necessary to disable AppArmor for Plesk on a Debian 11 (Bullseye) or 12 (Bookworm)?

Jose Flores

Updated October 08, 2025 18:00

kb: how-to

Applicable to:

Plesk for Linux

Question

Is it necessary to disable AppArmor for Plesk on a Debian 11 (Bullseye) or 12 (Bookworm)?

Answer

No. The recommendation to disable AppArmor only applies if you are upgrading from Debian 9 to 10 and if the bind service is unable to start after that. This is mentioned in our dist-upgrade guide.

If it is a fresh installation, disabling AppArmor is not necessary.

Additional information

Comments

0 comments

Please sign in to leave a comment.