admin password doen´t save

[chopneck]

Hello.
I have a problem with HV3, Rak4631 and Xiao. Doesn´t save the password and i can´t access to my rpt remotely. I´ve tried several times, reboots, etc.
With 1.17.1 an 1.16.
Anyone with the same problem?

[chopneck]

This is with Meshcore

[liamcottle]

Hey there, the MeshCore App will only save the password you type in the login screen if the login is successful.

If you're unable to login, check the password is correct, and if it is, you may need to reset the path.
Reset Path can be found in the top right 3dot menu.

If you can't ping/trace the repeater and can't login even when in direct range, something else might be wrong and you may need to check radio settings, or connect the repeater to USB and check settings via https://config.meshcore.io

[cjshaker]

I installed 1.17.1 on a new Sensecap Solar Node P1-Pro, and ran into what may be the same problem. Using the serial port configuration editor, I set the admin password. I then attempted remote administration from my phone, which was connected to my companion device over WiFi. I would input my login password, but the repeater never logged me in. It just sat there.

I backdated the repeater to 1.16, and everything worked normally. Was able to set the admin password, and then log into the repeater from my phone via remote admin through my companion device (a T-deck running beta_63 Wadamesh).

[chopneck]

Exacto. El problema lo tuve con el mismo equipo (Sensecap Solar Node P1-Pro) inicialmente. Pero luego probé con Rak 4631 y Heltec v3. Sucedió lo mismo. No podía acceder en forma remota desde la app MeshC ni de WADAMESH. Intenté nuevos reflasheos, volver a version 1.16... y nada. Lo que tenía distinto, es que en Chile utilizamos un generador de llaves para identificar con 2 bytes los repetidores (por región y comuna). Eso hace que algunos compartan el prefijo de la llave pública (D1FF, D188, etc.). La clave definitivamente si estaba guardada, pero al intentar acceder en forma remota la app no lo reconoce. Generé otras llaves y funcionó. Estaba configurando 3 repetidores.
Pero el problema era con el prefijo D1... cuando generé las nuevas llaves, 2 repetidores (HV3 y RAK4631) quedaron con prefijo D8 y no hay conflicto... puedo acceder en forma remota desde cualquier companion

[cjshaker]

Here is a translation of Chopneck's post into English:
"Exactly. I initially had the problem with that same device (Sensecap Solar Node P1-Pro). But then I tested it with the Rak 4631 and Heltec v3, and the same thing happened. I couldn't access them remotely via the MeshC app or WADAMESH. I tried reflashing, reverting to version 1.16... and nothing worked. The difference was that, here in Chile, we use a key generator to identify repeaters using 2 bytes (based on region and municipality). This causes some of them to share the same public key prefix (D1FF, D188, etc.). The key was definitely saved, but the app wouldn't recognize it during remote access attempts. I generated different keys, and it worked. I was setting up three repeaters, but the issue was with the "D1..." prefix; when I generated the new keys, two of the repeaters (HV3 and RAK4631) ended up with a "D8" prefix, and there was no conflict—I can now access them remotely from any companion device."

[cjshaker]

My Sensecap Solar Node P1-Pro is still running MeshCore repeater image 1.16, but today, it now times out when I attempt to log
in to remotely administer it. Tried it with the iPhone app connected to my T-deck companion running Wadamesh via WiFi, and while connected via Bluetooth instead of WiFi. Tried rebooting my iPhone, tried rebooting my T-deck. Remote admin attempts still time out.

Yesterday, I was able to remotely administer the Sensecap Solar Node P1-Pro while running repeater image 1.16...

[cjshaker]

Exacto. El problema lo tuve con el mismo equipo (Sensecap Solar Node P1-Pro) inicialmente. Pero luego probé con Rak 4631 y Heltec v3. Sucedió lo mismo. No podía acceder en forma remota desde la app MeshC ni de WADAMESH. Intenté nuevos reflasheos, volver a version 1.16... y nada. Lo que tenía distinto, es que en Chile utilizamos un generador de llaves para identificar con 2 bytes los repetidores (por región y comuna). Eso hace que algunos compartan el prefijo de la llave pública (D1FF, D188, etc.). La clave definitivamente si estaba guardada, pero al intentar acceder en forma remota la app no lo reconoce. Generé otras llaves y funcionó. Estaba configurando 3 repetidores. Pero el problema era con el prefijo D1... cuando generé las nuevas llaves, 2 repetidores (HV3 y RAK4631) quedaron con prefijo D8 y no hay conflicto... puedo acceder en forma remota desde cualquier companion

Only the first character of two of the public keys for my repeaters is the same: C5D4 vs C35B.

[chopneck]

Thanks cjshaker. I though that this page have an automatic translator (is my chrome configuration). May be only you have the same first character only, but some repeater in your zone... some neighbour share the first byte (two equal characters) and so the app can´t recognize it exactly. The same issue occurs when you analize the path of a message, the app tell you that the data hops from "some" repeater thah have D1 like first byte. may be.....

[cjshaker]

Possibly related?
Remote management problem from t-deck #278
ALLFATHER-BV/wadamesh#278