• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

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