Chirpstack v 4.11.1

[kskenyon]

I’m tying to adjust my expectations. Tried to get this running on Chirpstack 4.11.1 but I’m struggling getting it to run with docker-compose. It loads and runs but has some incomprehensible errors in the log. Also doesn’t like my delegate.bin file. Probably a deal breaker. Is that required? Should I convert it to hex? I tried and it didn’t like that either.

Should this be compatible with the latest Chirpstack? Is that too much to expect with the latest docker release?

Kevin

[ederuiter]

Hi Kevin,

As far as I know it should be compatible with the latest chirpstack; however I know there might be an issue with the format of newer keys. Helium recently introduced a change in how the keys are stored that is not yet compatible with our tool.
I haven't had time to investigate/fix this yet.

It would help if you can provide met with some logs that show the errors you are getting.

Kind regards,

Eric

[kskenyon]

Thanks for the reply. It does look related to parsing my delegate.bin file. I put it in the same subdirectory with docker-compose.yml and also in the configuration/chirpstack subdirectory because it wasn’t clear where it should go. Running on x86_64 Debian 12. No encryption chip present. ***@***.***:~/chirpstack-docker$ sudo docker-compose up |grep helium-route-updater Starting chirpstack-docker_mosquitto_1 ... done Starting chirpstack-docker_redis_1 ... done Starting chirpstack-docker_postgres_1 ... done Starting chirpstack-docker_chirpstack-gateway-bridge-us915_1 ... done Starting chirpstack-docker_chirpstack_1 ... done Starting chirpstack-docker_helium-route-updater_1 ... done Attaching to chirpstack-docker_mosquitto_1, chirpstack-docker_redis_1, chirpstack-docker_postgres_1, chirpstack-docker_chirpstack-gateway-bridge-us915_1, chirpstack-docker_chirpstack_1, chirpstack-docker_helium-route-updater_1 helium-route-updater_1 | Starting helium-route-updater_1 | [sync] starting full sync helium-route-updater_1 | panic: ed25519: bad private key length: 0 helium-route-updater_1 | helium-route-updater_1 | goroutine 68 [running]: helium-route-updater_1 | crypto/ed25519.sign({0xc0003b6100?, 0x4f?, 0x2?}, {0x0?, 0x521390?, 0xe0?}, {0xc0003b40f0?, 0x0?, 0x0?}, {0x0, ...}, ...) helium-route-updater_1 | /usr/local/go/src/crypto/ed25519/ed25519.go:209 +0x6a5 helium-route-updater_1 | crypto/ed25519.Sign(...) helium-route-updater_1 | /usr/local/go/src/crypto/ed25519/ed25519.go:190 helium-route-updater_1 | github.com/thisisdevelopment/helium-route-updater/pkg/helium-crypto.(*KeyPair).Sign(0xc09040?, {0xc0003b40f0, 0x4f, 0x4f}) helium-route-updater_1 | /app/pkg/helium-crypto/keypair.go:47 +0xba helium-route-updater_1 | github.com/thisisdevelopment/helium-route-updater/pkg/helium-crypto.SignRequest[...](0xc00005c028, 0xc0001a38c0?) helium-route-updater_1 | /app/pkg/helium-crypto/signed-request.go:30 +0x37c helium-route-updater_1 | main.sync({0xc000042010, 0x23}, 0x1113350?, 0xc0000911d0?, 0xc00021ea30, {0xc10fd8, 0xc0003aa060}) helium-route-updater_1 | /app/cmd/helium-route-updater/main.go:68 +0x29a helium-route-updater_1 | created by main.main in goroutine 1 helium-route-updater_1 | /app/cmd/helium-route-updater/main.go:52 +0x479 chirpstack-docker_helium-route-updater_1 exited with code 2 Everything else in docker-compose.yml continues to run OK.

…

On Feb 17, 2025, at 10:44 AM, Eric de Ruiter ***@***.***> wrote: ederuiter left a comment (thisisdevelopment/helium-route-updater#7) Hi Kevin, As far as I know it should be compatible with the latest chirpstack; however I know there might be an issue with the format of newer keys. Helium recently introduced a change in how the keys are stored that is not yet compatible with our tool. I haven't had time to investigate/fix this yet. It would help if you can provide me with some logs that show the errors you are getting. Kind regards, Eric — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. <#7 (comment)> <https://github.com/notifications/unsubscribe-auth/AF4WTTCSJHQQKW5G7ESUVQD2QH7WRAVCNFSM6AAAAABXHEJII6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGQ4DENZQG4> ederuiter left a comment (thisisdevelopment/helium-route-updater#7) <#7 (comment)> Hi Kevin, As far as I know it should be compatible with the latest chirpstack; however I know there might be an issue with the format of newer keys. Helium recently introduced a change in how the keys are stored that is not yet compatible with our tool. I haven't had time to investigate/fix this yet. It would help if you can provide me with some logs that show the errors you are getting. Kind regards, Eric — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4WTTCSJHQQKW5G7ESUVQD2QH7WRAVCNFSM6AAAAABXHEJII6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRTGQ4DENZQG4>. You are receiving this because you authored the thread.