signalapp / Signal-Desktop

A private messenger for Windows, macOS, and Linux.
https://signal.org/download
GNU Affero General Public License v3.0
14.55k stars 2.64k forks source link

Signal App can't conenct to netwokr after automatic update to version 7.2.0 #6831

Closed gpantazis closed 6 months ago

gpantazis commented 6 months ago

Using a supported version?

Overall summary

After updating to 7.2.0 The Signal app was unable to connect to the network and connect to any chats. After uninstalling and redownloading latest version, the QR code won't load. Please note I am behind a proxy. Additionally, http_proxy, https_proxy are all set correctly and were working

Checking the logs, the error in both instances is due to:

SocketManager: failed to connect unauthenticated socket due to error: HTTPError: connectResource: connectFailed; code: -1 .... Caused by: Error: createProxyAgent: all=true lookup is not supported

(Please see attached logs of newly downloaded version: debuglog.txt)

Note, running curl -4 -k https://textsecure-service.whispersystems.org/ returns valid html. Conversely running curl -6 -k https://textsecure-service.whispersystems.org/ complains about being unable to resolve proxy

EDIT: Prior closed issues referred to a similar problem but did not provide any resolution, and did not seem to point to the same error as indicated by my logs.

Steps to reproduce

  1. Download or open after updating latest version (7.2.0) of Signal Desktop app
  2. Try to connect/reconnect by clicking yellow banner OR try to load QR code for linking devices
  3. System fails to connect

Expected result

System should connect to to the network

Actual result

System is unable to connect to the network

Screenshots

image

image

Signal version

7.2.0

Operating system

Windows 10

Version of Signal on your phone

No response

Link to debug log

debuglog.txt

scottnonnenberg-signal commented 6 months ago

Looks like this is a duplicate of https://github.com/signalapp/Signal-Desktop/issues/6828

We're investigating, but for now there's a workaround available in that issue.