• 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!
  • 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 Error: Another administrator is activating a configuration now

SAGraphics

New Pleskian
Trying to ban 3 IP address via the firewall. I created a custom rule, but when I try to apply it, I get:

"Error: Another administrator is activating a configuration now."

Why is this happening and what can I do about it?
 
I suppose that the previous attempt to apply firewall activation/configuration failed from Plesk Firewall extension and further updates are locked. Try to fix it with the following steps:
  1. Stop the sw-cp-server service:
    Code:
    # service sw-cp-server stop
  2. Remove the lock file /usr/local/psa/var/modules/firewall/safeact.confirm:
    Code:
    # rm /usr/local/psa/var/modules/firewall/safeact.confirm
  3. Start the sw-cp-server service:
    Code:
    # service sw-cp-server start
  4. Try to activate/configure the firewall again from Plesk firewall extension.
 
I found this thread today because I had the same error. Before trying the solution above, I tried the following instead and it worked:
  • In Plesk Panel go to Firewall > Modify Plesk Firewall Rules
  • Click Discard Changes > OK
I then checked and the previous rule I'd entered was still there. I don't know what change it thought was stuck, but this fixed it.
 
Back
Top