Network-Server does not JoinAccept device JoinRequest

Hi there.
Device EU868 LoraWan 1.0.2 OTAA adr ON, SF12, 14dB does not JoinAccept. Logs from server:

    sep 07 12:57:26 chirpstack-application-server[781]: time="2021-09-07T12:57:26+02:00" level=info msg="device-keys updated" ctx_id="<nil>" dev_eui=0018b20000022222
    sep 07 12:57:26 chirpstack-application-server[781]: time="2021-09-07T12:57:26+02:00" level=info msg="backend/joinserver: sending response" dev_eui=0018b20000022222 message_type=JoinAns receiver_id=000000 result_code=Success sender_id=0000000000000000 transaction_id=918492148
    sep 07 12:57:27 chirpstack-application-server[781]: time="2021-09-07T12:57:27+02:00" level=info msg="gateway ping created" ctx_id=62ef7f19-af45-4ffa-930b-c4dec75532c1 dr=60 frequency=60 gateway_mac=7076ff006403068c id=31743119
    sep 07 12:57:27 chirpstack-application-server[781]: time="2021-09-07T12:57:27+02:00" level=error msg="finished client unary call" ctx_id="<nil>" error="rpc error: code = Unknown desc = lorawan/band: invalid data-rate" grpc.code=Unknown grpc.ctx_id=48eadf30-dca8-413e-adec-3ce4f5712980 grpc.duration="864.916µs" grpc.method=SendProprietaryPayload grpc.service=ns.NetworkServerService span.kind=client system=grpc
    sep 07 12:57:27 chirpstack-application-server[781]: time="2021-09-07T12:57:27+02:00" level=error msg="send gateway ping error: send ping error: send proprietary payload error: rpc error: code = Unknown desc = lorawan/band: invalid data-rate"

....

   *sep 07 12:57:26 chirpstack-network-server[780]: time="2021-09-07T12:57:26+02:00" level=info msg="sent uplink meta-data to network-controller" ctx_id=6f7f1b49-93bc-4a2b-a3b1-0b3dc98dc92f dev_eui=0018b20000022222
    sep 07 12:57:26 chirpstack-network-server[780]: time="2021-09-07T12:57:26+02:00" level=info msg="device-queue flushed" ctx_id=6f7f1b49-93bc-4a2b-a3b1-0b3dc98dc92f dev_eui=0018b20000022222
    sep 07 12:57:26 chirpstack-network-server[780]: time="2021-09-07T12:57:26+02:00" level=info msg="device-session saved" ctx_id=6f7f1b49-93bc-4a2b-a3b1-0b3dc98dc92f dev_addr=0049539e dev_eui=0018b20000022222
    sep 07 12:57:26 chirpstack-network-server[780]: time="2021-09-07T12:57:26+02:00" level=info msg="device-activation created" ctx_id=6f7f1b49-93bc-4a2b-a3b1-0b3dc98dc92f dev_eui=0018b20000022222 id=19208
    sep 07 12:57:26 chirpstack-network-server[780]: time="2021-09-07T12:57:26+02:00" level=info msg="device updated" ctx_id=6f7f1b49-93bc-4a2b-a3b1-0b3dc98dc92f dev_eui=0018b20000022222
    sep 07 12:57:26 chirpstack-network-server[780]: time="2021-09-07T12:57:26+02:00" level=info msg="gateway/mqtt: publishing gateway command" command=down downlink_id=6f7f1b49-93bc-4a2b-a3b1-0b3dc98dc92f gateway_id=7076ff00560703db qos=0 topic=gateway/7076ff00560703db/command/down
    sep 07 12:57:26 chirpstack-network-server[780]: time="2021-09-07T12:57:26+02:00" level=info msg="storage: downlink-frame saved" ctx_id=6f7f1b49-93bc-4a2b-a3b1-0b3dc98dc92f token=20852
    sep 07 12:57:27 chirpstack-network-server[780]: time="2021-09-07T12:57:27+02:00" level=error msg="finished unary call with code Unknown" ctx_id=48eadf30-dca8-413e-adec-3ce4f5712980 error="rpc error: code = Unknown desc = lorawan/band: invalid data-rate" grpc.code=Unknown grpc.method=SendProprietaryPayload grpc.service=ns.NetworkServerService grpc.start_time="2021-09-07T12:57:27+02:00" grpc.time_ms=0.097 peer.address="127.0.0.1:49160" span.kind=server system=grpc

Any help with this issue? Where could be the problem? Server or device configuration?
Thank you.

Hi,

We noticed the same behaviour on our chirpstack deployment. Is it random or always repeatable ?
Which version do you use ? We have this issue with latest version (GB 3.13.1 / NS 3.15.0 / AS 3.17.0) ans the previous one (GB 3.12.0 / NS 3.14.0 / AS 3.16.0). The working stack without this strange issue is GB 3.11.0 / NS 3.13.0 / AS 3.14.0.

Here is the post on this forum I dropped relating our issue, without any answer for the moment : Downlink fcount equals 0 issue
Have you got something similar ?

Some other posts seem to show up some similar issues :

could you have a look to devnonce field in join…are you sure the field is correct when it fails