Create a Post
Showing results for 
Search instead for 
Did you mean: 

Active Member of ClusterXL unable to reach

I was having this problem under R80.40, and upgraded to R81.10 and problem still exists.  The Active (call it B1) gateway is receiving an error Anti-Bot-Update Failed. Contract Entitlement check failed.  Could not reach ''. Check DNS and Proxy Configuration on gateway.

The Standby (call it B2) member has no errors.  Now, if I do a force failover between the two, B1 now has no errors after about 2 minutes, it is able to check, and B2 now gets the error.

I have explicit rules allowing the Cluster object, and each cluster member access to the internet via the required ports on both the Security ruleset and the Application ruleset.

What else can I check?


0 Kudos
1 Reply

Usually, it's the backup gateway that is problematic to reach the update servers, not the primary.
In any case, recommend a TAC case to assist: 

0 Kudos


Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events