Verify error: StatusCode: 404

[pavex]

Hi, The command keeps giving me a 404. Is it possible to find out why? Many thanks.

signal-cli.bat -u +000000000000 verify 123456
Verify error: StatusCode: 404

[AsamK]

Which signal-cli version are you using?

[pavex]

signal-cli-0.13.9

[AsamK]

That version should work, you can get more details with the -vv parameter.

[mv1769]

Hi, I have the same problem with this command :

./signal-cli -u phonenumber verify CODE Verify error: StatusCode: 404

I use the signal-cli version 0.13.12

Do you know what is the problem ?

[m-ueberall]

.@mv1769: See the last comment above:

That version should work, you can get more details with the -vv parameter.

Those details might be essential to answer your question (don't forget to redact your phone number, etc.) …

[mv1769]

@m-ueberall

OK, thank you very much!

I get this after doing ./signal-cli -vv :

./signal-cli -vv usage: signal-cli [-h] [--version] [-v] [--log-file LOG_FILE] [--scrub-log] [-c CONFIG] [-a ACCOUNT] [--bus-name GLOBAL-BUS-NAME] [-o {plain-text,json}] [--service-environment {live,staging,sandbox}] [--trust-new-identities {always,on-first-use,never}] [--disable-send-log] [--dbus | --dbus-system] {addDevice,addStickerPack,block,daemon,deleteLocalAccountData,finishChangeNumber,getAttachment,getAvatar,getSticker,getUserStatus,joinGroup,jsonRpc,link,listAccounts,listContacts,listDevices,listGroups,listIdentities,listStickerPacks,quitGroup,receive,register,remoteDelete,removeContact,removeDevice,removePin,send,sendContacts,sendMessageRequestResponse,sendPaymentNotification,sendReaction,sendReceipt,sendSyncRequest,sendTyping,setPin,startChangeNumber,submitRateLimitChallenge,trust,unblock,unregister,updateAccount,updateConfiguration,updateContact,updateGroup,updateProfile,uploadStickerPack,verify,version} ... signal-cli: error: too few arguments

the problem is related to ‘signal-cli: error: too few arguments’ ? Do you know what I have to do ?

I'm sorry, I'm a linux beginner and I don't understand everything :/

[m-ueberall]

@mv1769 : Try ./signal-cli -vv -u PHONENUMBER verify CODE

[mv1769]

@m-ueberall

I get this after :

2025-01-27T20:43:34.754+0100 [main] DEBUG org.asamk.signal.App - Starting signal-cli 0.13.12 2025-01-27T20:43:35.122+0100 [main] TRACE org.asamk.signal.manager.Manager - Expected exception when checking libsignal-client: Failed to deserialize zkgroup::api::groups::uuid_ciphertext::UuidCiphertext 2025-01-27T20:43:35.122+0100 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_DATA_HOME not set, falling back to home dir 2025-01-27T20:43:35.355+0100 [main] TRACE o.a.s.manager.storage.SignalAccount - Opening account file 2025-01-27T20:43:35.357+0100 [main] TRACE o.a.s.manager.storage.SignalAccount - Loading account file 403200 2025-01-27T20:43:35.434+0100 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting... 2025-01-27T20:43:35.566+0100 [main] INFO com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.sqlite.jdbc4.JDBC4Connection@a8c1f44 2025-01-27T20:43:35.567+0100 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed. 2025-01-27T20:43:35.574+0100 [main] TRACE o.a.s.m.storage.AccountDatabase - Current database version: 27 Program database version: 27 2025-01-27T20:43:36.879+0100 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated... 2025-01-27T20:43:36.883+0100 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed. Verify error: StatusCode: 404 org.whispersystems.signalservice.api.push.exceptions.NoSuchSessionException: StatusCode: 404 at org.whispersystems.signalservice.internal.push.PushServiceSocket$RegistrationCodeSubmissionResponseHandler.handle(PushServiceSocket.java:3352) at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:2371) at org.whispersystems.signalservice.internal.push.PushServiceSocket.submitVerificationCode(PushServiceSocket.java:455) at org.whispersystems.signalservice.api.registration.RegistrationApi.verifyAccount$lambda$4(RegistrationApi.kt:84) at org.whispersystems.signalservice.api.NetworkResult$Companion.fromFetch(NetworkResult.kt:44) at org.whispersystems.signalservice.api.registration.RegistrationApi.verifyAccount(RegistrationApi.kt:83) at org.asamk.signal.manager.internal.RegistrationManagerImpl.verifyAccountWithCode(RegistrationManagerImpl.java:264) at org.asamk.signal.manager.internal.RegistrationManagerImpl.lambda$verifyAccount$2(RegistrationManagerImpl.java:167) at org.asamk.signal.manager.util.NumberVerificationUtils.verifyNumber(NumberVerificationUtils.java:120) at org.asamk.signal.manager.internal.RegistrationManagerImpl.verifyAccount(RegistrationManagerImpl.java:163) at org.asamk.signal.commands.VerifyCommand.verify(VerifyCommand.java:71) at org.asamk.signal.commands.VerifyCommand.handleCommand(VerifyCommand.java:43) at org.asamk.signal.commands.CommandHandler.handleRegistrationCommand(CommandHandler.java:33) at org.asamk.signal.App.handleRegistrationCommand(App.java:268) at org.asamk.signal.App.handleCommand(App.java:177) at org.asamk.signal.App.init(App.java:147) at org.asamk.signal.Main.main(Main.java:56)

[mv1769]

The problem was solved when I redid the process with the captcha link (the sms had been sent too late?)! I'm moving on to the next steps, thank you very much :)