-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Comments
I'm having the same issue. I suspect Signal does not like our proxy server?? |
I discovered a really strange thing. When at work... Signal Desktop works fine on wifi but not on lan. Both requires a proxy. |
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? |
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 |
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? |
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. |
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 |
BTW, version 1.0.34 fails the same way (Disconnected): |
BTW, env vars set: export use_proxy=on export USE_PROXY=${use_proxy} |
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... |
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:
|
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. 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. |
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... |
I'm closing this in favor of #1632 |
Bug description
When using Signal Desktop behind a firewall... I get the error message: "Disconnected".
Steps to reproduce
Actual result: Signal displays the error message "Disconnected"
Expected result: Signal loading the conversation
Screenshots
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
The text was updated successfully, but these errors were encountered: