Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't reregister landline account after inactivity: 400 (InvalidTransportModeException) #1666

Closed
theblackhole opened this issue Jan 6, 2025 · 2 comments · Fixed by #1706
Closed

Comments

@theblackhole
Copy link
Contributor

Hello and happy new year!

After 1.5 year of inactivity, I decided to use signal-cli again. My account was created with a landline number (so registered with voice) and I upgraded from 0.11.11 to the latest 0.13.11.

It seems like I have to register again because when I do signal-cli listAccounts I first get [401] Authorization failed! (AccountCheckException) then after a second check I get User is not registered. (NotRegisteredException)

But when I try to register, I get a Failed to register: StatusCode: 400 (InvalidTransportModeException) error.
I tried with and without the --reregister flag and it does this with the 2 devices I was using signal-cli on (one was linked to the other but I don't remember which was the main one so I tried to reregister on both)

date && signal-cli --verbose -a +33********* register --reregister --captcha 'signalcaptcha://signal-hcaptcha******'
lun. 06 janv. 2025 16:17:00 CET
2025-01-06T16:17:01.164+0100 [main] DEBUG org.asamk.signal.App - Starting signal-cli 0.13.11
2025-01-06T16:17:01.475+0100 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_DATA_HOME not set, falling back to home dir
2025-01-06T16:17:01.735+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2025-01-06T16:17:01.876+0100 [main] INFO  com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.sqlite.jdbc4.JDBC4Connection@458342d3
2025-01-06T16:17:01.878+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2025-01-06T16:17:02.734+0100 [main] DEBUG o.a.s.m.util.NumberVerificationUtils - No registration session, creating new one.
2025-01-06T16:17:03.925+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
2025-01-06T16:17:03.929+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
Failed to register: StatusCode: 400 (InvalidTransportModeException)
org.whispersystems.signalservice.api.push.exceptions.InvalidTransportModeException: StatusCode: 400
	at org.whispersystems.signalservice.internal.push.PushServiceSocket$RegistrationCodeRequestResponseHandler.handle(PushServiceSocket.java:3303)
	at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:2372)
	at org.whispersystems.signalservice.internal.push.PushServiceSocket.requestVerificationCode(PushServiceSocket.java:447)
	at org.whispersystems.signalservice.api.registration.RegistrationApi.requestSmsVerificationCode$lambda$3(RegistrationApi.kt:73)
	at org.whispersystems.signalservice.api.NetworkResult$Companion.fromFetch(NetworkResult.kt:44)
	at org.whispersystems.signalservice.api.registration.RegistrationApi.requestSmsVerificationCode(RegistrationApi.kt:72)
	at org.asamk.signal.manager.util.NumberVerificationUtils.requestVerificationCode(NumberVerificationUtils.java:96)
	at org.asamk.signal.manager.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:140)
	at org.asamk.signal.commands.RegisterCommand.register(RegisterCommand.java:80)
	at org.asamk.signal.commands.RegisterCommand.handleCommand(RegisterCommand.java:51)
	at org.asamk.signal.commands.CommandHandler.handleRegistrationCommand(CommandHandler.java:33)
	at org.asamk.signal.App.handleRegistrationCommand(App.java:265)
	at org.asamk.signal.App.handleCommand(App.java:174)
	at org.asamk.signal.App.init(App.java:144)
	at org.asamk.signal.Main.main(Main.java:56)
@theblackhole theblackhole changed the title Can't reregister account after inactivity: 400 (InvalidTransportModeException) Can't reregister landline account after inactivity: 400 (InvalidTransportModeException) Jan 6, 2025
@lateralas
Copy link

Hi,

i had the same problem today. After receiving error 400, (wait 60 seconds), you still need to :
signal-cli -a ACCOUNT register --voice
to initiate Account registration.
Then wait for the call, write down the verification code and complete the registration with “signal-cli -a ACCOUNT verify CODE”.
And always remember that it is now necessary to receive messages from time to time, otherwise the account will be deactivated again.

@theblackhole
Copy link
Contributor Author

theblackhole commented Feb 7, 2025

Thank you very much, it worked!

I think I made 2 mistakes:

  • At first I tried with --voice directly ➡ you have to do try a normal registration attempt, that's what I tried after my first attempt but...
  • ...I did too many retries and got rate limited ➡ you have to wait 60s between retries

I'll update the readme with the correct procedure for landline. Thanks again! 🙂

theblackhole added a commit to theblackhole/signal-cli that referenced this issue Feb 7, 2025
Update landline (`--voice`) registration procedure.

This closes AsamK#1666 (🤘)
AsamK pushed a commit that referenced this issue Feb 7, 2025
Update landline (`--voice`) registration procedure.

This closes #1666 (🤘)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants