• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved /etc/named.conf: permission denied

Erwan

Regular Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Obsidian v18.0.50
Hi all,

When setting up a new instance, everything works fine... except Bind which fails.

In the /var/log/syslog file, i've this:
open: /etc/named.conf: permission denied
named[33696]: loading configuration: permission denied
named[33696]: exiting (due to fatal error)
systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: named.service: Failed with result 'exit-code'.
kernel: [73566.183889] audit: type=1400 audit(1678803291.528:63): apparmor="DENIED" operation="open" profile="named" name="/mnt/disk/var/named/run-root/etc/named.conf" pid=33696 comm="named" requested_mask="r" denied_mask="r" fsuid=110 ouid=0


I can access to /etc/named.conf:
# ls -l /etc/na*
lrwxrwxrwx 1 root root 34 Mar 13 12:17 /etc/named.conf -> /var/named/run-root/etc/named.conf

Do you have an idea of the problem?
Thank you.

Erwan
 
Back
Top