Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Issue could not create //run/named/session.key
- Thread starter nMLxTMJTZ
- Start date
Have you checked that the path named in named.conf for "session-keyfile" is writeable?
1) Look into /etc/named.conf and find the line "session-keyfile".
2) Check the file permissions of that path, e.g. "ll <path>".
2) Check the file permissions of that path, e.g. "ll <path>".
This looks correct. Could you please check whether the situation described in https://support.plesk.com/hc/en-us/...based-OS-couldn-t-mkdir-run-Permission-denied is yours and maybe try the suggested solution?
We discussed it here and think it is necessary to check directly on your server. It's most likely not a Plesk issue in the first place, but we're still willing to assist to the best of our knowledge. Please open a support ticket so that a Plesk engineer can check and solve the issue directly on your server.
To sign-in to support please go to https://support.plesk.com
If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work
If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
To sign-in to support please go to https://support.plesk.com
If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work
If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
Johnny9977
Basic Pleskian
Hi. Any out coming here? I have the same issue!!!
asolopovas
New Pleskian
I am struggling from the same issue it constantly flooding my logs since I clean installed my plesk panel.
These 2 following me every couple minutes.
If you check the folder the folder owned by root:bind
ls -ld /run/named
drwxrwxr-x 2 root bind 40 Mar 24 11:37 /run/named
if I chown it with bind:bind, problem disappears until reboot, when the folder reverts to root:bind, how can this behaviour be adjusted is there any solution to this problem?
These 2 following me every couple minutes.
| 2025-03-23 18:20:12 | err | named [766] System daemons [3] | failed to generate session key for dynamic DNS: permission denied |
| 2025-03-23 18:20:12 | err | named [766] System daemons [3] | could not create //run/named/session.key |
If you check the folder the folder owned by root:bind
ls -ld /run/named
drwxrwxr-x 2 root bind 40 Mar 24 11:37 /run/named
if I chown it with bind:bind, problem disappears until reboot, when the folder reverts to root:bind, how can this behaviour be adjusted is there any solution to this problem?
