Step-by-step gateway setup for ChirpStack Online using secure MQTT/TLS, ChirpStack Gateway Bridge, MQTT Forwarder, or legacy Semtech UDP.
Last updated: 18 July 2026
Server healthCollecting
Checking uptime and error-free probes from the public server.
Recommended connection method
Use secure MQTT/TLS whenever your gateway supports it. ChirpStack Online accepts encrypted gateway traffic on mqtt.chirpstack.online:8884 and requires a client certificate generated from the ChirpStack console. Use legacy UDP only for gateways that cannot run Gateway Bridge or MQTT Forwarder.
Create or log in to your account.Open Create account or Log in, then enter the real ChirpStack console.
Add the gateway in ChirpStack.Go to Gateways, add a gateway, and use the 16-character gateway EUI shown on the device label or gateway UI.
Select the correct region.For Romania and most EU deployments use EU868. The ChirpStack Online topic prefix is eu868.
Generate the gateway certificate.Open the gateway details page in ChirpStack and generate/download the MQTT/TLS certificate files for that gateway. Use that package only for the matching gateway EUI.
Check outbound access.The gateway network must allow outbound TCP traffic to mqtt.chirpstack.online:8884. For legacy UDP, it must allow UDP traffic to udp.growguard.eu:1700.
Option 1: Gateway Bridge over MQTT/TLS
This is the preferred option when your gateway can run ChirpStack Gateway Bridge. The packet forwarder sends packets locally to the bridge, and the bridge sends encrypted MQTT/TLS traffic to ChirpStack Online.
Install ChirpStack Gateway Bridge on the gateway.If the bridge runs on the same gateway, configure the Semtech packet forwarder to send to 127.0.0.1 on port 1700.
Copy certificate files.Create /etc/chirpstack-gateway-bridge/certs/ and copy the downloaded files as ca.pem, gateway.pem, and gateway-key.pem.
Update the bridge configuration.Use the configuration below, restart the bridge, then restart the packet forwarder if needed.
Verify in ChirpStack.Open the gateway page and check that Last seen updates after the next stats packet.
Use this option for gateways or images that support ChirpStack MQTT Forwarder. It forwards gateway packets to the same secure broker and uses the same gateway certificate package from ChirpStack.
Install or enable ChirpStack MQTT Forwarder.On many gateways this is available in the gateway UI or package manager.
Copy certificate files.Create /etc/chirpstack-mqtt-forwarder/certs/ and copy the downloaded files as ca.pem, gateway.pem, and gateway-key.pem.
Apply the MQTT Forwarder configuration.Use ssl://, port 8884, and topic prefix eu868.
Restart and check traffic.After restart, the gateway should appear online in ChirpStack when stats or uplinks are sent.
Use this only when the gateway does not support MQTT/TLS. UDP packet forwarder traffic on port 1700 is compatible with many gateways, but it is not encrypted end to end.
Add the gateway in ChirpStack first.The gateway EUI in ChirpStack must match the gateway hardware EUI.
Open the gateway packet forwarder settings.Depending on the gateway this may be called Semtech UDP, LoRa packet forwarder, packet forwarder, or gateway server.
Enter the UDP server settings.Use the server address and ports below, then save and restart the gateway service.
Verify last seen.In ChirpStack, the gateway should show stats within a few minutes if the gateway has internet access.
Security noteLegacy UDP is provided for compatibility. For customer deployments and sensitive telemetry, use Gateway Bridge or MQTT Forwarder over MQTT/TLS.
Troubleshooting checklist
Gateway EUI must be exactly 16 hexadecimal characters, without spaces or separators.
The certificate package must be generated for the same gateway that is connecting.
Gateway time/NTP must be correct, otherwise TLS certificate validation can fail.
The local packet forwarder must point to the local bridge/forwarder when using MQTT/TLS.
The network must allow outbound TCP to mqtt.chirpstack.online:8884.
Use region EU868 unless your hardware and deployment location require another region.
If Last seen does not update, restart the gateway service and check the gateway logs for TLS, certificate, DNS, or firewall errors.
Need help?
Email support is available within 12 hours. Send the gateway model, gateway EUI, chosen method, screenshot of the gateway network settings, and the latest gateway logs.