Search results

Ah great, so for a fresh Debian 11 installation, AppArmor can stay active. I suggest to mention that on the 'software requirements' page. Can we just enable AppArmor again? Do we have to take something into account?

Thanks for the clear answer, IgorG. Is it planned to support AppArmor for Debian in the future? Is the implementation so different then on Ubuntu, where it is supported? I disabled AppArmor after installing Plesk on Debian 11 on one server. Is there something else I have to do?

Hi On the 'software requirements' page, I read that apparmor must be disabled on Debian. Is that still the case? Thanks Kris

Ahh great. Thank you.

Hello AYamshanov On both servers (Plesk Master and the Slaves): BIND 9.16.1-Ubuntu (Stable Release).

Hello When I delete zones in Plesk (which is the Master DNS), they are not deleted on the Slave DNS servers. Adding and modifying zones is not a problem, but zone files are not removed on the slave DNS servers when they are removed from the Plesk Master DNS server. It seems that no 'rndc...

A temporary solution can be to export a list of all domains on all servers, consolidate the output en import them in the prohibited domain list on all Plesk servers. https://docs.plesk.com/en-US/obsidian/cli-linux/using-command-line-utilities/site-sites.67067/...

Multi Server is only available for Plesk Onyx 17.0 and 17.5.

Sure, if you manage all domains of all clients on all Plesk web servers manually. Or run one (or more) slave DNS servers for each Plesk server. But that means that if you run 20 Plesk servers, you'll need (at least) 20 slave DNS servers. A better solution should be a Plesk upgrade of the Slave...

You can indeed have a slave DNS for multiple master DNS servers. Problem: when domain.com is configured on Plesk server A and another customer configures domain.com also on Plesk server B ... then both Plesk servers A and B are the master of that domain. The last DNS record update will propagate...

There should be only 1 primary DNS server for each zone. Slave DNS Manager should do this: Check if the server that pushes a new/change/delete record for a zone, is the primary DNS server for that domain. Yes? Then the server sending the push is legit. No? Then there is something wrong and...

I'm not sure what you mean, but dnf and apt are two very different package managers. The result is of course the same: they'll install, delete and manage your packages. I would recommend to have a look to Ansible for this. It will save you much time once you've configured your playbooks. If...

A few months ago, I migrated a whole Ceph cluster and many VM's (like name servers, monitoring servers, etc.) from CentOS 7 to 8. That's a pain. I'm planning to migrate all systems to Debian in the coming months. Why? Just like CentOS, Debian is rock solid. Familiarity with the apt-family. No...

That's how I've done all my past migrations too. But I was wondering if there was a existing tool that would automate a "full Plesk settings copy" of one server to another.

Hi I'm going to install a new Plesk server. How can I export a copy of the configuration of an existing Plesk server so all the settings are the same? I'm aware and familiar with the Migration tool and the Service plan exporter plugin. But I'm looking for a solution to export/import the Plesk...

Hi CentOS and RedHat announced that the support for CentOS 8 will end at the end of 2021. They are shifting focus from CentOS Linux to CentOS Stream. At this moment, Plesk isn't supporting CentOS Stream. I'm curious how this shift will be adopted in Plesk. Announcements: CentOS Project shifts...

Hi I'm a bit confused with some service plan settings. I get this warning when I save a service plan: PHP handler: FPM served by nginx Hosting settings management: enabled Setup of potentially insecure web scripting options that override provider's policy: disabled...

True, that's a solution. But when you have 20 Plesk webservers, you'll need 20 Slave DNS servers. A nicer solution would be 1 or 2 Slave DNS servers for all these 20 Plesk webservers. Any solution, tips or ideas for this, @IgorG ?

Okay I get it. Thats a Master > (multi) Slave solution. With (much) manual work for you and clients can't manager their own DNS records. That indeed has its advantages and disadvantages. My situation is that I have multiple Plesk webservers (Master DNS) and my customers can manager their own...

Your clients manage their DNS zones outside of Plesk? In an external DNS application? Do they create their subdomain records etc. manual in that external app? So when a new client is created, he has to add all his DNS records manually?