search

mautrix / signal

A Matrix-Signal puppeting bridge
GNU Affero General Public License v3.0
505 stars 75 forks source link

Fails registering #39

Closed yajo closed 2 years ago

yajo commented 3 years ago

Here you see the conversation:

imagen

Notice that I was already registered on signal in my phone, but I'd love to be able to uninstall it from there and keep only the matrix version.

Full trace:

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/mautrix/bridge/commands/handler.py", line 405, in handle
    await self._run_handler(handler, evt)
  File "/usr/lib/python3.8/site-packages/mautrix_signal/commands/auth.py", line 93, in enter_register_code
    account = await evt.bridge.signal.verify(username, code=evt.args[0])
  File "/opt/mautrix-signal/mausignald/signald.py", line 98, in verify
    resp = await self.request("verify", "verification_succeeded", username=username, code=code)
  File "/opt/mautrix-signal/mausignald/rpc.py", line 157, in request
    resp_type, resp_data = await self._raw_request(command, **data)
  File "/opt/mautrix-signal/mausignald/rpc.py", line 154, in _raw_request
    return await future
mausignald.errors.UnexpectedError: java.net.SocketTimeoutException: timeout

Version: mautrix-signal 0.1.0b2+dev.0defb3f7

cc @joao-p-marques

felbinger commented 3 years ago

Got basicly the same error, but the stacktrace is a bit diffrent. I thought it might be usedful to solve the problem so I added it below.

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/mautrix/bridge/commands/handler.py", line 405, in handle
    await self._run_handler(handler, evt)
  File "/usr/lib/python3.8/site-packages/mautrix/bridge/commands/handler.py", line 290, in __call__
    return await self._handler(evt)
  File "/usr/lib/python3.8/site-packages/mautrix_signal/commands/auth.py", line 84, in register
    username = await evt.bridge.signal.register(phone, voice=voice)
  File "/opt/mautrix-signal/mausignald/signald.py", line 104, in register
    resp = await self.request("register", "verification_required", username=phone,
  File "/opt/mautrix-signal/mausignald/rpc.py", line 200, in request
    resp_type, resp_data = await self._raw_request(command, **data)
  File "/opt/mautrix-signal/mausignald/rpc.py", line 197, in _raw_request
    return await future
mausignald.errors.UnexpectedError: Unexpected error with no message
foux commented 3 years ago

I've got the same erros as @felbinger, execpt that it is not at the same moment than @Yajo : it happens as soon as I entered the register command, I don't receive the SMS. I suppose it's the same for you @felbinger. Should we create a new issue for this one?

thedanbob commented 3 years ago

Just ran across the same thing. I checked the logs and found more details:

matrix-mautrix-signal-daemon[27677]: 19:16:29.383 [socketlistener] ERROR io.finn.signald.SocketHandler - Catching
matrix-mautrix-signal-daemon[27677]: org.whispersystems.signalservice.api.push.exceptions.CaptchaRequiredException: null
matrix-mautrix-signal-daemon[27677]:         at org.whispersystems.signalservice.internal.push.PushServiceSocket$1.handle(PushServiceSocket.java:267) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
matrix-mautrix-signal-daemon[27677]:         at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:1433) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
matrix-mautrix-signal-daemon[27677]:         at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceBodyRequest(PushServiceSocket.java:1420) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
matrix-mautrix-signal-daemon[27677]:         at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:1362) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
matrix-mautrix-signal-daemon[27677]:         at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:1350) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
matrix-mautrix-signal-daemon[27677]:         at org.whispersystems.signalservice.internal.push.PushServiceSocket.requestSmsVerificationCode(PushServiceSocket.java:263) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
matrix-mautrix-signal-daemon[27677]:         at org.whispersystems.signalservice.api.SignalServiceAccountManager.requestSmsVerificationCode(SignalServiceAccountManager.java:236) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
matrix-mautrix-signal-daemon[27677]:         at io.finn.signald.Manager.register(Manager.java:317) ~[signald.jar:unspecified]
matrix-mautrix-signal-daemon[27677]:         at io.finn.signald.SocketHandler.register(SocketHandler.java:396) ~[signald.jar:unspecified]
matrix-mautrix-signal-daemon[27677]:         at io.finn.signald.SocketHandler.handleRequest(SocketHandler.java:192) [signald.jar:unspecified]
matrix-mautrix-signal-daemon[27677]:         at io.finn.signald.SocketHandler.run(SocketHandler.java:134) [signald.jar:unspecified]
matrix-mautrix-signal-daemon[27677]:         at java.lang.Thread.run(Unknown Source) [?:?]
matrix-mautrix-signal[27822]: [2021-02-03 19:16:29,389] [ERROR@mau.commands] Unhandled error while handling command register [REDACTED] from [REDACTED] (ref: 1612379147)
matrix-mautrix-signal[27822]: Traceback (most recent call last):
matrix-mautrix-signal[27822]:   File "/usr/lib/python3.8/site-packages/mautrix/bridge/commands/handler.py", line 405, in handle
matrix-mautrix-signal[27822]:     await self._run_handler(handler, evt)
matrix-mautrix-signal[27822]:   File "/usr/lib/python3.8/site-packages/mautrix/bridge/commands/handler.py", line 290, in __call__
matrix-mautrix-signal[27822]:     return await self._handler(evt)
matrix-mautrix-signal[27822]:   File "/usr/lib/python3.8/site-packages/mautrix_signal/commands/auth.py", line 84, in register
matrix-mautrix-signal[27822]:     username = await evt.bridge.signal.register(phone, voice=voice)
matrix-mautrix-signal[27822]:   File "/opt/mautrix-signal/mausignald/signald.py", line 104, in register
matrix-mautrix-signal[27822]:     resp = await self.request("register", "verification_required", username=phone,
matrix-mautrix-signal[27822]:   File "/opt/mautrix-signal/mausignald/rpc.py", line 200, in request
matrix-mautrix-signal[27822]:     resp_type, resp_data = await self._raw_request(command, **data)
matrix-mautrix-signal[27822]:   File "/opt/mautrix-signal/mausignald/rpc.py", line 197, in _raw_request
matrix-mautrix-signal[27822]:     return await future
matrix-mautrix-signal[27822]: mausignald.errors.UnexpectedError: Unexpected error with no message

Going by that second line, it looks like the crash is caused by Signal requiring a captcha.

elmehalawi commented 3 years ago

@thedanbob How are you getting those logs? I tried getting those logs with:

systemctl status -f matrix-mautrix-signal
# and:
systemctl status -f matrix-mautrix-signal-daemon

And neither show anything when I run register (although I'm getting the same "Unhandled error" response).

thedanbob commented 3 years ago

I’m running them in docker via this project and they just show up in the system logs. Maybe you need to change the logging level?

elmehalawi commented 3 years ago

I'm seeing INFO entries in the logs, so I must be running into something else. Thanks though!

foux commented 3 years ago

@tulir I think we've got two different issues here. Do you want us to split them?

jannis3005 commented 3 years ago

Im having the same issue when registering, also getting the CaptchaRequiredException

corrupt3k commented 3 years ago

I also have this issue.

Feb 09 11:25:04 element matrix-mautrix-signal[12137]: Traceback (most recent call last):
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:   File "/usr/lib/python3.8/sitepackages/mautrix/bridge/commands/handler.py", line 405, in handle
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:     await self._run_handler(handler, evt)
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:   File "/usr/lib/python3.8/sitepackages/mautrix/bridge/commands/handler.py", line 290, in __call__
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:     return await self._handler(evt)
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:   File "/usr/lib/python3.8/sitepackages/mautrix_signal/commands/auth.py", line 84, in register
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:     username = await evt.bridge.signal.register(phone, voice=voice)
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:   File "/opt/mautrix-signal/mausignald/signald.py", line 104, in register
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:     resp = await self.request("register", "verification_required",username=phone,
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:   File "/opt/mautrix-signal/mausignald/rpc.py", line 200, in request
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:     resp_type, resp_data = await self._raw_request(command, **data)
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:   File "/opt/mautrix-signal/mausignald/rpc.py", line 197, in _raw_request
Feb 09 11:25:04 element matrix-mautrix-signal[12137]:     return await future
Feb 09 11:25:04 element matrix-mautrix-signal[12137]: mausignald.errors.UnexpectedError: Unexpected error with no message
tijder commented 3 years ago

You can temporary fix this by solving the captcha here: https://signalcaptchas.org/registration/generate.html (Firefox didn't work for me, I had to use chromium). The redirect url, that shown in the network tab (f12) needs to be filled on this line: https://github.com/tulir/mautrix-signal/blob/5fa2c227ea2f383388099cacd0ba9812be872ff1/mausignald/signald.py#

resp = await self.request("register", "verification_required", username=phone,
                                  voice=voice, captcha="CAPTCHA")

Then run the register command once more.

Signald wiki about Captchas

thedanbob commented 3 years ago

For anyone running this in docker (e.g. matrix-docker-ansible-deploy), here's one way to do this:

  1. Copy signald.py from github or the docker container to somewhere on the server: docker exec <container ID> bash -c 'cat mausignald/signald.py' > signald.py
  2. Generate a captcha link and edit the file as mentioned, without the signalcaptcha:// prefix
  3. Add a bind mount for that file to the docker command: -v "<dir>/signald.py:/opt/mautrix-signal/mausignald/signald.py". If you're running matrix-docker-ansible-deploy, the service file to edit can be found at /etc/systemd/system/matrix-mautrix-signal.service.
  4. Restart the matrix-mautrix-signal service / recreate the container
  5. Register
  6. Remove the bind mount and restart the container again
foux commented 3 years ago

Thanks you both, that was really helpfull!

Unfortunately it got me only one step further : after inputing the code received by SMS, I got the following error : 

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/mautrix/bridge/commands/handler.py", line 405, in handle
    await self._run_handler(handler, evt)
  File "/usr/lib/python3.8/site-packages/mautrix_signal/commands/auth.py", line 97, in enter_register_code
    account = await evt.bridge.signal.verify(username, code=evt.args[0])
  File "/opt/mautrix-signal/mausignald/signald.py", line 110, in verify
    resp = await self.request("verify", "verification_succeeded", username=username, code=code)
  File "/opt/mautrix-signal/mausignald/rpc.py", line 205, in request
    resp_type, resp_data = await self._raw_request(command, **data)
  File "/opt/mautrix-signal/mausignald/rpc.py", line 202, in _raw_request
    return await future
mausignald.errors.UnexpectedError: Bad response: 400

Which seems linked to the original issue of the ticket (not the same error, but seems reasonably close)

pcolusso commented 3 years ago

Also running into this, instead of modifying the code you can send raw commands to signald, using raw register { "type": "register", "username": "", "captcha": "" }, then signald responds with Got reply verification_required:.

Did receive the SMS verify, raw verify {"type": "verify", "username": "", "code": "" } but receive the same Bad Response 400, but this looks like it's coming from signald; log below

01:13:29.451 [socketlistener] INFO  io.finn.signald.SocketHandler - Submitting verification code [REDACTED] for number [REDACTED]
01:13:29.661 [socketlistener] ERROR io.finn.signald.SocketHandler - Catching
org.whispersystems.signalservice.api.push.exceptions.NonSuccessfulResponseCodeException: Bad response: 400
    at org.whispersystems.signalservice.internal.push.PushServiceSocket.validateServiceResponse(PushServiceSocket.java:1477) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
    at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:1435) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
    at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceBodyRequest(PushServiceSocket.java:1420) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
    at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:1362) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
    at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:1338) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
    at org.whispersystems.signalservice.internal.push.PushServiceSocket.verifyAccountCode(PushServiceSocket.java:314) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
    at org.whispersystems.signalservice.api.SignalServiceAccountManager.verifyAccountWithCode(SignalServiceAccountManager.java:276) ~[signal-service-java-x86_64-unknown-linux-gnu-2.15.3_unofficial_17.jar:?]
    at io.finn.signald.Manager.verifyAccount(Manager.java:407) ~[signald.jar:unspecified]
    at io.finn.signald.SocketHandler.verify(SocketHandler.java:407) ~[signald.jar:unspecified]
    at io.finn.signald.SocketHandler.handleRequest(SocketHandler.java:193) [signald.jar:unspecified]
    at io.finn.signald.SocketHandler.run(SocketHandler.java:132) [signald.jar:unspecified]
    at java.lang.Thread.run(Unknown Source) [?:?]

EDIT: I think this may be related to a collision I precipitated. I had set up mautrix-signal for Signal first, and then signed in on my phone using the native app, which invalidated the previous login with mautrix-signal. I just tried wiping away the Postgres database and registering raw again, and was able to log in. May be worth a shot for those experiencing the Bad Response issue?

EDIT 2: After realising why I cannot link my phone I realise that is unsupported, so I have abandoned my plans to have mautrix-signal as my primary registered device and instead link it to my phone. To do this, I had to delete some registration files from the signald/data folder, there's a prompt in the logs if you're experiencing issues.

abliss commented 3 years ago

I was able to get registration to complete using the raw register and raw verify commands, but it doesn't seem to have linked my matrix user to the account, so I still can't use it (the bot says 'you must be logged in'). I would suggest thedanbob's method instead.

Happyfeet01 commented 2 years ago

I have the same Problem. I was already registered, but removed the account. Now i was unable to register again. 

19 21:03:25 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:03:25,552] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:03:25 +0000] "PUT /transactions/24272?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:07:36 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:07:36,250] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:07:36 +0000] "PUT /transactions/24273?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:09:25 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:09:25,625] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:09:25 +0000] "PUT /transactions/24274?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:13:09 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:13:09,423] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:13:09 +0000] "PUT /transactions/24275?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:15:19 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:15:19,544] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:15:19 +0000] "PUT /transactions/24276?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:15:20 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:15:20,010] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:15:20 +0000] "PUT /transactions/24277?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:15:21 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:15:21,380] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:15:21 +0000] "PUT /transactions/24278?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:15:21 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:15:21,847] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:15:21 +0000] "PUT /transactions/24279?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:16:07 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:16:07,485] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:16:07 +0000] "PUT /transactions/24280?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:16:45 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:16:45,150] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:16:45 +0000] "PUT /transactions/24281?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:17:28 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:17:28,263] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:17:28 +0000] "PUT /transactions/24282?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:20:55 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:20:55,945] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:20:55 +0000] "PUT /transactions/24283?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:21:19 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:21:16,170] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:21:16 +0000] "PUT /transactions/24284?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:21:31 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:21:31,688] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:21:31 +0000] "PUT /transactions/24285?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:22:05 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:22:05,555] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:22:05 +0000] "PUT /transactions/24286?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:22:36 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:22:36,679] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:22:36 +0000] "PUT /transactions/24287?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:22:38 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:22:38,745] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:22:38 +0000] "PUT /transactions/24288?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:22:51 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:22:51,459] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:22:51 +0000] "PUT /transactions/24289?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:22:52 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:22:52,026] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:22:52 +0000] "PUT /transactions/24290?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:22:52 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:22:52,090] [DEBUG@mau.mx] Received Matrix event $aXVy5cYgUlsSJCMFexpOpIamzizdEC12KbkInkiMBk0 from @lars:fulda.social in !WBgkCFgFYNqMtkFphq:fulda.social
Oct 19 21:22:59 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:22:59,926] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:22:59 +0000] "PUT /transactions/24291?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:23:01 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:01,476] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:23:01 +0000] "PUT /transactions/24292?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:23:09 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:09,806] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:23:09 +0000] "PUT /transactions/24293?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:23:12 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:12,526] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:23:12 +0000] "PUT /transactions/24294?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:23:13 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:13,791] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:23:13 +0000] "PUT /transactions/24295?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:23:14 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:14,276] [DEBUG@mau.mx] Received Matrix event $vu54-hUQtMfikvv3Z5prY_VmcYQ_LcFw98TKuLh5c_c from @lars:fulda.social in !WBgkCFgFYNqMtkFphq:domain.tld
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:14,978] [ERROR@mau.commands] Unhandled error while handling command  676181 from @lars:domain.tld (ref: 1634659334)
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: Traceback (most recent call last):
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:   File "/usr/lib/python3.9/site-packages/mautrix/bridge/commands/handler.py", line 406, in handle
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:     await self._run_handler(handler, evt)
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:   File "/usr/lib/python3.9/site-packages/mautrix_signal/commands/auth.py", line 126, in enter_register_code
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:     account = await evt.bridge.signal.verify(username, code=evt.args[0])
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:   File "/opt/mautrix-signal/mausignald/signald.py", line 119, in verify
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:     resp = await self.request_v1("verify", account=username, code=code)
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:   File "/opt/mautrix-signal/mausignald/rpc.py", line 223, in request_v1
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:     return await self.request(command, expected_response=command, version="v1", **data)
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:   File "/opt/mautrix-signal/mausignald/rpc.py", line 217, in request
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:     resp_type, resp_data = await self._raw_request(command, **data)
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:   File "/opt/mautrix-signal/mausignald/rpc.py", line 214, in _raw_request
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]:     return await asyncio.shield(future)
Oct 19 21:23:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: mausignald.errors.AuthorizationFailedException: [403] Authorization failed!
Oct 19 21:23:17 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:17,800] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:23:17 +0000] "PUT /transactions/24296?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
Oct 19 21:23:21 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[108853]: [2021-10-19 19:23:21,565] [INFO@aiohttp.access] 172.24.0.21 [19/Oct/2021:19:23:21 +0000] "PUT /transactions/24297?access_token=a9a3de77-7309-5bf2-b499-d9bbc017195b HTTP/1.1" 200 158 "-" "Synapse/1.45.0"
^C
Happyfeet01 commented 2 years ago

The logentry in syslog file when it fails to register

Oct 24 07:59:38 Debian-1100-bullseye-amd64-base matrix-postgres[73026]: 2021-10-24 05:59:38.466 UTC [175] STATEMENT: INSERT INTO users (name, password_hash, creation_ts, is_guest, appservice_id, admin, user_type, shadow_banned) VALUES('@signalbot:domain.tld', '', 1635055178, 0, 'signal', 0, NULL, false) Oct 24 08:02:15 Debian-1100-bullseye-amd64-base matrix-mautrix-signal[2838727]: [2021-10-24 06:02:15,644] [#033[31;1mERROR#033[0m@#033[32mmau.commands#033[0m] Unhandled error while handling command 911634 from @lars:domain.tld (ref: 1635055178)

tulir commented 2 years ago

Captchas are already supported, other error codes are probably issues with signald or the signal servers rather than the bridge

Happyfeet01 commented 2 years ago

@tulir can you give an tip how can i reset the data from one User? The Bridge tells me, not connected, but i receive Messages from Signal, but can't answer. logout is also not possible