signal-cli icon indicating copy to clipboard operation
signal-cli copied to clipboard

Unregistered user

Open Tsjippy opened this issue 8 months ago • 6 comments

While trying to send messages I always get the reply " Unregistered user ". This is a from a newly registered signal number. I have tried 3 different recipients which I know are valid. Response:

signal-cli -a +316NUMBER-v send -m "This is a message" +234NUMBER
2025-04-30T13:58:48.516+0100 [main] DEBUG org.asamk.signal.App - Starting signal-cli 0.13.12
2025-04-30T13:58:48.611+0100 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_DATA_HOME not set, falling back to home dir
2025-04-30T13:58:51.380+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2025-04-30T13:58:52.053+0100 [main] INFO  com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.sqlite.jdbc4.JDBC4Connection@1572e62
2025-04-30T13:58:52.063+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2025-04-30T13:59:11.143+0100 [main] DEBUG o.a.s.manager.internal.JobExecutor - Running RefreshRecipientsJob job
2025-04-30T13:59:11.178+0100 [pool-2-thread-1] DEBUG o.a.s.manager.helper.RecipientHelper - No new numbers to query.
2025-04-30T13:59:11.183+0100 [pool-2-thread-1] DEBUG o.a.s.m.s.recipients.RecipientStore - Marking 0 numbers as undiscoverable
2025-04-30T13:59:11.185+0100 [pool-2-thread-1] DEBUG o.a.s.m.s.recipients.RecipientStore - Marking 0 numbers as discoverable
2025-04-30T13:59:11.757+0100 [main] WARN  LibSignal - [PhoneNumberFormatter]: Got local CC: NL
Failed to send (some) messages:
+2349011531222: Unregistered user "+234NUMBER"
1746017951818
2025-04-30T13:59:12.015+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
2025-04-30T13:59:12.029+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
Failed to send message

Tsjippy avatar Apr 30 '25 13:04 Tsjippy

What do you get if you run signal-cli -a +316NUMBER getUserStatus +234NUMBER

AsamK avatar May 08 '25 18:05 AsamK

Hi,

Same issue when trying to send a message from "sender" (SCLI used as sender number) to all recipients on Android smartphone (SPi used as others phone numbers) I have for testing. Tested with 13.18, 13.19 (13.20 give me another error): same behavior

The versions ares modified according to AsamK update. A specific certificate has been added to whisper.store because of my entreprise proxy. Registering is OK UpdatingProfile is also OK (no more issues due to firewall)

The getUsersStatus give me also an error (may be due the entreprise proxy) what ever the SP1 Unable to check if users are registered: connect timed out (NetworkException), but very fast (IPV6 connection seen in log)

I have tested to send messages to Smartphone1 (SP1) or to SP2 or to SP3: same think SP1, SP2 and SP3 can communicate between each others.

Some thing strange: SP1 or SP2 can send messages to SCLI: messages are received (using receive command) SCLI sends in return that distribution is OK, but no way the send the read status => Unregistered user "SPi"

On Smartphone, when going to settings "Display security number" I have a message "In order to display secuirty number of XXX, start by exchanging messages" (translated from french :) )

So, what ? Where is the issue ?

Edit #1 I have tested 13.19 with another number WITHOUT proxy, and ... is works :) signal-cli is not in fault. I think it is linked to the account.

Edit #2 After several tests with different numbers of my service. I have the same issue with others numbers. Signal-cli and proxies are not the cause. These numbers are not clean or "virgin" for signal. That is the point. It seems that when you change the devices, Signal does not make the links between each others and numbers appears not registered. This is a signal issue or misunderstanding from us. Problem: we are unable to remove account clearly event whith Android App on smartphone. Strange thing: I invited a colleague, who change nothing on his side, by signal. When he answer me I receive the message as unknown user, not in the same chat. Strange...

Edit #3 Test using 13.19 (13.20 generate error Error while checking account $ACCOUNT: Closed unexpectedly) I succeed in sending message to blacklisted numbers. In fact, Signal hides those numbers on smartphone even if they exists in my phone book. So I set an user name to account like this signal-cli -a $ACCOUNT updateAccount -u foo Command answer foo.1234

Sending a message from smartphone to foo.1234 is OK. We can confirm the peer with validating security number ! Good point. Message is received by foo.1234 but I have a message when running receive command:

Server timestamps: received: 1758802613620 (2025-09-25T12:16:53.620Z) delivered: 1758802626058 (2025-09-25T12:17:06.058Z) The user’s key is untrusted, either the user has reinstalled Signal or a third party sent this message. Use 'signal-cli -a $ACCOUNT listIdentities -n 1234567-8901-2345-6789-01234567890Z', verify the key and run 'signal-cli -a $ACCOUNT trust -v "FINGER_PRINT" 1234567-8901-2345-6789-01234567890Z' to mark it as trusted If you don't care about security, use 'signal-cli -a $ACCOUNT trust -a 1234567-8901-2345-6789-01234567890Z' to trust it without verification I run signal-cli -a $ACCOUNT listIdentities -n 1234567-8901-2345-6789-01234567890Z

Check the security number and finally run signal-cli -a $ACCOUNT listIdentities -n 1234567-8901-2345-6789-01234567890Z

2025-09-25T14:17:41.857+0200 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_RUNTIME_DIR not set, falling back to temp dir 2025-09-25T14:17:41.868+0200 [main] DEBUG org.asamk.signal.App - Starting signal-cli0.13.19_by_XX2025-09-25T14:17:42.536+0200 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_DATA_HOME not set, falling back to home dir 2025-09-25T14:17:42.894+0200 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting... 2025-09-25T14:17:43.020+0200 [main] INFO com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.sqlite.jdbc4.JDBC4Connection@3ebff828 2025-09-25T14:17:43.022+0200 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed. 2025-09-25T14:17:43.640+0200 [main] INFO LibSignal - [OkHttpWebSocketConnection]: [normal:1130656047] connect() 2025-09-25T14:17:44.677+0200 [OkHttp https://chat.signal.org/...] INFO LibSignal - [OkHttpWebSocketConnection]: [normal:1130656047] onOpen() connected 2025-09-25T14:17:45.080+0200 [main] DEBUG o.a.s.manager.internal.JobExecutor - Running RefreshRecipientsJob job 2025-09-25T14:17:45.089+0200 [pool-2-thread-1] DEBUG o.a.s.manager.helper.RecipientHelper - No new numbers to query. 2025-09-25T14:17:45.090+0200 [pool-2-thread-1] DEBUG o.a.s.m.s.recipients.RecipientStore - Marking 0 numbers as undiscoverable 2025-09-25T14:17:45.091+0200 [pool-2-thread-1] DEBUG o.a.s.m.s.recipients.RecipientStore - Marking 0 numbers as discoverable 2025-09-25T14:17:45.325+0200 [main] INFO LibSignal - [OkHttpWebSocketConnection]: [normal:1130656047] disconnect() 2025-09-25T14:17:45.327+0200 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated... 2025-09-25T14:17:45.329+0200 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed. Safety number has invalid format, either specify the old hex fingerprint or the new safety number

This is a signal-cli message. After reading the doc, I change the command and run: signal-cli -a $ACCOUNT trust -v "12345 12345 12345 12345 12345 12345 12345 12345 12345 12345 12345 12345" $RECIPIENT

And I get

The user $RECIPIENT is not registered

Back to starting point :(

NB: fake security number an fingerprint. Number replaced by $ACCOUNT for sender and $RECIPIENT for recipient

Edit #4 I replace the phone number by the 1234567-8901-2345-6789-01234567890Z (UUID) and it works !

Edit #5 The day after phone numbers have replacer UUID in list of contact. It is a Signal issue. Strange

Didou31 avatar Sep 24 '25 16:09 Didou31