-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Standalone Signal-Desktop has problems connecting through a proxy #1632
Comments
Same here. Environment variables set for my company proxy in Windows 8.1, also proxy set in Internet Options. No QR Code: fails to connect. |
I also configured a proxy and Signal Desktop does not connect. |
Confirmation, no signal desktop behind the proxy ... tried linux and windows v1.0.34 You shouldn't have disabled the chrome-app before fixing this ... anyways hope to see a working version soon. |
Signal Desktop on Chrome is absolutely still useable. If you've already exported and imported to Signal Desktop Standalone, you can remove the Chrome version and reinstall from scratch. This issue is on my list. |
Same issue on Windows 10. |
Happy to be guinea pig tester on this |
Still valid for v1.0.38 |
Experiencing this on macOS 10.12.6. |
The beta build installed today has support for using a proxy specified in environment variables - |
This is great news... There 2 new dependencies to take into account when using next release, or when testing the beta release: https://github.com/Rob--W/proxy-from-env Which can be confirmed on package.json, the commit added:
Is it possible to somehow publish those new requirements? Just so people and/or distribution developers take that into account... Thanks a lot ! |
@scottnonnenberg, I saw your comment on the PR:
I'm on macOS Sierra, and while the proxies generally are system-wide and transparent, each program still needs to have built-in support for reading them. Signal does not currently work for me when I'm behind a proxy. I do have environment variables set in my terminal, but those are only available within a terminal session. |
@gfairchild for now it would be useful to determine whether those environment variables work for you, by running from the command line. Just gotta reach into that app to find the executable. :0) |
Yeah, that'll certainly be a start. That should work. I'm not in a place where I can compile/test the beta. Is there by chance a pre-built beta for macs that I could use to test? |
You can find the latest prebuilt beta windows install here: |
Just tried the current beta, and it doesn't appear to be working. I see this when I try to setup a new install: I tried both launching the app natively and from the command line, where I have an
|
@gfairchild Glad to see that you're trying out the beta. You can either provide |
You mean provide one of those as an argument when launching? So something like this?:
? |
They're environment variables, so you can set them with |
Ah, sorry, I didn't make it clear, but I do have those set. If you look at the very first line of my big blob, I'm outputting my current proxy environment variables. So |
Yes, and you need to add either |
Ahhhhhh, gotcha. I'll try that.... |
Adding
And I see similar results even if I specify |
@gfairchild Well, the good news is that we're attempting to use the proxy. Maybe the right thing is to take this offline - feel free to contact me directly. |
Sounds good. Just pinged you on Twitter. |
+1 ... Signal doesn't work on my work PC because the company proxies all our traffic. |
Doesn't work when tethering to a phone for me, either. Only thing I can assume is that the iPhone personal hotspot acting as a proxy triggers the same issue. |
I agree that this is pretty unreasonable, but this does work for us: |
I still maintain that until Signal bakes the proxy configuration into the app, it has no hope of any sort of adoption. Currently, what it has is a nice beta-level demonstration of the ability to work with a proxy, but that’s it. This issue shouldn’t be closed until proxy support is added to the UI and made accessible to the general user base. |
@gfairchild you do realize Signal has over 40 million users right? I think your 'no hope of any sort of adoption' comment is slightly dellusional. |
The service as a whole has that many users, but I’m clearly referring to the desktop app, which I absolutely promise you does not have that many users. |
Any updates on this? Can we hope with a proxy configuration in the UI in the near future? Workarounds didn't work for me and I don't want to use the app by a workaround. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still relevant.
|
The fact that no one have worked on this issue doesn’t change its relevance. It is still relevant, even more in a working environment. |
I'm interested in contributing to this, should I open a new issue, or should I just point the PR here? I'm thinking the UI should be similar to Telegram's proxy setting flow, but would that cause legal issues? |
I don't think there would be legal issues if the gui concept is in some sort similar |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I can only repeat that statement |
Well, we do really need some sort of solution to this. Do not close this Issue until it is completed |
Today I tried the following bat Script:
And I was able to connect through the proxy and use Signal (Don't know if a sysadmin will cut my throat for doing this 😄). |
Workaround still works on: version 6.40.0 |
Setting
I think this has been properly resolved? |
We indeed made some changes to our proxy code and hope that they work better now! Thanks for confirming it. |
I think documentation need to be updated.
Right now somebody wanting to configure a proxy needs to find this issue and the right comment to figure out the right variable.
The official website has a page discussing proxy support and includes details for iOS and Android, but for Signal Desktop it only includes a vague statement about focus being elsewhere.
|
Just wanted to say that this worked for me! I was using PDAnet+ but hide tethering usage stopped working. Maybe because of Android 14 (Pixel 7 Pro owner). I reached out to the developer to see if this can be fixed. I switched to NetShare Pro and since it uses a proxy 192.168.49.1:8282 Signal Desktop stopped working for me. After several trial and errors I was able to get Signal Desktop on Windows to work with NetShare app. I had to use the Beta since the standard version refused to connect. Also because Signal Beta.exe has a space between the two words I had to use "" to make it work. Maybe using a dash or an underscore in the app name would have been better since signal-desktop-beta avoids spacing anyway. I'm happy this is working now on my Windows! Great work team! |
Bug description
I've set the
http_proxy
andhttps_proxy
variables on my system. Sognal-Desktop however seems to ignore them. I cannot get a connection to get the QR code. An strace says:Which is clearly not the proxy.
Steps to reproduce
Actual result: No QR code, Server not reachable
Expected result: QR Code, normal operation.
Platform info
Operating System: GNU/Linux
Browser: Chrome
Signal version: v1.0.34
Link to debug log
https://gist.github.com/0bbe048ee23480d58dae34f0b07e16fe
The text was updated successfully, but these errors were encountered: