Get no registration code

[matzgewinn]

On OnePlus 5, Ubuntu Touch, RC, after Reinstalling Axolotl there will be no registration code

[After several messups with the app I tried a complete reinstall. But I can get no registrationcode.]

Steps to Reproduce

1. Install the app. Open it
2. Insert your phone number. check out the captcha.
3. wait for the registration code

Expected behavior: one should get the code per sms

Actual behavior: nothing

Versions

1.6.0

Device

Oneplus 5 with Ubuntu Touch, RC

Link to Debug Log

Please provide a link to debug from ~/.cache/upstart/application-click-textsecure.nanuc_textsecure*.log Be careful it contains sensible data application-click-textsecure.nanuc_textsecure_1.6.0.log

[Blackoverflow]

The first unexpected line In the provided log is [31mERRO[0m[0000] [axolotl] creating settings file open /home/phablet/.config/textsecure.nanuc/settings.yml: no such file or directory Maybe the config directory was not yet created (which strangely is created after trying to create the settings file)

The lines about the captcha seem fine, but there is no log about what happens next.

Please can someone change the loglevel to debug and try it again? To change the loglevel before registration, edit the corresponding line in /home/phablet/.config/textsecure.nanuc/config.yml to read loglevel: debug

[matzgewinn]

After installing the .click package textsecure.nanuc_1.6.0_939build_arm64.click Axolotl does not start. application-click-textsecure.nanuc_textsecure_1.6.0.log

[Blackoverflow]

You currently have the cofing.yml with only loglevel:debug in it, correct? If so, please delete it (or rename it) and try to start Axolotl. The app should create a config.yml. It that one stays empty, then that's a problem for itself.

[matzgewinn]

I just de- and then reinstalled axolotl. I thinks that created a new confiig.yml. I will have a look if its empty.

Am Thu, 3 Nov 2022 12:48:07 -0700, Blackoverflow schrieb:

You currently have the cofing.yml with only loglevel:debug in it, correct? If so, please delete it (or rename it) and try to start Axolotl. The app should create a config.yml. It that one stays empty, then that's a problem for itself.

-- Sent with Dekko - the convergent email app

[matzgewinn]

Its true: file is empty.

Am Thu, 3 Nov 2022 12:48:07 -0700, Blackoverflow schrieb:

You currently have the cofing.yml with only loglevel:debug in it, correct? If so, please delete it (or rename it) and try to start Axolotl. The app should create a config.yml. It that one stays empty, then that's a problem for itself.

-- Sent with Dekko - the convergent email app

[nalysius]

The initial problem was caused by the new certificate used by Signal since October 26th, which use their own root certificate. This issue has been fixed on yesterday by updating libsignal-service.rs.

Now the registration code is received by SMS, but after submitting the code an error occurred. Below my log file. I think the most important line is 115, a missing field "name" in a JSON object. It might be caused by the update of libsignal-service that added this field. Line 134-136 are errors too: "bad handshake".

application-click-textsecure.nanuc_textsecure_1.6.0.log

[peter33826]

I can confirm this issue on Nexus 5 with latest Ubuntu Touch and latest Axolotl.

[ncorder]

@nanu-c Is the registration code supposed to be texted to me or is it just the pin from my old signal device/account?

I am not receiving a registration code as well. Pixel 3a XL

[darkdragon-001]

Same for me for Flatpak v1.6.0 on Pinephone with German phone number.

[TriVoxel]

I also experience this issue on Google Pixel 3a, with the new update from 12/18/2022 on Ubuntu Touch OTA-24. It makes the app completely unusable.

To clarify, I do not even receive an SMS text at all after completing the Captcha.

[ph1l]

same for me, using a flatpak on librem5 pureos.

[TriVoxel]

@nanu-c here is a log generated from a fresh install (2022.12.18) with full cache, config, and app data cleared: application-click-textsecure.nanuc_textsecure_1.6.0.log

I got to the screen asking for the registration pin, and couldn't get any further. Hope it helps!

[nanu-c]

@TriVoxel i have bought a new sim card and i have registered axolotl with no problems. In the past we had conflicts with some blocklist of uadblock because you need to solve the recaptcha from google and also signal hosts their services at amazon/aws and google. Do you have some block list or is it possible for your phonenumber to receive messages?

Further you need to unregister with signal if you have used an official client, because we don't support the profile pin. If you don't do so, the number is blocked for 7 days for new registrations.

[TriVoxel]

@nanu-c Hi, thanks for the reply. I can receive SMS and calls. I also do not have Amazon or Google blocked. I will try to unregister my official Signal phone app, however the first time I tried to set up Signal at all was with Axolotl. I'll wait a week before trying, though. Thanks for the feedback.

[nanu-c]

I always try with another cheap simcard, here you can get them for 2€ or so.

[wakamex]

Further you need to unregister with signal if you have used an official client, because we don't support the profile pin. If you don't do so, the number is blocked for 7 days for new registrations.

by unregister with signal do you mean you have to sign out on all devices? that seems quite prohibitive

[nanu-c]

Axolotl is an replacement for signal android / ios, it's not yet another signal desktop. by logout i mean

1.    In Signal, tap your profile. > Account > Delete account.
2.    Enter your Signal number.
3.    Tap Delete account.
4.    Confirm Delete account.

[TriVoxel]

Unfortunately, even after I waited 7 days, deleted the Signal account, deleted token in Axolotl and cleared all settings and cache in UT Tweak tool, I cannot create a Signal accoubt with Axolotl. I don't know if my operating system is at fault, or Axolotl, but it does not send an SMS and I get an error message in the app telling me to delete my account and try again. My SMS is fully functional and I use it every day. I used it to register my Signal app on Android after giving up with Axolotl for the time being. Perhaps there is a chance the bug is specific to Pixel 3a, Ubuntu Touch OTA 24, or something else. Basically, it never sends a text. I'm actually not sure what a working setup process looks like or what to expect. Does anyone have a video demonstrating the setuo process so I can be sure I am not at fault?

[peter33826]

@TriVoxel: I can confirm the behavior on my Nexus5, latest Ubuntu Touch.

I unregistered with Android client, waited 7 days and registered again with Axolotl. I do NOT received any SMS with Axolotl. When I register again with Android client, it works out of the box.

@nanu-c: Before the update in August (?) Axolotl worked great. Is it possible to switch back to the old status?

[nanu-c]

The problem is, signal changed things for the registration and for the groups. To solve that we need a new zkgroup lib but that has been merged to libsignal. To solve the problems we are working on replacing the axolotl backend with a rust on build on top of presage. That gives us the possibility to avoid to write nasty go <-> cgo <-> c <-> rust-ffi <-> rust (a la zkgroup) or go <-> websocket <-> rust (a la crayfish) bridges. This will take 2 more weeks or so, but then axolotl can also be an replacement for signal desktop with an existing signal installation. Therefore we recommend to use waydroid -> https://waydro.id/ with signal from the website until everything is worked out.

[TriVoxel]

Thank you for the update. I really appreciate your efforts and look forward to that update! If you need someone to help test that new backend when it's ready, hmu.

[Bit-Interested]

Same problem on fairphone FP3 / ubports: Ubuntu 16.04 (OTA-24) No Signal-account registered, yet.

Registration process stops waiting for registration pin... Are there already any ideas / fixes in sight?

[Bit-Interested]

In addition the first ERROR in .cache/upstart/application-click-textsecure.nanuc_textsecure_1.6.0.log says:

ERRO[2023/02/08 17:04:47] [axolotl-ws] wsReader websocket: close 1001 (going away)

Maybe the communication with the Signal server does not work? --Another hint could be that I tried to fill in a random registration code. Just in order to see what happens. As a matter of fact, I got no error message (what would certainly be the case if the Signal server would have tried to verify the entered registration code) but received the (not) working front-end.

[robert-winkler]

Hi, I have the same issue with v1.6.0 .deb on Mobian. I give my phone number, click the captcha images, and wait for the registration code that never arrives.

Is there any other way, I could register Axolotl? I'm using a separate SIM card for my Mobian PinePhone; telephony/SIM works.

BTW: I'm living in Mexico, and the Axolotl should feel at home 😁.

[nanu-c]

This will be solved in #985 where we replace the go backend with a rust backend

[nanu-c]

One of the problems is, they changed from recaptcha to humancaptcha for registration.

[jakub-bidzan]

same happens on google pixel 3A

[ell1e]

Same here on PinePhone, no registration pin ever arrives via text and I remain stuck at the axolotl screen asking me to enter it. I'm reachable otherwise via phone services just fine. I used the axolotl flatpak with the phosh desktop. I never used signal before so I shouldn't have some blocked number.

[nanu-c]

This will be solved in https://github.com/nanu-c/axolotl/pull/985 where we replace the go backend with a rust backend. And it already works, but we need to fix the debian crosscompiling and packaging. For ut 20.04 there are already packages in the ci.

[TriVoxel]

This will be solved in #985 where we replace the go backend with a rust backend. And it already works, but we need to fix the debian crosscompiling and packaging. For ut 20.04 there are already packages in the ci.

Hey, it seems CI is skipping the UT packaging step due to (presumably) the Debian errors.

[WuShufei]

Bug is also present in snap version under Raspbian 10 buster for armv7l / armhf. I shall keep abreast. Thanks for your attention, devs!

[peter33826]

Does anyone have any idea when this bug will be fixed?

[josch]

Since #985 just got merged, does that mean that this issue is fixed?

[nanu-c]

Unfortunately not, it was working but signal turned of another old registration api and we need this to finished -> https://github.com/whisperfish/libsignal-service-rs/issues/206

[nanu-c]

But you can register as secondary device like signal desktop

[josch]

Thanks, I subscribed to that issue. I have to wait for that because I do not own a smartphone, so for me, axolotl is my primary client. Thanks a lot for all your work! :+1:

[josch]

For everybody who is also subscribed to this issue and waiting patiently: https://github.com/whisperfish/libsignal-service-rs/pull/285 which fixes https://github.com/whisperfish/libsignal-service-rs/issues/206 was just merged. :partying_face:

[ell1e]

was just merged. 🥳

Is this meant to be working then? Sadly, I still don't get a registration pin. My apologies if it's intended that this will still take a while to release and if this is a silly question :flushed:

[flamingradian]

This still might need https://github.com/whisperfish/presage/pull/245 merged and an update to the dependency in Cargo.toml here. One remaining review comment in the PR got an eyes emoji by the contributor.

[josch]

This still might need whisperfish/presage#245 merged and an update to the dependency in Cargo.toml here. One remaining review comment in the PR got an eyes emoji by the contributor.

And now it got merged. :smile:

[ell1e]

since the latest release of axolotl here on github seems to be from february, does anybody know if the fix made it to flathub yet? I apologize for the noise and please don't consider this as a request to hurry whatsoever, I'm just curious!

[ell1e]

Update: I just tested this myself, it seems like this doesn't work yet with the latest Flathub version.