ConfigServer Community Forum

If you want to make any changes to the block settings for something, you would do it in the corresponding configuration page for that app. CSF's settings are done directly through CSF's DA plugin. BFM's are "Administrator Settings" and then under the Security header. Ignoring the automated...

What? The guide for integrating BFM into CSF will, at the end, make it so ANY block that BFM does winds up being properly implemented as a block in CSF (and subsequently blocked by the firewall).

That is the CSF management plugin for Directadmin and is unrelated to this. Unless you specifically run scripts, such as the one that I linked, to tie BFM into CSF, the two will not work together. See: https://help.directadmin.com/item.php?id=527 It says you may use CSF or BFM on their own just fine...

Have you done anything to tie the two together or are you just running the two separately for now?

If the two are running separately, this guide would probably be your best bet.

You'll need to whitelist 85.10.199.177 in whatever sort of firewall interface SingleHop offers you and then also submit to them a ticket requesting to have that IP unblocked. For whatever reason, several server providers decided to add CSF's IP to their blocklists and the end result is this. You nee...

Seems the problem is finally resolved as two of our servers running CSF that also had the OVH firewall active were able to update

It appears that there are some IPs that are being filtered thorugh our VAC. We
are currently investigating the issue and will see to get back to you with
more informations as soon as we have them.

For the moment, we recommend to disable the OVH firewall.

At least it's some form of progress.

Bleh, my apologies. I was gone for the weekend and wasn't able to check OVH's response until earlier today. All they initially gave me was a generic "This is how to whitelist an IP", which is a localized band-aid solution at best. I reopened the ticket but we may need one of the CSF devs t...

It's tied to the mitigation component of the OVH firewall. If you either have the firewall enabled or toggled the mitigation mode from automatic to permanent, it will result in what we're currently experiencing. We've submitted a ticket to OVH regarding this so it should hopefully be resolved later ...