Issues with Jooby Gateway (Basics Station) CUPS connection — SSL Fatal Alert

Issues with Jooby Gateway (Basics Station) CUPS connection — SSL Fatal Alert

Hello Team,

I am experiencing issues connecting a Jooby Outdoor Gateway LoRaWAN 400 EU to the ThingPark Community platform using the LoRa Basics Station protocol.

Environment details:

  • Platform: ThingPark Community

  • Base Station Configuration:

    • Manufacturer: Generic

    • Model: Basics Station packet forwarder (multiple regions)

    • LRR-UUID: 0016C0-001A79FFFE3F410C (EUI: 1A79FFFE3F410C)

    • RF Region: EU 863-870MHz

  • Gateway Side Settings:

    • Update Protocol: CUPS (Port 443)

    • Server URL: https://community.thingpark.io

    • Auth Mode: TLS Server Authentication (Server Only)

    • Trust Store: Amazon Root CA 1

    • Software version: Basics Station 2.0.6 (mbedTLS 2.28.0)

Problem Description: The gateway successfully initiates the TLS handshake, but the connection is immediately terminated by the server during the CUPS update-info request with a "Fatal Alert" message.

Logs from Gateway:

  1. Mar 06 10:34:13 jogls-3f410c station[9936]: 2026-03-06 10:34:12.980 [AIO:INFO] cups has no key+cert configured - running server auth only
  2. Mar 06 10:34:13 jogls-3f410c station[9936]: 2026-03-06 10:34:13.010 [CUP:VERB] Retrieving update-info from CUPS https://community.thingpark.io:443...
  3. Mar 06 10:34:13 jogls-3f410c station[9936]: 2026-03-06 10:34:13.012 [CUP:DEBU] CUPS Request: {"router":"1a:79ff:fe3f:410c","cupsUri":"https://community.thingpark.io:443","tcUri":null,"cupsCredCrc":3696675727,"tcCredCrc":2077607535,"station":"2.0.6(corecell/stdn) 2026-03-02 16:11:23","model":"corecell","package":"2.0.6","keys":[]}
  4. Mar 06 10:34:13 jogls-3f410c station[9936]: 2026-03-06 10:34:13.034 [AIO:ERRO] [4] Send failed: SSL - A fatal alert message was received from our peer
  5. Mar 06 10:34:13 jogls-3f410c station[9936]: 2026-03-06 10:34:13.034 [AIO:DEBU] [4] HTTP connection shutdown...
  6. Mar 06 10:34:13 jogls-3f410c station[9936]: 2026-03-06 10:34:13.034 [CUP:INFO] Interaction with CUPS failed - retrying in 1m