Search

how to connect rak gateway to chirpstack v4 using basics™ station (lns)

This guide explains how to connect a RAK gateway to ChirpStack v4 using Basics™ Station with LNS for secure TLS-based LoRaWAN® data communication.

Prerequisites

Before configuring the connection, make sure the following conditions are met:

  • A deployed ChirpStack v4 Network Server

  • Open the following ports on your ChirpStack server:

    • TCP 3001 for LoRaWAN packet forwarding

    • HTTP 8080 for ChirpStack Web UI access  

  •  A RAK Gateway running WisGateOS 2, version 2.2.x or above

    • Must have internet access

Register the Gateway in ChirpStack v4

This section provides step-by-step instructions for registering a RAK gateway in ChirpStack v4. For detailed instructions, refer to: How to Register a RAK Gateway in ChirpStack v4

Configure the Gateway

  1. Log in to the gateway's Web UI.

图形用户界面, 文本, 应用程序 描述已自动生成

  1. Go to LoRa > Configuration, and set Work Mode to Basics station.

Changing the working mode

  1. Click Configure Basics Station server setup to expand the relevant settings panel. Configure the following parameters:

图形用户界面, 文本, 应用程序 描述已自动生成

  • Basics Station Server Type: LNS Server

  • Server URL: Enter the WebSocket address of your ChirpStack server. Example: ws://18.156.176.220 (replace with your actual IP)

🗒️
NOTE
  • Use ws:// for non-encrypted WebSocket connections.
  • Use wss:// if you are using TLS, along with appropriate certificates (tc.cert, tc.key, tc.trust).

    •  

    • Server Port: 3001

    • Authentication Mode: Authentication for the ChirpStack server. Select None for this setup.

    1. Click Save changes to apply the configuration.

    Once everything is set up correctly, your gateway should show as online in the ChirpStack web interface.

    图形用户界面, 文本, 应用程序, 电子邮件 描述已自动生成

    Troubleshooting

    Issue Possible Cause Solution
    Gateway not showing as online Gateway cannot reach ChirpStack server (network issue or wrong IP/port)
    • Verify ChirpStack server IP/port is reachable from gateway
    • Ensure TCP port 3001 is open on the ChirpStack firewall
      GatewayEUI mismatch
    • Check gateway EUI in WebUI > Dashboard > Overview
    • Make sure the same EUI is used when registering the gateway in ChirpStack
      Wrong WebSocket protocol (ws:// vs wss://)
    • Use wss:// when TLS is enabled, and upload valid tc.cert, tc.key, tc.trust files
    • Use ws:// for non-TLS connections
    ChirpStack Web UI not accessible Port 8080 blocked
    • Allow port 8080 through firewall/security group
    • Access via http://<your-server-ip>:8080

    FAQs

    1. Where can I find my Gateway EUI?
    It's printed on the device labeled as “GWEUI”, or available in the WisGate Web UI under Dashboard > Overview.

    2. What WebSocket URL format should I use for ChirpStack LNS?

    • Use ws://<IP> for unsecured connections (dev/test)

    • Use wss://<IP> for production (with TLS + certs)

    3. Can I use a private IP for a server address?
    Yes, if both server and gateway are on the same LAN. Otherwise, use a public IP.

    4. What if my gateway firmware is older than WisGateOS 2.2.x?
    You need to update your gateway to WisGateOS 2.2.x or above, as support for ChirpStack v4 is only available from this version onwards. You can check your current version and perform the upgrade via the gateway’s Web UI under System > Firmware. For detailed steps and download links, refer to the official upgrade guide: WisGateOS 2 – Firmware Upgrade Documentation.

     

    Changelog
    • Version 1 - How to Connect RAK Gateway to ChirpStack v4 Using Basics™ Station (LNS)
      • Date Published: 10/30/2025

    Updated