textsecure gateway stops because of websocket failure

[Hetti]

I have encountered, that the textsecure server in gateway mode stopped after some time with the error unexpected EOF because of some websocket failure. The logging level is already in debug.

I selfcompiled the binary as stated in https://morph027.gitlab.io/signal-web-gateway/installation/standalone/

From the system log:

level=debug msg="[textsecure] Received websocket pong message"
level=debug msg="[textsecure] Sending websocket ping message"
level=debug msg="[textsecure] Received websocket pong message"
level=debug msg="[textsecure] Sending websocket ping message"
level=debug msg="[textsecure] Received websocket pong message"
level=debug msg="[textsecure] Sending websocket ping message"
level=debug msg="[textsecure] Received websocket pong message"
level=error msg="websocket: close 1006 (abnormal closure): unexpected EOF"

Any Ideas?

Cheers.

[Hetti]

I am running now the latest version and now this error triggers the stop of the tool:

level=debug msg="[textsecure] Websocket UnexpectedCloseError: websocket: close 1005 (no status)"
level=error msg="websocket: close 1005 (no status)"

Cheers.

[nanu-c]

Hey Hetti, actually we have the same, but only with cli and not as library. Sometimes this is signal-server hickups sometimes something different. But, we can do a debugging session at metalab :)