Invalid data-rate errors on fresh ChirpStack v4.16.2 installation (US915, ABP, DR0)

I’m facing an issue with Invalid data-rate errors on a fresh installation of ChirpStack v4.16.2. I see these errors both for uplink handling and when trying to schedule downlinks.

Environment

ChirpStack version: v4.16.2
Gateway: RisingHF RHF2S024 v1.1.3
Region and sub_band: US915_0
Gateway configuration: Standard 8-channel US915 configuration
Device activation: ABP
ADR: Disabled
Device data-rate: DR0 (SF10 BW125 kHz)
Device class: Class C
MAC version: LORAWAN 1.0.1
Regional parameters revision: A

Uplink

The device uplinks are received correctly and are published over MQTT, so RF reception seems to be working fine.

Uplink error seen in Network Server logs

**ERROR up{deduplication_id=1b9591d4-c817-4ecc-9598-571705fa8b0c}: chirpstack::uplink::data: Handle uplink error error=Invalid data-rate**

Even though this error appears, the uplink payload still gets published to MQTT and it is visible in the network server device page.

Downlink behavior

When I publish a downlink through MQTT:

The message is successfully enqueued in the Network Server.

However, it looks like the downlink never gets transmitted to the gateway.

Relevant logs:

*TRACE schedule{dev_eui=xxxxxxx0000013bb downlink_id=2252225287}: chirpstack::downlink::data: Handle schedule next-queue item flow
TRACE schedule{dev_eui=xxxxxxx0000013bb downlink_id=2252225287}: chirpstack::downlink::data: Selecting downlink gateway
TRACE schedule{dev_eui=xxxxxxx0000013bb downlink_id=2252225287}: chirpstack::downlink::data: Updating scheduler_run_after_ts for Class-C
INFO schedule{dev_eui=xxxxxxx0000013bb downlink_id=2252225287}: chirpstack::storage::device: Device partially updated dev_eui=xxxxxxx0000013bb
TRACE schedule{dev_eui=xxxxxxx0000013bb downlink_id=2252225287}: chirpstack::downlink::data: Checking if device has sent its first uplink already
TRACE schedule{dev_eui=xxxxxxx0000013bb downlink_id=2252225287}: chirpstack::downlink::data: Setting immediately flag
TRACE schedule{dev_eui=xxxxxxx0000013bb downlink_id=2252225287}: chirpstack::downlink::data: Setting tx-info for RX2
ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=Invalid data-rate*

Downlink configuration

Current RX settings:

RX1 delay: 1
RX1 data-rate offset: 0
RX2 data-rate: 8
RX2 frequency: 923300000

Lorawan Frame

Any guidance would be greatly appreciated.

Thanks!

{
    "phy_payload": {
        "mhdr": {
            "f_type": "UnconfirmedDataUp",
            "major": "LoRaWANR1"
        },
        "mic": [
            67,
            42,
            229,
            74
        ],
        "payload": {
            "f_port": 2,
            "fhdr": {
                "devaddr": "00f23c21",
                "f_cnt": 230,
                "f_ctrl": {
                    "ack": false,
                    "adr": false,
                    "adr_ack_req": false,
                    "class_b": false,
                    "f_opts_len": 0,
                    "f_pending": false
                },
                "f_opts": []
            },
            "frm_payload": "1420ff0000000c00000448"
        }
    },
    "rx_info": [
        {
            "channel": 5,
            "context": "KPHABA==",
            "crcStatus": "CRC_OK",
            "gatewayId": "8cf957ffff8003ee",
            "location": {},
            "nsTime": "2026-02-12T14:17:50.727773894+00:00",
            "rfChain": 1,
            "rssi": -11,
            "snr": 8.300000190734863,
            "uplinkId": 34476
        }
    ],
    "tx_info": {
        "frequency": 903300000,
        "modulation": {
            "lora": {
                "bandwidth": 125000,
                "codeRate": "CR_4_5",
                "spreadingFactor": 10
            }
        }
    }
}