Issue enabling Plesk Firewall

[karyo]

Server operating system version

Ubuntu 20.04 LTS

Plesk version and microupdate number

18.0.52 Update #3

Hi ,

I'm having problems enabling Plesk Firewall.

I installed Plesk Firewall, but it does not activate and gives the following error.

Failed to apply the firewall configuration.

• I did not receive connectivity confirmation after applying new firewall configuration, then same happened after I reverted to previous configuration. This means that both new and previous configurations were bad. Emergency rollback to configuration without rules was performed. Firewall is now disabled. Fix your rules and try again.

I can't even edit the rules in the panel.
What is the problem?

 

[Dave W]

Hi Karyo,

This might help;

https://support.plesk.com/hc/en-us/articles/14220544536727-Plesk-Firewall-can-not-be-enabled-in-Plesk-18-0-52-and-newer-I-did-not-receive-connectivity-confirmation-after-applying-new-firewall-configuration

D.

 

[karyo]

Hi Karyo,

This might help;

https://support.plesk.com/hc/en-us/articles/14220544536727-Plesk-Firewall-can-not-be-enabled-in-Plesk-18-0-52-and-newer-I-did-not-receive-connectivity-confirmation-after-applying-new-firewall-configuration

D.

Thankful
My problem was not solved with this link

 

[Dave W]

You used the workaround right?

Edit the file /usr/local/psa/admin/sbin/modules/firewall/rules and set

DEFAULT_CONFIRM_INTERVAL to 30:

grep DEFAULT_CONFIRM_INTERVAL /usr/local/psa/admin/sbin/modules/firewall/rules
DEFAULT_CONFIRM_INTERVAL = 30

This is what worked for me on numerous servers.

D.

 

[karyo]

You used the workaround right?

Edit the file /usr/local/psa/admin/sbin/modules/firewall/rules and set

DEFAULT_CONFIRM_INTERVAL to 30:

grep DEFAULT_CONFIRM_INTERVAL /usr/local/psa/admin/sbin/modules/firewall/rules
DEFAULT_CONFIRM_INTERVAL = 30

This is what worked for me on numerous servers.

D.

Yes, I changed it to 30, but there is still a problem

 

[Peter Debik]

Please try the solution from https://support.plesk.com/hc/en-us/...ion-after-applying-new-firewall-configuration
You can also use longer timeout values.