-
-
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
Unable to connect when running 7.2.0 (also random "crash") #6828
Comments
Same issue here at work Clients not updated to 7.2.0 connect just fine. |
Same issue here; Since Updating from 7.1.1 to 7.2 the proxy wont connect anymore. |
Error workaround: if you change the proxy settings from a fwdn to the ip-address the signal client can connect again! there seems to be a bug in the name resolution. a quick fix would be great! :-) |
i can confirm that this works! Thanks! |
Can confirm too. |
Can also confirm connection issue & temporary mitigation measure with https_proxy env var with Linux: ========= System info ========= |
Can also confirm that as of 7.2.0 (noticed this from Beta) that on Mac, proxies were an issue. Can also confirm that the workaround of using IP address instead of the domain appears to work. So does appear to be an issue with name resolution. |
This bug emphasizes the need for native proxy support. If native proxy support were added to the app, it'd be tested and bugs like this one would not likely be released in the wild. |
Me too! |
You can switch to using a pac file. It wasn't working before but it is now working. |
@TheNetworkIsDown I didn't think Signal was actually ready a |
@aureq Not sure what u mean. Unfortunately, there is no standard (like RFC) concerning the content of those env variables. It's not even clear if the variable name themselves should be in upper or lower case. From many apps I know that proxy support, especially (interactively) authenticated proxy or PAC, is abyssimal. Simply specifying an IP or hostname is the absolute minimum that should always work. |
@TheNetworkIsDown I agree with your latest sentence. Some have suggested to use an IP address instead of a hostname, and this is what I tried to set in my |
@aureq No, the workaround is setting an IP address in the env variable directly. The pac file works either way. In case you use a pac file and it "doesn't work", what do the logs say? What does pactester say? If it "doesn't work" you should try to find out why it "doesn't work" or at least provide information what you did exactly so that someone can help. |
@aureq well if you think the pac file "doesn't work" you should probably open another issue with all the necessary information, as this is issue is not about pac files. |
with ip adress , it is working , thank for the tip , and you save me ;-) |
Wait, you can point it at pac? How, with the http[s]_proxy (lowercase, the mentioned uppercase seems to be misunderstanding of some users, mostly)? As @Huuuze mentioned, this shows that proper proxy support with documentation would help a lot. Yes. the desktop Signal is not working for me for days... |
Thanks, that would be so wonderful to see in the official documentation.
|
I confirm that specifying IP addr instead of host name makes it work again for me. Thanks! |
It seems 7.5.0 has broken proxies again. Had to go back to 7.2.0, but of course Signal tells me that this version has expired. I wish the obsolesence policy was a little more use friendly. |
bro, where to download pre build versions? |
can confirm that it's broken again. WARN 2024-04-16T21:21:45.100Z SocketManager: authenticated socket connection failed with error: Error: Connection timed out |
I can also confirm that it's broken again (even with an IP address used instead of a hostname) on 7.6.0-beta.1 Getting the same log results as ichEben |
Can confirm complete breakage with 7.5.0. |
Hi! We released a fix in prod 7.5.1 and beta v7.6.0-beta.3 which both include the proxy fix, please try them. As this issue pertains to an old version and previously resolved, future discussion can be consolidated to this topic: |
@ayumi-signal The fix implemented in 7.5.1 appears to be working fine for me. Thank you for fixing Signal on desktop. |
Using a supported version?
Overall summary
Up until 7.2.0, Signal used to work with a web proxy (squid-cache). I just got notified to restart Signal to run on the latest version and since the connection status shows as "Disconnected".
If I click the yellow notification to reconnect, the nothing happens. Looking at the proxy's log it doesn't seem like Signal is initiating any connection with the signal servers. I don't see any attempts to connect directly either.
After deleting all files (application and application data), during the initial startup, Signal couldn't display the QR Code either.
I did try to submit the debug logs (
debuglogs.org
), but they seem to ignore the proxy settings (the local socket is inSYN_SENT
state). Though, I saved both log files and made an archive attached to this issue and emailed them to the support email address with a reference to this issue.On the random "crash", I noticed that sometimes the Signal window would just disappear a few seconds after opening the app.
signal-debugs.zip
Steps to reproduce
Scenario 1: Upgrade (see
debuglog-post-7.2.0-upgrade.txt
)HTTP_PROXY
,HTTPS_PROXY
pointing to your proxyScenario 2: New install (see
debuglog-new-install.txt
)HTTP_PROXY
,HTTPS_PROXY
pointing to your proxyRetry
doesn't change the outcome ❌Scenario 3
HTTP_PROXY
,HTTPS_PROXY
pointing to your proxyExpected result
Signal connects to its network via the designated proxy.
Actual result
Signal stays disconnected.
Screenshots
Signal version
7.2.0
Operating system
Windows 10
Version of Signal on your phone
7.0.2
Link to debug log
No response
The text was updated successfully, but these errors were encountered: