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

Signal Desktop unable to connect #896

Closed
BiLLou32 opened this issue Sep 16, 2016 · 15 comments
Closed

Signal Desktop unable to connect #896

BiLLou32 opened this issue Sep 16, 2016 · 15 comments

Comments

@BiLLou32
Copy link

BiLLou32 commented Sep 16, 2016

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

Bug description

When using Signal Desktop behind a firewall... I get the error message: "Disconnected".

Steps to reproduce

  • Start Signal Desktop behind a firewall
  • Load a conversation

Actual result: Signal displays the error message "Disconnected"
Expected result: Signal loading the conversation

Screenshots

chrome_2016-09-15_08-04-14

chrome_2016-09-15_08-34-47

Platform info

Operating System: Windows 10
Browser: Google Chrome 53.0.2785.113 m (64-bit)

Signal version: 0.22.2

Link to debug log

https://gist.github.com/011e995695c5748a3161c3e0c03d2590

@packeteer
Copy link

I'm having the same issue. I suspect Signal does not like our proxy server??

@BiLLou32
Copy link
Author

I discovered a really strange thing. When at work... Signal Desktop works fine on wifi but not on lan. Both requires a proxy.

@SeamusReynolds
Copy link

SeamusReynolds commented Jan 31, 2017

I'm having a similar problem with Signal Desktop, on my Mac, when I have a simple non-authenticated web proxy set up in my Mac's network configuration.

Attempting to navigate to site without proxy
withoutproxy
Attempting to navigate to site with proxy enabled
withproxy
Proxy settings
proxysettings

(Specific addresses and identifying info whited out)

@BiLLou32
Copy link
Author

It's working again at my work. I'm not sure why but I have the feeling it is related to the new version of Signal that came out the 14th of February.

Anyone else got this fixed recently?

@ekkis
Copy link

ekkis commented Jul 28, 2017

I'm having these issues too but I can't even tell what version of the app I'm running as the "About" box is grayed out. wtf? also there isn't an auto-update for it

@jcollum-cambia
Copy link

Yeah there really should be a version and an about box. How do I tell the devs what I'm running when I submit a bug report?

@scottnonnenberg
Copy link
Contributor

Your app version number is at the top of the debug log. If you submit one, we'll know what version it came from. Also, Electron has a little 'About Signal' dialog.

@je-vv
Copy link

je-vv commented Nov 1, 2017

Well, I was using the chromium app, and it was working fine with http_proxy, https_proxy and such, but as reading about chrome app getting deprecated, I moved into the Desktop SW, and it just doesn't connect under proxy... The debug log:

https://gist.github.com/fd46c0a31a3ea6ed0fc1a1034db8a4a8

the version: 1.0.33

@je-vv
Copy link

je-vv commented Nov 1, 2017

BTW, version 1.0.34 fails the same way (Disconnected):

https://gist.github.com/fab6f3e5cf98a8323f296aa96ba9ac18

@je-vv
Copy link

je-vv commented Nov 1, 2017

BTW, env vars set:

export use_proxy=on
export soap_use_proxy=${use_proxy}
export http_proxy="http://<proxy_server>:<proxy_port>"
export https_proxy=${http_proxy}
export ftp_proxy=${http_proxy}
export rsync_proxy=${http_proxy}
export no_proxy="localhost,127.0.0.1"

export USE_PROXY=${use_proxy}
export SOAP_USE_PROXY=${soap_use_proxy}
export HTTP_PROXY=${http_proxy}
export HTTPS_PROXY=${https_proxy}
export FTP_PROXY=${ftp_proxy}
export RSYNC_PROXY=${rsync_proxy}
export NO_PROXY=${no_proxy}

@je-vv
Copy link

je-vv commented Nov 1, 2017

uh, forgot, I'm running on Arch GNU/Linux up to date, as opposed to the OP running on windows, but getting the "Disconnected" error any ways...

@rbclark
Copy link

rbclark commented Nov 6, 2017

I seem to be running into a similar issue on Mac behind a corporate proxy. The Signal Chrome application has been working for me with no problems, however upon hearing the Chrome is removing desktop applications I went ahead and took the plunge over to the standalone Signal app. I exported my profile from the Chrome version and imported it into the standalone version, however I am unable to actually get the application to connect, it just stays saying Disconnected no matter how long I leave it to sit. I am running version 1.0.35. Below is what I believe is the relevant portion of the log:

INFO  2017-11-06T16:26:58.670Z fetchMessages
INFO  2017-11-06T16:26:58.671Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584
INFO  2017-11-06T16:26:58.745Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584 0 Error
INFO  2017-11-06T16:26:58.745Z {"name":"FetchError","message":"request to https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584 failed, reason: connect ECONNREFUSED 52.206.164.16:443","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}
INFO  2017-11-06T16:26:59.005Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]658
INFO  2017-11-06T16:26:59.287Z Conversation +[REDACTED]584 took 616 milliseconds to load
INFO  2017-11-06T16:26:59.340Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]658 0 Error
INFO  2017-11-06T16:26:59.340Z {"name":"FetchError","message":"request to https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]658 failed, reason: connect ECONNREFUSED 52.206.164.16:443","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}
INFO  2017-11-06T16:26:59.746Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584
INFO  2017-11-06T16:26:59.801Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584 0 Error
INFO  2017-11-06T16:26:59.802Z {"name":"FetchError","message":"request to https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584 failed, reason: connect ECONNREFUSED 52.206.164.16:443","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}
INFO  2017-11-06T16:27:00.339Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]658
INFO  2017-11-06T16:27:00.394Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]658 0 Error
INFO  2017-11-06T16:27:00.394Z {"name":"FetchError","message":"request to https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]658 failed, reason: connect ECONNREFUSED 52.206.164.16:443","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}
INFO  2017-11-06T16:27:00.396Z getProfile error: Error
    at ajax (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:37557:25)
    at TextSecureServer.ajax (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:37601:20)
    at TextSecureServer.getProfile (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:37649:25)
    at MessageSender.getProfile (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:39938:28)
    at getProfile (file:///Applications/Signal.app/Contents/Resources/app.asar/js/models/conversations.js:852:37)
    at Function._.map._.collect (file:///Applications/Signal.app/Contents/Resources/app.asar/js/components.js:18474:24)
    at child.getProfiles (file:///Applications/Signal.app/Contents/Resources/app.asar/js/models/conversations.js:848:30)
    at child.throttledGetProfiles (file:///Applications/Signal.app/Contents/Resources/app.asar/js/components.js:19095:23)
    at child.onOpened (file:///Applications/Signal.app/Contents/Resources/app.asar/js/views/conversation_view.js:461:37)
    at triggerEvents (file:///Applications/Signal.app/Contents/Resources/app.asar/js/reliable_trigger.js:60:39)
INFO  2017-11-06T16:27:00.580Z done with status fetch
INFO  2017-11-06T16:27:00.580Z done with status fetch
INFO  2017-11-06T16:27:00.803Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584
INFO  2017-11-06T16:27:00.867Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584 0 Error
INFO  2017-11-06T16:27:00.867Z {"name":"FetchError","message":"request to https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]584 failed, reason: connect ECONNREFUSED 52.206.164.16:443","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}
INFO  2017-11-06T16:27:00.867Z getProfile error: Error
    at ajax (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:37557:25)
    at TextSecureServer.ajax (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:37601:20)
    at TextSecureServer.getProfile (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:37649:25)
    at MessageSender.getProfile (file:///Applications/Signal.app/Contents/Resources/app.asar/js/libtextsecure.js:39938:28)
    at getProfile (file:///Applications/Signal.app/Contents/Resources/app.asar/js/models/conversations.js:852:37)
    at Function._.map._.collect (file:///Applications/Signal.app/Contents/Resources/app.asar/js/components.js:18474:24)
    at child.getProfiles (file:///Applications/Signal.app/Contents/Resources/app.asar/js/models/conversations.js:848:30)
    at child.throttledGetProfiles (file:///Applications/Signal.app/Contents/Resources/app.asar/js/components.js:19095:23)
    at child.onOpened (file:///Applications/Signal.app/Contents/Resources/app.asar/js/views/conversation_view.js:461:37)
    at triggerEvents (file:///Applications/Signal.app/Contents/Resources/app.asar/js/reliable_trigger.js:60:39)
INFO  2017-11-06T16:27:00.868Z done with status fetch

@Bairnsfather
Copy link

Bairnsfather commented Nov 7, 2017

Signal Desktop 1.0.35 new install on macOS 10.12.6 (16G1036).

I had to turn DNSCrypt Proxy off in order for Signal to work properly.
https://github.com/alterstep/dnscrypt-osxclient

Running normally, with DNSCrypt Proxy on, I was able to see the QR Code on the desktop version and begin the pairing process although it seemed buggy with long hangs on the iOS client (2.18.0.9 on iOS 9).

Eventually my desktop showed up in the iOS Linked Devices list. But none of my contacts showed up in the desktop app. Searching the issues here lead me to think about my use of DNSCrypt, which I then figured I would test by disabling it.

Disabling DNSCrypt enabled Desktop Signal to load my contacts, previously there was just empty space.

I will now turn DNSCrypt back on and whitelist textsecure-service.whispersystems.org and the amazonaws.com domain too. Ok. Seems to work for me now.

There definitely seems to be an issue with proxies. Hope this helps.

@je-vv
Copy link

je-vv commented Nov 9, 2017

Well, I'm using 1.0.35 on Arch GNU/Linux, and the problem persists. I don't use DNSCrypt at all...

I'm specifying the proxy through env. vars. (already posted) for the any applications supporting them, or applications configurations if they don't look into the env. vars...

No luck yet...

@scottnonnenberg
Copy link
Contributor

I'm closing this in favor of #1632

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

No branches or pull requests

9 participants