Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSocketConnection.readRequest timing out repeatedly and not reading any requests #1695

Closed
scottslewis opened this issue Jan 28, 2025 · 3 comments

Comments

@scottslewis
Copy link

This code:

  WebSocketRequestMessage request = getWebSocket().readRequest(timeout);

From line 293 of org.whispersystems.signalservice.api.SignalWebSocket class is not reading any messages and repeatedly timing out (timeout set to 60 seconds). This happens in both jsonRPC as well as signal-cli receive.

The url of the web socket is pointing to https://chat.signal.org

This is on 1/27/2025. It seems as if perhaps chat.signal.org is not responding as expected to signal-cli to these incoming requests.

Could be related to issure #1684 ?

@AsamK
Copy link
Owner

AsamK commented Jan 28, 2025

It's still working for me. Which signal-cli version are you using?
Maybe a proxy on the network interfering?

@scottslewis
Copy link
Author

It was working for me two weeks ago. I'm running in IDE for debugger and for mods on story support issue. Havent pulled in a bit, will do so today.

I dont think its proxy as it was working before without any network changes. And its timing out on network request. Something about websocket lib change? I havent updated that in a while.

@scottslewis
Copy link
Author

Updated to latest on master and is building and running ok now. Don't know what changed exactly, but something in my fork was apprently out of date. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants