V3 - drop join request - uplink channel not found

I’ve installed the latest version V3 (3.8.7). Application and gateway are running.
i’ve added a new device with:
LoRaWAN MAC : 1.0.2
Regional Parameters version:PHY V1.0.2 REV A
Frequency plan·:Europe 863-870 MHz (SF12 for RX2)

and set correctly JoinEUI (AppEUI), devEUI, APPkey
but when my device sends it a request for join to join server, error appears.

Drop join-request ( uplink channel not found )

this is the “Receive join-request”:

  "@type": "type.googleapis.com/ttn.lorawan.v3.UplinkMessage",
  "raw_payload": "AAkHAAAAAAAA4AsDgAMUAAAt4nUdXaI=",
  "payload": {
    "m_hdr": {},
    "mic": "dR1dog==",
    "join_request_payload": {
      "join_eui": "0000000000000709",
      "dev_eui": "0000140380030BE0",
      "dev_nonce": "E22D"
  "settings": {
    "data_rate": {
      "lora": {
        "bandwidth": 125000,
        "spreading_factor": 7
    "data_rate_index": 5,
    "coding_rate": "4/5",
    "frequency": "868099975",
    "timestamp": 2026573620
  "rx_metadata": [
      "gateway_ids": {
        "gateway_id": "gigino2",
        "eui": "246F28FFFF87FA80"
      "timestamp": 2026573620,
      "rssi": -45,
      "channel_rssi": -45,
      "snr": 9,
      "uplink_token": "ChUKEwoHZ2lnaW5vMhIIJG8o//+H+oAQtJ6sxgc="
  "received_at": "2020-07-22T21:03:44.678679865Z",
  "correlation_ids": [

this is the response:

  "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails",
  "namespace": "pkg/networkserver",
  "name": "uplink_channel_not_found",
  "message_format": "uplink channel not found",
  "code": 5

i add some screen of configuration.

Can u help me?

Schermata 2020-07-22 alle 23.12.02

Schermata 2020-07-22 alle 23.02.55 Schermata 2020-07-22 alle 23.13.21

Hi @luigirusso. What device are you connecting?

The issue is here: "frequency": "868099975",
Unless your device/gateway is doing something custom, the frequency should have been 868100000, which is the first frequency in EU868.
@johan any input here? I suppose this should be handled by the GS somehow?

Also, that’s a text value, not a number, in the JSON. Looking at, e.g., "bandwidth": 125000 one sees a proper number. (I don’t know if that affects any handling.)

JSON strings are used according to the protobuf spec: https://developers.google.com/protocol-buffers/docs/proto3#json
Frequency is a uint64

1 Like

hello, everybody,
thanks for replies.
my node and my gateway are Heltec esp32
I use following library:

Node: https://github.com/HelTecAutomation/ESP32_LoRaWAN/tree/master/examples/OTAA

Actually this configuration works on V2 (and on another stack :)). (I 've checked that even in V2, the package arrives with “868099975”)

I checked the gateway code but couldn’t find why it sets that value. It’set with correctly freq range (primary freq = 868100000) . Furthermore , the value ‘868099975’ It does not appear in the configuration file for any kind of format.

From gateway web console you can see that frequency is correct!

Schermata 2020-07-30 alle 16.23.58

Single channel gateways are hugely problematic for other users, the owner (that’s you), as you have discovered and are considered unsupportable.

So, sadly, until you get a proper gateway, you will find that you are stuck with some complex servers that you installed (well done, I haven’t tried yet!) and a workable device and a gateway that needs replacing.

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.