ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Web Socket Connection Closed by Gateway

book

Article ID: 212687

calendar_today

Updated On:

Products

Web Isolation Threat Isolation Gateway

Issue/Introduction

The web socket messages from the browser developer tools show the connection starts, but is closed by the gateway after receiving the tab information.

Cause

There are no browser engines running on the gateway.

You can check this with the command

sudo docker ps | grep fireglass_engine

Resolution

Spin up the engines using the following command.

Note: If your deployment is sized differently, specify the intended number of engines instead of the default of 10

fgcli service set-engine-count 10