WebSocket connection errored out

Ignition
1

Hello,

I am getting Web socket disconnected, Web socket connection errored out continuous error in gateway console log. Please help me to resolve these errors.

We are using Ignition version 8.1.25 (b2023021409)
Windows Server 2019 | amd64

java.nio.channels.ClosedChannelException: null

at org.eclipse.jetty.websocket.core.internal.WebSocketSessionState.onEof(WebSocketSessionState.java:169)

at org.eclipse.jetty.websocket.core.internal.WebSocketCoreSession.onEof(WebSocketCoreSession.java:253)

at org.eclipse.jetty.websocket.core.internal.WebSocketConnection.fillAndParse(WebSocketConnection.java:482)

at org.eclipse.jetty.websocket.core.internal.WebSocketConnection.onFillable(WebSocketConnection.java:340)

at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)

at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:558)

at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:379)

at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:146)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)

at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:416)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:385)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:272)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.lambda$new$0(AdaptiveExecutionStrategy.java:140)

at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:934)

at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1078)

at java.base/java.lang.Thread.run(Unknown Source)

image
image1218×872 72.7 KB

2

Can you upload your actual logs? It seems like an issue either on the user agent (browser or mobile device or workstation), or originating on somewhere on the network outside of Ignition; the persistent websocket is closing abruptly, and so the gateway is logging these messages indicating the websocket 'disappeared' from its perspective.

3

Hello @PGriffith
thank you for the looking into it. Please find attached Gateway logs.
Ignition-FisServer_Ignition_logs_20230420-2107.zip (4.7 MB)

Background:
We have Ignition GW located at Cloud (somewhere in USA), connected with tosibox with fix IP address. We have purchased one domain example.com from GoDaddy, we have DNS forwarded to tosibox IP. So when where we get request on example.com we directed to the main dashboard (perspective project) page located on Ignition GW. We are located in the India and we can access the projects located on Ignition gateway using example.com. However, our client located in USA cannot access perspective dashboard and other project from his laptop (any browser) and nor from his phone.

IA advised before that it need SSL certificate, hence we have purchased and configured on GoDaddy and Ignition (Web server > SSL configuration) as well.

We are getting these web socket disconnected errors, from when configured above setup.

4

Well, doesn't really offer any more information. Whatever's happening to the websocket is happening outside of the gateway. Investigate with your IT team, try different devices, etc. It's not SSL related; it's just a plain old network failure, as far as I can tell. Something is hiccuping and causing the gateway's outbound half of the websocket to think there's nothing available on the other end.

5

Ok. Thank you we will check with our IT team.

6

Did you end up finding the solution to this issue? We are having the same issue with the Websocket closing and clients hanging.

1 Like
7

Some commercial firewall products have been reported to close websockets unconditionally after a short time (like 30 minutes). If your logged errors are the same, you need your IT to investigate.

1 Like
8

Unfortunately there are no firewalls between the server and clients. Server sits in the server room, connected to clients in the production floor via Meraki switches. IT have looked into it and suggested it isn't an 'IT / Infra' issue but I'll request they look again.

The logs display these errors and after this the clients in the field became unresponsive / hang needing a session restart, on the laptop this doesn't happen though. Could this is something to do with idle timeouts, power saving?

9

Quite possible. Tablet or mobile clients? Some have aggressive power saving behaviors that break the network connection.

See if you can turn off those power saving behaviors in the device settings. Or exempt the Perspective app.