Remote server forcibly closed the web socket: Session Closed

Ignition
1

Hello,

I have two Ignition gateways: the first is Ignition Edge on my local machine, and the second is a standard Ignition instance on a remote server.

I have set up a network connection between the two, with Ignition Edge configured to connect to the remote Ignition gateway. Both gateways are accessible from each other; I can access their respective configuration web portals without issues.

Firewall rules are configured to allow all traffic, and I can successfully ping each gateway from the other.

However, I'm encountering an issue where Ignition Edge fails to connect to the remote Ignition gateway, resulting in the following error: Remote server forcibly closed the web socket: Session Closed. This connection worked during the initial setup but has since stopped functioning.

Below is a screenshot for reference:

Screenshot 2024-09-12 152635

On my Edge Gateway, I see the following log:

MetroWebSocket | 12Sep2024 15:33:11 | -> outgoing local='edge' remote='ignition' method=onClose: Remote server forcibly closed the web socket: Session Closed

And on my Ignition Gateway, I see these logs:

|12Sep2024 15:36:41|[100] edge connection status has been updated from Faulted to Shutdown: Remote is reconnecting|
|---|---|
|12Sep2024 15:36:31|[100] edge connection status has been updated from Initialized to Faulted: onClose has been called on web socket:Session Closed|
|12Sep2024 15:36:21|[100] edge connection status has been updated from Unknown to Initialized|

Has anyone encountered this issue before or knows how to resolve it?

2

That's usually a firewall in the network path. Some older firewalls simply don't support websockets, and newer ones might have websocket-specific inspection/filtering that breaks them. Ask your IT if there's been a change along the network path.