Signal-desktop: Signal desktop windows client will not connect
Signal desktop client will not connect
- [X ] I have searched open and closed issues for duplicates
Bug description
Signal Desktop client will not connect
Windows 7 Enterprise
Only one day after migrating to the desktop version (from Chrome) without issue, the program remains "disconnected." I am receiving Signal messages on my phone and through the browser plugin, just not the desktop client.
Steps to reproduce
- Open Signal
2."Disconnected: Attempting reconnect in 60 seconds"
Screenshots
Platform info
Signal version:
Operating System:
Win7 Enterprise SP1.
Linked device version:
https://gist.github.com/eae38b6a63bd30e2a862ff0d49029aa5
Link to debug log
https://gist.github.com/anonymous/28573934f6857b168ee135e4fda7726f
ajlynch
All 21 comments
Now cannot use chrome plugin after launching the migration tool. Cannot find chrome extension in web store.
ajlynch
on 6 Feb 2018
It looks like you're behind a proxy of some kind, since I'm seeing certificate verification failures in your log. You can use the HTTPS_PROXY environment variable to try out our Beta proxy support.
scottnonnenberg
on 6 Mar 2018
Using the HTTPS_PROXY environment variable works fine. The down-side is that you manually have to change it when using a different or a non-proxied network (when working from home for example).
jnasm
on 12 Mar 2018
Please improve signal proxy setting support.
signal always can not connect .
cnmade
on 26 Mar 2018
With the Signal beta, one can set proxy environment variables which will allow Signal to use the proxy
Right click on My Computer and select Properties. Then Advanced System Settings > Environment Variables
Set up the following variables
HTTPS_PROXY
HTTP_PROXY
http_proxy
https_proxy
All pointing to your proxy http://proxy.server.com:port/
Seems to be working well on my corporate system
skulumani
on 9 Aug 2018
Right click on My Computer and select Properties. Then Advanced System Settings > Environment Variables
I can not change these settings as I do not have administrator privilege. Why not use a settings file in the program folder? It could be so easy!
loefflerc
on 18 Sep 2018
signaldesktop[120fb9ba84bd3e184c59916eef766902].log
I am not using a proxy, but an enterprise tool called ZScaler seems to be the issue. This workstation was rid of it until recently, and now Signal Desktop fails to connect.
ajlynch
on 26 Sep 2018
@ajlynch Looking at the debug log, ZScaler may be doing man-in-the-middle SSL termination, since the certificate is incorrect. Even if you do get the proxy set up properly, Signal Desktop doesn't support proxies which do that.
scottnonnenberg-signal
on 26 Sep 2018
I run into the same issue. Recently my company added man-in-the-middle SSL termination to scan HTTPS connections for viruses. With this change I can no longer use Signal from the company network.
I looked into the Signal code. The connection seems to be established here:
https://github.com/signalapp/Signal-Desktop/blob/master/js/modules/web_api.js#L146
I think, the library supports an additional request option rejectUnauthorized which is true by default.
Would it be possible to parse an additional environment variable (e.g. HTTPS_ALLOW_UNAUTHORIZED) which would set the rejectUnauthorized option to false? The changes to Signal should be minimal but I am not sure how severe the security hole is that one would add. The end-to-end message encryption should not be affected by such a change.
rettenbs
on 21 Jan 2019
I run into the same issue. Recently my company added man-in-the-middle SSL termination to scan HTTPS connections for viruses. With this change I can no longer use Signal from the company network.
Same here, using Fortigate SSL Inspection. https://cookbook.fortinet.com/why-you-should-use-ssl-inspection/
So with that inspection the application is not usable anymore. Using here KDE-Neon 18.04.
boospy
on 28 Feb 2019
I found a workaround. There is an environment variable you can set to disable SSL verification in node: NODE_TLS_REJECT_UNAUTHORIZED=0
rettenbs
on 29 Mar 2019
Setting NODE_TLS_REJECT_UNAUTHORIZED is no longer working in 1.24.0 because of https://github.com/signalapp/Signal-Desktop/commit/6cf4f19317703d2bba16f63be2e552eaeba2a79d
rettenbs
on 17 Apr 2019
For anyone wondering how to easily configure signal to use a proxy, just create a new shortcut and paste the following command to startup Signal with the required proxy environments.
C:\Windows\System32\cmd.exe /c "SET http_proxy=http://127.0.0.1:3128 && SET https_proxy=http://127.0.0.1:3128 && START /D ^"C:\Users\<user>\AppData\Local\Programs\signal-desktop^" Signal.exe"
lukeb2e
on 8 Jul 2019
I have the same problem. But in addition to SSL scanning our proxy requires basic authentication. The environment variable https_proxy is set correctly - which is indeed not the best way to provide authentication data. But this works for other applications well; unfortunately not for Signal.
tolot27
on 16 Oct 2019
You can use a local proxy which uses your local upstream proxy. On windows I can recommend https://github.com/genotrance/px - it can use kerberos to authenticate with your proxy. That way you can configure your http(s)_proxy to use localhost.
lukeb2e
on 16 Oct 2019
I found a workaround. There is an environment variable you can set to disable SSL verification in node:
NODE_TLS_REJECT_UNAUTHORIZED=0
Didn't work for me :(
In fact, if I enable the proxy env variable, it crashes immediately. If I don't, it takes its time to fail.
gilsanx
on 28 Oct 2019
With the Signal beta, one can set proxy environment variables which will allow Signal to use the proxy
Right click on My Computer and select Properties. Then Advanced System Settings > Environment Variables
Set up the following variables
HTTPS_PROXY
HTTP_PROXY
http_proxy
https_proxyAll pointing to your proxy http://proxy.server.com:port/
Seems to be working well on my corporate system
I followed your instructions and it works.
but you need just lower- or uppercase env to set.
TheRojam
on 3 Mar 2020
I am on version v1.39.4 & setting environment variables doent work. Any other tricks to get it to work behind a corporate proxy?
subashp
on 8 Jan 2021
Same as above. Using v1.39.5 and with corportate solution, zscaler, on MacOSX Signal will not connect.
vaktadmin
on 15 Jan 2021
Will not connect on v1.39.5 for Windows 10
michaeldrrc
on 15 Jan 2021
There are problems in connecting and sending messages:
WARN 2021-01-15T15:35:24.027Z registerForActive: Failed to to refresh remote config. Code: 502
INFO 2021-01-15T15:35:25.080Z SQL channel job 214 (updateConversations) succeeded in 33ms
INFO 2021-01-15T15:35:27.380Z Sending a keepalive message
INFO 2021-01-15T15:35:28.534Z Sending a message with 0 mentions and 0 placeholders
INFO 2021-01-15T15:35:28.536Z loadSession {"encodedAddress":"[REDACTED]65b.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:28.536Z loadSession {"encodedAddress":"[REDACTED]65b.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:28.537Z loadSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:28.537Z loadSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:28.537Z loadSession {"encodedAddress":"[REDACTED]65b.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:28.537Z loadSession {"encodedAddress":"[REDACTED]65b.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:28.538Z loadSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:28.538Z loadSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:28.550Z storeSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:28.551Z storeSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:28.555Z loadSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:28.556Z loadSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:28.557Z PUT https://textsecure-service.whispersystems.org/v1/messages/[REDACTED]a43 (unauth)
ERROR 2021-01-15T15:35:29.082Z PUT https://textsecure-service.whispersystems.org/v1/messages/[REDACTED]a43 502 Error
ERROR 2021-01-15T15:35:29.085Z 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 new ReplayableError ([REDACTED]\app.asar\ts\textsecure\Errors.js:19:19)
at new SendMessageNetworkError ([REDACTED]\app.asar\ts\textsecure\Errors.js:69:9)
at [REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:172:23
at async OutgoingMessage.sendToIdentifier ([REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:387:13)
Original stack:
HTTPError: promiseAjax: error response; code: 502
at makeHTTPError ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:389:15)
at [REDACTED]\app.asar\ts\textsecure\WebAPI.js:354:24
Original stack:
Error
at _outerAjax ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:384:21)
at _ajax ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:532:20)
at Object.sendMessagesUnauth ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:886:20)
at OutgoingMessage.transmitMessage ([REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:159:35)
at [REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:247:29
at async OutgoingMessage.sendToIdentifier ([REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:387:13)
INFO 2021-01-15T15:35:29.127Z SQL channel job 218 (createOrUpdateSessions) succeeded in 70ms
INFO 2021-01-15T15:35:29.276Z SQL channel job 219 (saveMessage) succeeded in 149ms
INFO 2021-01-15T15:35:29.276Z SQL channel job 221 (getLastConversationActivity) succeeded in 150ms
INFO 2021-01-15T15:35:29.280Z SQL channel job 220 (getLastConversationPreview) succeeded in 154ms
INFO 2021-01-15T15:35:30.152Z SQL channel job 224 (updateConversations) succeeded in 35ms
INFO 2021-01-15T15:35:31.250Z Sending a message with 0 mentions and 0 placeholders
INFO 2021-01-15T15:35:31.250Z loadSession {"encodedAddress":"[REDACTED]65b.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:31.250Z loadSession {"encodedAddress":"[REDACTED]65b.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:31.251Z loadSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:31.251Z loadSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:31.251Z loadSession {"encodedAddress":"[REDACTED]65b.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:31.251Z loadSession {"encodedAddress":"[REDACTED]65b.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:31.251Z loadSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:31.251Z loadSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:31.259Z storeSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:31.260Z storeSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:31.262Z loadSession {"encodedAddress":"[REDACTED]a43.1","id":"[REDACTED]65b.1"}
INFO 2021-01-15T15:35:31.263Z loadSession {"encodedAddress":"[REDACTED]a43.2","id":"[REDACTED]65b.2"}
INFO 2021-01-15T15:35:31.263Z PUT https://textsecure-service.whispersystems.org/v1/messages/[REDACTED]a43 (unauth)
ERROR 2021-01-15T15:35:31.403Z PUT https://textsecure-service.whispersystems.org/v1/messages/[REDACTED]a43 502 Error
ERROR 2021-01-15T15:35:31.404Z 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 new ReplayableError ([REDACTED]\app.asar\ts\textsecure\Errors.js:19:19)
at new SendMessageNetworkError ([REDACTED]\app.asar\ts\textsecure\Errors.js:69:9)
at [REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:172:23
at async OutgoingMessage.sendToIdentifier ([REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:387:13)
Original stack:
HTTPError: promiseAjax: error response; code: 502
at makeHTTPError ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:389:15)
at [REDACTED]\app.asar\ts\textsecure\WebAPI.js:354:24
Original stack:
Error
at _outerAjax ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:384:21)
at _ajax ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:532:20)
at Object.sendMessagesUnauth ([REDACTED]\app.asar\ts\textsecure\WebAPI.js:886:20)
at OutgoingMessage.transmitMessage ([REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:159:35)
at [REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:247:29
at async OutgoingMessage.sendToIdentifier ([REDACTED]\app.asar\ts\textsecure\OutgoingMessage.js:387:13)
INFO 2021-01-15T15:35:31.578Z SQL channel job 227 (saveMessage) succeeded in 138ms
INFO 2021-01-15T15:35:31.579Z SQL channel job 228 (getLastConversationPreview) succeeded in 139ms
INFO 2021-01-15T15:35:31.580Z SQL channel job 229 (getLastConversationActivity) succeeded in 140ms
INFO 2021-01-15T15:35:31.787Z SQL channel job 232 (createOrUpdateSessions) succeeded in 26ms
INFO 2021-01-15T15:35:32.280Z SQL channel job 233 (updateConversations) succeeded in 31ms
igvk
on 15 Jan 2021
Related issues
jeremymasters
路
3Comments
cmdrogogov
路
3Comments
demux4555
路
3Comments
vincenzopalazzo
路
3Comments
bcsga
路
3Comments
Most helpful comment
With the Signal beta, one can set proxy environment variables which will allow Signal to use the proxy
Right click on My Computer and select Properties. Then Advanced System Settings > Environment Variables
Set up the following variables
HTTPS_PROXY
HTTP_PROXY
http_proxy
https_proxy
All pointing to your proxy http://proxy.server.com:port/
Seems to be working well on my corporate system