Firewall rule could not be updated. Firewall rule ... already exists.

Hi UHagi: Based on the error it is appearing there is another rule that exists on the database with the same name. I would suggest checking all rule's names to confirm any of them not configured with the same name (including the rules which are in the "Disabled" state as well)

Hi Vishal_R, I checked it befor. But I found the solution: One (disabled) rule used the same domain. I mean, the error message is wrong!

Even disabled rules count here.

that is not what he means. The error being returned is misleading. The error returned states, that a firewall with the very same rule name already exists. That was not the case, though. The same error will appear if you configure a WAF rule (different name) with a domain (virtual host which apache checks for based on SNI) which already exists in another rule. It's poor design in Webadmin.

that is not what he means. The error being returned is misleading. The error returned states, that a firewall with the very same rule name already exists. That was not the case, though. The same error will appear if you configure a WAF rule (different name) with a domain (virtual host which apache checks for based on SNI) which already exists in another rule. It's poor design in Webadmin.

Ah ok, I didn_t notice that before.

I agree, that this is no good design, then.