Local webblocker failover

Steve_ESteve_E
in Firebox - Subscription Services

I use a local webblocker server with a hot spare.

I dont see a way to auto failover if the the working vm is unavailable.

Is there a way?

Comments

  • HeroHero
    https://www.watchguard.com/help/docs/help-center/en-US/content/en-us/Fireware/services/webblocker/webblocker_define_adv_options_c.html
  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @Steve_E

    For local webblocker servers, the system should connect to the first available one on the list. So long as it can maintain a TCP connection, and it gets responses, it will stay with that server.

    If both servers are listed in your on-premise webblocker config, that's all you should need, provided they're both up and responding to queries.

    -James Carson
    WatchGuard Customer Support

  • Steve_ESteve_E

    When you say list, you mean the list. right?

    pm > subscription service > webblocker > configure > global settings

    Anywhere else?

  • Steve_ESteve_E

    @Hero said:
    https://www.watchguard.com/help/docs/help-center/en-US/content/en-us/Fireware/services/webblocker/webblocker_define_adv_options_c.html

    Thanks for the link

    What I cant find is a "server timeout" setting to "failover"

    If the server checked in the proxy policies stops working, I have to manually change it in each policy

  • james.carsonjames.carson Moderator, WatchGuard Representative

    That action is per webblocker policy. If you use the same webblocker policy for several policies, you only need to update it once.

    Each of your webblocker policies will have a unique name. If you're using a policy that is colored blue, it's a default policy that can't be edited, and you will need to clone it or make your own to save.

    -James Carson
    WatchGuard Customer Support

  • Steve_ESteve_E

    Problem is when the selected webblocker server on web policies fail, the other isnt used

    All I see in the traffic gui are timeouts, nothing about failing over to the other server

  • Steve_ESteve_E

    @james.carson

    For local webblocker servers, the system should connect to the first available one on the list. So long as it can maintain a TCP connection, and it gets responses, it will stay with that server.

    If both servers are listed in your on-premise webblocker config, that's all you should need, provided they're both up and responding to queries.

    If the list is here:

    pm > subscription service > webblocker > configure > global settings

    then failover doesnt work at all

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @Steve_E
    If you're experiencing an issue with webblocker failover, I suggest opening a support case so we can assist you.

    There haven't been any instances of a complete webblocker cloud failure in recent memory, so if you're experiencing issues with webblocker there may be something else potentially causing an issue.

    -James Carson
    WatchGuard Customer Support

Sign In to comment.