Signal-desktop: Disconected: Check your network connection

Created on 22 Mar 2019 · 17Comments · Source: signalapp/Signal-Desktop

[x] I have searched open and closed issues for duplicates

Bug Description

Steps to Reproduce

I updated to the new Signal Desktop version 1.23.0
Upon re-launching after the update, Signal reported it had no network connection.
All other apps on the computer have network access, Signal was working prior to update, however is no longer working after the update.

Actual Result:

Expected Result:

Screenshots

Platform Info

Signal Version:

v1.23.0
Operating System:

Win10 Pro, build 1803
Linked Device Version:

4.35.1

Link to Debug Log

https://debuglogs.org/ac8b39efbd402fa7b22f80ba27af1b302d5b279746c4240387a4cfca5718941b

Source

alternativesurfer

👍2

Most helpful comment

All: When you're experiencing this, please go to View -> Toggle Developer Tools and put this into the console: navigator.onLine - what value does it return?

Our online/offline detection seems to be confused by sleep/wake events.

scottnonnenberg-signal on 22 Mar 2019

👍2 😕1

All 17 comments

I just had this as well. I put my report here since it was the same as what I had, but this is basically the same root I think. https://github.com/signalapp/Signal-Desktop/issues/2569
https://debuglogs.org/429f438e483d4eb2643ce14ef17c71b349be37a05d9e0d73bc9980aa455cea5c

jeremymasters on 22 Mar 2019

👍2

All: When you're experiencing this, please go to View -> Toggle Developer Tools and put this into the console: navigator.onLine - what value does it return?

Our online/offline detection seems to be confused by sleep/wake events.

scottnonnenberg-signal on 22 Mar 2019

👍2 😕1

I experienced the same issue (on a machine without sleep/wakeup). But for me it felt like some server-related problem.
It started with sending a message, which instantly failed and showed error 502 in message details:

The server rejected our query, please file a bug report.

ERROR 2019-03-22T19:44:48.085Z PUT https://textsecure-service.whispersystems.org/v1/messages/+[REDACTED]473 502 Error
ERROR 2019-03-22T19:44:48.087Z Message.saveErrors: Failed to create or send message SendMessageNetworkError: The server rejected our query, please file a bug report. (original: promiseAjax: error response; code: 502)
    at SendMessageNetworkError.ReplayableError (file:///C:/Users/[REDACTED]/AppData/Local/Programs/signal-desktop-beta/resources/app.asar/js/libtextsecure.js:32:13)
    at new SendMessageNetworkError (file:///C:/Users/[REDACTED]/AppData/Local/Programs/signal-desktop-beta/resources/app.asar/js/libtextsecure.js:83:21)
    at promise.catch.e (file:///C:/Users/[REDACTED]/AppData/Local/Programs/signal-desktop-beta/resources/app.asar/js/libtextsecure.js:39877:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
Original stack:
HTTPError: promiseAjax: error response; code: 502
    at HTTPError ([REDACTED]\app.asar\js\modules\web_api.js:377:13)
    at resultPromise.then.result ([REDACTED]\app.asar\js\modules\web_api.js:333:13)
    at process._tickCallback (internal/process/next_tick.js:68:7)
Original stack:
Error
    at _outerAjax ([REDACTED]\app.asar\js\modules\web_api.js:371:19)
    at _ajax ([REDACTED]\app.asar\js\modules\web_api.js:472:14)
    at Object.sendMessagesUnauth ([REDACTED]\app.asar\js\modules\web_api.js:801:14)
    at OutgoingMessage.transmitMessage (file:///C:/Users/[REDACTED]/AppData/Local/Programs/signal-desktop-beta/resources/app.asar/js/libtextsecure.js:39851:29)
    at Promise.all.then.jsonData (file:///C:/Users/[REDACTED]/AppData/Local/Programs/signal-desktop-beta/resources/app.asar/js/libtextsecure.js:39992:23)

https://debuglogs.org/9d458dfc4f41885a4a5d324a0dd034813e17422c641e1ee67decd1dd4f747e6f

During the same time, I haven't been able to send messages using the Android app.
See also these reddit posts:
https://www.reddit.com/r/signal/comments/b473bb/signal_servers_down/

The issue has been resolved after ~10-20 min.

minnmann on 22 Mar 2019

For reference, this is the time this happened for me in MDT

jeremymasters on 23 Mar 2019

10:16 am MDT is the exact same time it happened to me (5:16 pm MET) (found the corresponding second log entry with timestamp ID 1553271374265).

minnmann on 23 Mar 2019

Same issue.

Signal version: v1.32.1
Operating system: Chrome OS Version 81.0.4044.62 (Official Build) beta (64-bit)

From the log:

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Signal/1.32.1 Chrome/80.0.3987.134 Electron/8.0.3 Safari/537.36 node/12.13.0 env/production
...
INFO  2020-03-17T00:02:27.568Z Sending a keepalive message
INFO  2020-03-17T00:03:03.152Z websocket closed 1006 Connection dropped by remote peer. calledClose: 
INFO  2020-03-17T00:03:03.158Z GET https://textsecure-service.whispersystems.org/v1/devices
INFO  2020-03-17T00:03:03.158Z Cycling agent for type -auth
ERROR 2020-03-17T00:03:04.309Z GET https://textsecure-service.whispersystems.org/v1/devices 502 Error
ERROR 2020-03-17T00:03:04.310Z background onError: HTTPError: promiseAjax: error response; code: 502
    at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:380:13)
    at [REDACTED]/app.asar/js/modules/web_api.js:336:13
Original stack:
Error
    at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:374:19)
    at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:483:14)
    at Object.getDevices ([REDACTED]/app.asar/js/modules/web_api.js:676:14)
    at MessageReceiver.onclose (file://[REDACTED]/app.asar/js/libtextsecure.js:38455:8)
    at W3CWebSocket._dispatchEvent [as dispatchEvent] ([REDACTED]/app.asar/node_modules/yaeti/lib/EventTarget.js:107:17)
    at W3CWebSocket.onClose ([REDACTED]/app.asar/node_modules/websocket/lib/W3CWebSocket.js:228:10)
    at WebSocketConnection.<anonymous> ([REDACTED]/app.asar/node_modules/websocket/lib/W3CWebSocket.js:201:17)
    at WebSocketConnection.emit (events.js:210:5)
    at WebSocketConnection.handleSocketClose ([REDACTED]/app.asar/node_modules/websocket/lib/WebSocketConnection.js:389:14)
    at TLSSocket.emit (events.js:215:7)
ERROR 2020-03-17T00:03:04.312Z Top-level unhandled promise rejection: HTTPError: The server rejected our query, please file a bug report. (original: promiseAjax: error response; code: 502)

From the console:

[Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
_readFile @ /opt/Signal/resources/app.asar/node_modules/typo-js/typo.js:233

Uncaught (in promise) HTTPError: promiseAjax: error response; code: 502
    at HTTPError (/opt/Signal/resources/app.asar/js/modules/web_api.js:380:13)
    at /opt/Signal/resources/app.asar/js/modules/web_api.js:336:13
Original stack:
Error
    at _outerAjax (/opt/Signal/resources/app.asar/js/modules/web_api.js:374:19)
    at _ajax (/opt/Signal/resources/app.asar/js/modules/web_api.js:483:14)
    at Object.getDevices (/opt/Signal/resources/app.asar/js/modules/web_api.js:676:14)
    at MessageReceiver.onclose (file:///opt/Signal/resources/app.asar/js/libtextsecure.js:38455:8)
    at W3CWebSocket._dispatchEvent [as dispatchEvent] (/opt/Signal/resources/app.asar/node_modules/yaeti/lib/EventTarget.js:107:17)
    at W3CWebSocket.onClose (/opt/Signal/resources/app.asar/node_modules/websocket/lib/W3CWebSocket.js:228:10)
    at WebSocketConnection.<anonymous> (/opt/Signal/resources/app.asar/node_modules/websocket/lib/W3CWebSocket.js:201:17)
    at WebSocketConnection.emit (events.js:210:5)
    at WebSocketConnection.handleSocketClose (/opt/Signal/resources/app.asar/node_modules/websocket/lib/WebSocketConnection.js:389:14)
    at TLSSocket.emit (events.js:215:7)

navigator.onLine
true

norman-shulman on 17 Mar 2020

@norman-shulman How long did that persist?

scottnonnenberg-signal on 17 Mar 2020

It started sometime after I sent a message. The message was received, but I
only received the replies on my phone, not on the desktop. I finally shut
down the desktop app after several hours.

On Tue, Mar 17, 2020 at 12:35 PM Scott Nonnenberg notifications@github.com
wrote:

@norman-shulman https://github.com/norman-shulman How long did that
persist?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/signalapp/Signal-Desktop/issues/3250#issuecomment-600171537,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH53JNQZNM74FFES55PDWMLRH6RGNANCNFSM4HAPZXKA
.

norman-shulman on 17 Mar 2020

I am also seeing the "Disconnected - Check your network connection" error.

My debug log:
https://debuglogs.org/690499c816ed2245b803c48df7181d5120cbc3349c23817b6cdac024ea9ddc64

Possibly relevant lines:

WARN  2020-04-27T17:30:46.246Z Client is no longer authorized; deleting local configuration

INFO  2020-04-27T17:30:46.443Z Rotating signed prekey...
ERROR 2020-04-27T17:30:46.444Z rotateSignedPrekey error: TypeError: Cannot read property 'privKey' of undefined
    at Object.generateSignedPreKey (file://[REDACTED]/app.asar/js/libtextsecure.js:35553:31)
    at file://[REDACTED]/app.asar/js/libtextsecure.js:37741:35
ERROR 2020-04-27T17:30:46.444Z rotateSignedPrekey() failed. Trying again in five minutes

jlindgren90 on 27 Apr 2020

@jlindgren90 Please restart Signal Desktop, and it should ask you to re-link with your phone.

scottnonnenberg-signal on 27 Apr 2020

@jlindgren90 Please restart Signal Desktop, and it should ask you to re-link with your phone.

I did restart it already, and it didn't ask. Anyway, a messaging app that shows messages out-of-order (#2424) and randomly deauthenticates itself isn't reliable enough for my needs. I will be using Signal on my phone only from now on. It's too bad, since a reliable desktop app would be very convenient.

jlindgren90 on 27 Apr 2020

@jlindgren90 I understand that you're frustrated. Any information you can give us now will help us avoid these problems in the future. I expect that there's a reason for the unlink, for example, and I'd like to get to the bottom of it.

scottnonnenberg-signal on 28 Apr 2020

@jlindgren90 I understand that you're frustrated. Any information you can give us now will help us avoid these problems in the future. I expect that there's a reason for the unlink, for example, and I'd like to get to the bottom of it.

Sure. I appreciate the efforts. The full debug log is there, so hopefully that contains something that might be a clue. The other thing that could be relevant is that I recently updated the system from Ubuntu 19.10 to 20.04.

jlindgren90 on 28 Apr 2020

@jlindgren90 Unfortunately no, that log just tells us that the server now believes that we're unlinked. If you reinstalled SIgnal on your phone, or you hadn't started Signal Desktop in over 30 days, then you'd need to re-link.

scottnonnenberg-signal on 28 Apr 2020

👍1

Oh it unlinks after 30 days? That might be it, I don't think I had used it on that computer in a while.

jlindgren90 on 28 Apr 2020

confirm it now works as expected on 1.33.4

unlinked manually from phone for testing
after relink conversations appears as they where left, with the addiction of the warning about conv.history.
Preferences (notifications, menu bar...) are instead reset to default, but not applied until next restart of signal.
Not a big deal of course, but strange.

Lion-box on 28 Apr 2020

@Lion-box Can you enter a new bug for this 'loss of settings' bug? Also, a debug log would be really helpful, if you have one capturing the install of the new build, restart, and loss of settings. Thanks!

I'm going to close this bug. Thanks for verifying that our fix worked for you.

scottnonnenberg-signal on 28 Apr 2020

Was this page helpful?

0 / 5 - 0 ratings