search

signalapp / Signal-Desktop

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

Signal for desktop fails to link to account #3084

Closed favourthebold closed 5 years ago

favourthebold commented 5 years ago

Bug Description

When linking Signal for desktop, after scanning the QR code, shows error 'something went wrong'

Steps to Reproduce

  1. Open Signal for desktop (windows)
  2. Scan QR code from phone
  3. Type name of new device, press ok
  4. Shows error 'Something went wrong'

Screenshots

image

Platform Info

Signal Version:

v1.20.0

Operating System:

Windows 10 Enterprise Version: 1607 OS Build: 14393.1770

Linked Device Version:

iPhone 7+ iOS 12.1.2 (16C101)

Link to Debug Log

https://debuglogs.org/97fd450ae2a186af70efc0dc328203e0b73e25b5f1d97bd773e1f0b60d66e7d7

OscarHeller commented 5 years ago

This just happened to me too.

Platform Info

Signal Version:

v1.20.0

Operating System:

Windows 10 Home Version: 1803 OS Build: 17134.523

Linked Device Version:

Pixel XL Android 9

Link to Debug Log

https://debuglogs.org/90d928cf467d77d7c9e9522ced97d4ad69c5f7d709e536face0e8f5461837dd6

ruicraveiro commented 5 years ago

It is also happening to me.

Platform Info

Signal Version:

v1.20.0 (but also with the same error on 1.19 and 1.18)

Operating System:

Windows 10 Pro Version: 1809 OS Build: 17763.253

Linked Device Version:

iPhone SE iOS 12.1.2 (16C101)

Link to Debug Log (from the final attempt on 1.18)

https://debuglogs.org/af9d244de60fce031b750c40b7870889504eb49bf1b83c6a53b92068ff29e837

bgroins commented 5 years ago

Same problem on Windows 10 and Windows Server 2019 Pixel XL

klatteri commented 5 years ago

Same issue on MacBook Pro 2018 running MacOS 10.14.3

Natanji commented 5 years ago

Here is an error log from Signal Desktop:

ERROR 2019-01-25T00:43:25.837Z websocket error
INFO  2019-01-25T00:43:25.837Z websocket closed 1006 connection failed calledClose: 
INFO  2019-01-25T00:43:25.837Z GET https://textsecure-service.whispersystems.org/v1/devices
ERROR 2019-01-25T00:43:25.841Z PUT https://textsecure-service.whispersystems.org/v1/devices/unauthenticated_delivery 401 Error
ERROR 2019-01-25T00:43:25.842Z Error: Unable to register for unauthenticated delivery support. HTTPError: promiseAjax: error response; code: 401
    at HTTPError ([REDACTED]\app.asar\js\modules\web_api.js:316:13)
    at resultPromise.then.result ([REDACTED]\app.asar\js\modules\web_api.js:275:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
Original stack:
Error
    at _outerAjax ([REDACTED]\app.asar\js\modules\web_api.js:310:19)
    at _ajax ([REDACTED]\app.asar\js\modules\web_api.js:400:14)
    at Object.registerSupportForUnauthenticatedDelivery ([REDACTED]\app.asar\js\modules\web_api.js:464:14)
    at connect (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/background.js:703:22)
    at start (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/background.js:500:7)
    at storage.onready (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/background.js:424:7)
INFO  2019-01-25T00:43:25.842Z Start idle detector
ERROR 2019-01-25T00:43:25.843Z GET https://textsecure-service.whispersystems.org/v1/certificate/delivery 401 Error
ERROR 2019-01-25T00:43:25.843Z refreshSenderCertificate: Get failed. Trying again in two minutes... HTTPError: promiseAjax: error response; code: 401
    at HTTPError ([REDACTED]\app.asar\js\modules\web_api.js:316:13)
    at resultPromise.then.result ([REDACTED]\app.asar\js\modules\web_api.js:275:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
Original stack:
Error
    at _outerAjax ([REDACTED]\app.asar\js\modules\web_api.js:310:19)
    at _ajax ([REDACTED]\app.asar\js\modules\web_api.js:400:14)
    at Object.getSenderCertificate ([REDACTED]\app.asar\js\modules\web_api.js:455:14)
    at run ([REDACTED]\app.asar\js\modules\refresh_sender_certificate.js:65:44)
    at runWhenOnline ([REDACTED]\app.asar\js\modules\refresh_sender_certificate.js:88:7)
    at Object.initialize ([REDACTED]\app.asar\js\modules\refresh_sender_certificate.js:30:3)
    at start (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/background.js:493:46)
    at storage.onready (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/background.js:424:7)
INFO  2019-01-25T00:43:25.843Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]701
ERROR 2019-01-25T00:43:25.969Z GET https://textsecure-service.whispersystems.org/v1/profile/+[REDACTED]701 401 Error
ERROR 2019-01-25T00:43:25.969Z getProfile error: +[REDACTED]701 HTTPError: promiseAjax: error response; code: 401
    at HTTPError ([REDACTED]\app.asar\js\modules\web_api.js:316:13)
    at resultPromise.then.result ([REDACTED]\app.asar\js\modules\web_api.js:275:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
Original stack:
Error
    at _outerAjax ([REDACTED]\app.asar\js\modules\web_api.js:310:19)
    at _ajax ([REDACTED]\app.asar\js\modules\web_api.js:400:14)
    at Object.getProfile ([REDACTED]\app.asar\js\modules\web_api.js:472:14)
    at MessageSender.getProfile (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/libtextsecure.js:40741:24)
    at getProfile (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/models/conversations.js:1437:48)
    at process._tickCallback (internal/process/next_tick.js:68:7)
INFO  2019-01-25T00:43:25.989Z SQL channel job 213 (createOrUpdateItem) succeeded in 12ms
ERROR 2019-01-25T00:43:26.209Z GET https://textsecure-service.whispersystems.org/v1/devices 401 Error
ERROR 2019-01-25T00:43:26.210Z background onError: HTTPError: promiseAjax: error response; code: 401
    at HTTPError ([REDACTED]\app.asar\js\modules\web_api.js:316:13)
    at resultPromise.then.result ([REDACTED]\app.asar\js\modules\web_api.js:275:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
Original stack:
Error
    at _outerAjax ([REDACTED]\app.asar\js\modules\web_api.js:310:19)
    at _ajax ([REDACTED]\app.asar\js\modules\web_api.js:400:14)
    at Object.getDevices ([REDACTED]\app.asar\js\modules\web_api.js:591:14)
    at MessageReceiver.onclose (file:///C:/Users/natan/AppData/Local/Programs/signal-desktop/resources/app.asar/js/libtextsecure.js:38605:8)
    at W3CWebSocket._dispatchEvent [as dispatchEvent] ([REDACTED]\app.asar\node_modules\yaeti\lib\EventTarget.js:107:17)
    at W3CWebSocket.onConnectFailed ([REDACTED]\app.asar\node_modules\websocket\lib\W3CWebSocket.js:219:14)
    at WebSocketClient.<anonymous> ([REDACTED]\app.asar\node_modules\websocket\lib\W3CWebSocket.js:59:25)
    at WebSocketClient.emit (events.js:182:13)
    at WebSocketClient.failHandshake ([REDACTED]\app.asar\node_modules\websocket\lib\WebSocketClient.js:339:10)
    at ClientRequest.<anonymous> ([REDACTED]\app.asar\node_modules\websocket\lib\WebSocketClient.js:278:18)
WARN  2019-01-25T00:43:26.226Z Client is no longer authorized; deleting local configuration
SebastianWaterhouse commented 5 years ago

Also having this issue, this seems to be the most relevant snippet of log:



Error

    at _outerAjax ([REDACTED]\app.asar\js\modules\web_api.js:310:19)

    at _ajax ([REDACTED]\app.asar\js\modules\web_api.js:400:14)

    at Object.registerKeys ([REDACTED]\app.asar\js\modules\web_api.js:621:14)

    at createAccount.then.then.then.keys (file:///C:/Users/littl/AppData/Local/Programs/signal-desktop/resources/app.asar/js/libtextsecure.js:37744:35)

ERROR 2019-01-25T01:26:23.693Z Top-level unhandled promise rejection: HTTPError: Invalid authentication, most likely someone re-registered and invalidated our registration. (original: promiseAjax: error response; code: 401)
scottnonnenberg-signal commented 5 years ago

We're looking at this.

scottnonnenberg-signal commented 5 years ago

Alright everyone, please try again. It should work now!

favourthebold commented 5 years ago

Working! Thanks Scott!

ruicraveiro commented 5 years ago

Working! Thanks Scott!

zelyev commented 5 years ago

It is not working for me. I just got the same error message: "Something went wrong!"

Linux Desktop Version + Android 4.4.2 Version

https://debuglogs.org/b62b05a2d5e67bb8ee7e2b9495d7dadba224c9563055bd724c9465801ab007cf

limeandcoconut commented 4 years ago

Same issue. Macbook Pro Mojave + Pixel 4 Android 10

scottnonnenberg-signal commented 4 years ago

@limeandcoconut What's your specific Signal Android version?

limeandcoconut commented 4 years ago

Signal 4.50.6, Android QD1A.190821.014.

The phone is new. I just now switched from my old one and it's been working fine. The macbook is the device I was adding scanning.

scottnonnenberg-signal commented 4 years ago

@limeandcoconut Please consider joining the SIgnal Android beta, because v4.51.1 has additional logging for this scenario: https://support.signal.org/hc/en-us/articles/360007318471-How-do-I-join-Signal-s-beta-

limeandcoconut commented 4 years ago

@scottnonnenberg-signal, I'm joined! Would you like a log when I get the update?

scottnonnenberg-signal commented 4 years ago

@limeandcoconut Please. We're especially interested to see if the problem persists once you upgrade.

cestrad commented 4 years ago

Same problem for me when needing to relink a desktop computer running Win7. I got a new cell phone and set up Signal, seems to working okay there but no longer on the PC.

BlueCyberCat commented 4 years ago

Had the same issue on android. Worked after joining the beta.

scottnonnenberg-signal commented 4 years ago

@cestrad Please provide your Desktop debug log (View -> Debug Log) as well as your phone's log (you'll find it in Settings).

mnstrspeed commented 4 years ago

I ran into the same issue today: had to re-install the Android client (no back-up available through my own mistake) and upon attempting to link my existing Signal Desktop client (v1.29.0 on Windows 10 64-bit) I encountered the same "Something went wrong".

Joining the beta on Android also resolved the issue for me.

Desktop debug log Android debug log

Hope this helps.

ThornedRose commented 4 years ago

@sideyourspirit

Had the same issue on android. Worked after joining the beta.

@mnstrspeed

I ran into the same issue today: had to re-install the Android client (no back-up available through my own mistake) and upon attempting to link my existing Signal Desktop client (v1.29.0 on Windows 10 64-bit) I encountered the same "Something went wrong".

Joining the beta on Android also resolved the issue for me.

[Desktop debug log] [Android debug log]

Hope this helps.

I have had the same problem on Arch Linux. Fresh install of Signal on Arch, fresh install of my OS on my phone (Resurrection OS Android 9 on a Samsung Note3) and thus a fresh install of Android Signal. As others have said above, the Android beta version of Signal fixed the issue although I had to restart the app on my PC and clear the memory and cache on Android Signal before it would start working (otherwise Android version just sat there with a loading animation when I tapped link device).

Here are the logs before I updated to the beta version: Android: https://debuglogs.org/dfcf99c01038147f40dd790f1989fc47cdeee46c7896cc1a69be09dbcb5fa42d Arch Linux: https://debuglogs.org/aba4b175ae9f29c3881531c77f05b66055c5133724d56437ff9af5ccea8633d0

ERROR 2019-12-10T23:31:29.641Z PUT https://textsecure-service.whispersystems.org/v1/devices/237266 401 Error
ERROR 2019-12-10T23:31:29.643Z provisioning failed HTTPError: promiseAjax: invalid response; code: 401
    at HTTPError ([REDACTED]/app.asar/js/modules/web_api.js:379:13)
    at [REDACTED]/app.asar/js/modules/web_api.js:293:19
    at processTicksAndRejections (internal/process/task_queues.js:85:5)
Original stack:
Error
    at _outerAjax ([REDACTED]/app.asar/js/modules/web_api.js:373:19)
    at _ajax ([REDACTED]/app.asar/js/modules/web_api.js:476:14)
    at Object.confirmCode ([REDACTED]/app.asar/js/modules/web_api.js:634:30)
    at AccountManager.createAccount (file://[REDACTED]/app.asar/js/libtextsecure.js:37844:42)
ERROR 2019-12-10T23:31:29.648Z Top-level unhandled promise rejection: HTTPError: Invalid authentication, most likely someone re-registered and invalidated our registration. (original: promiseAjax: invalid response; code: 401)
sayak1711 commented 3 years ago

I get same error in June 2021 also.

hiqua commented 3 years ago

@sayak1711 make sure you use the latest versions. If you use a beta version, make sure you use the latest beta. This bug should be fixed now.

sayak1711 commented 3 years ago

@hiqua I downloaded the setup today from https://signal.org/download/windows/. It should be latest right?

hiqua commented 3 years ago

Which version do you have on Android? If you have a beta version, please use the latest.

sayak1711 commented 3 years ago

@hiqua It's not beta. It is the latest 5.13.8

imonlygitting commented 3 years ago

also having this trouble while using (which is v5.4.1): https://github.com/louislam/Signal-Desktop-Multiple-Portable

but on that fork there seems no way to feedback this error to dev... hope he sees it here and upgrade closer to 5.13.8 which presumably solves the problem?