# Gateway connects to TTN but operates on AS923 instead of EU868 – moved to CUPS to change frequency, now CUPS not connecting

**URL:** <https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808>\
**Category:** Gateways\
**Tags:** dragino\
**Created:** [December 10, 2025, 1:13pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808 "2025-12-10T13:13:17Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dm778866](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/d/c5a1d2/32.png) [@dm778866](https://www.thethingsnetwork.org/forum/u/dm778866)\
**Post date:** [December 10, 2025, 1:13pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/1 "2025-12-10T13:13:17Z")

</div>

I am working with a **Dragino LoRaWAN gateway (EU868 hardware)** and **The Things Network / The Things Stack Cloud**.

### **Initial situation**

Initially, I registered the gateway on TTN using **normal (non-CUPS) configuration**.  
The gateway **successfully connected to TTN** , and I could see it online in the console.

However, **end devices were not able to communicate properly through the gateway**.

## **Issue Discovered During Debugging**

While troubleshooting, I checked the gateway logs (`LogRead`) and noticed that the gateway was **operating on 923 MHz frequencies (AS923)** instead of EU868.

Example observed frequencies:

```
**LogRead**
 **FreqINFO:**
Gateway Channels frequency**

chan_multSF_0
Lora MAC, 125kHz, all SF, 923.2 MHz**

chan_multSF_1
Lora MAC, 125kHz, all SF, 923.4 MHz**

chan_multSF_2
Lora MAC, 125kHz, all SF, 922.2 MHz**

chan_multSF_3
Lora MAC, 125kHz, all SF, 922.4 MHz**

chan_multSF_4
Lora MAC, 125kHz, all SF, 922.6 MHz**

chan_multSF_5
Lora MAC, 125kHz, all SF, 922.8 MHz**

chan_multSF_6
Lora MAC, 125kHz, all SF, 923.0 MHz**

chan_multSF_7
Lora MAC, 125kHz, all SF, 922.0 MHz**

## **chan_Lora_std
Lora MAC, 250kHz, SF7, 922.1 MHz**

## **chan_FSK
FSK 50kbps, 921.8 MHz**

IoT Server Connection Ctate:
Logread FWD State:
Logread Error:
Logread RxTxJson:
Logread PULL State:

This suggests the gateway is not receiving EU868 from CUPS.

```

Because of this frequency mismatch, devices configured for **EU868** could not communicate correctly.

## **Understanding After Research**

After further research, I realized that:

- The **cluster I am using automatically registers gateways as AS923**
- This seems to be the default behavior based on cluster/region
- However, **EU868 is allowed in my deployment region (UAE)**

So the problem was **not connectivity** , but **wrong frequency configuration**.

## **Decision: Move to EU868 Using CUPS**

Since the default registration kept using AS923, I looked for a way to **force the gateway to operate on EU868**.

Based on TTN documentation, the recommended approach is to use **LoRa Basics Station with CUPS** , where:

- Frequency plan is pushed from the server
- Gateway configuration becomes centrally managed
- Frequency can be changed by server-side configuration

Reference documentation:  
[Using CUPS to redirect to a different LNS | The Things Stack for LoRaWAN](https://www.thethingsindustries.com/docs/hardware/gateways/concepts/lora-basics-station/cups-forwarding/#:~:text=Copy%20the%20LNS%20key%20from,redirect%20to%20the%20target%20instance).

## **Actions Taken (In Sequence)**

1. Registered the gateway on **TTN / TTS Cloud**

2. Set the gateway **frequency plan to EU868** in the console

3. Switched the gateway to:  
LoRa Basics Station – TTN

4. Started configuring **CUPS**

5. Generated API keys from TTN:

6. LNS authentication key

- CUPS authorization key
- Added the keys to the gateway configuration
- Rebooted and retried multiple times

## **Current Problem**

After enabling CUPS:

- The gateway **no longer completes connection to CUPS**

- Gateway logs show **CUPS connection errors**

- Because CUPS is not connecting, the **EU868 configuration is never applied**

- Gateway continues to show **AS923 frequencies in LogRead**

- Devices still cannot communicate properly

**SystemLogs:**  
2025-12-10 12:24:39.607 [AIO:DEBU] [-1] HTTP connection shutdown… 2025-12-10 12:24:39.607 [CUP:ERRO] CUPS connect failed - URI: [https://as1.cloud.thethings.network:443](https://as1.cloud.thethings.network/) 2025-12-10 12:24:39.607 [CUP:INFO] Interaction with CUPS failed - retrying in 1m 2025-12-10 12:24:39.608 [TCE:INFO] Starting TC engine 2025-12-10 12:24:39.608 [TCE:ERRO] No TC URI configured 2025-12-10 12:24:39.608 [TCE:INFO] Router rejected or retry limit reached. Invoking CUPS. 2025-12-10 12:24:39.609 [TCE:INFO] Terminating TC engine 2025-12-10 12:24:39.609 [CUP:INFO] Starting a CUPS session in 60 seconds. 2025-12-10 12:24:39.609 [\__\_:INFO] lgw\_stop:1202: — IN Note: LoRa concentrator was not started… 2025-12-10 12:25:39.610 [CUP:INFO] Starting a CUPS session now. 2025-12-10 12:25:39.610 [CUP:INFO] Connecting to CUPS … [https://as1.cloud.thethings.network:443](https://as1.cloud.thethings.network/) (try #2) 2025-12-10 12:25:39.613 [AIO:INFO] /etc/station/cups.trust: cert. version : 3 serial number : 82:10:CF:B0:D2:40:E3:59:44:63:E0:BB:63:82:8B:00 issuer name : C=US, O=Internet Security Research Group, CN=ISRG Root X1 subject name : C=US, O=Internet Security Research Group, CN=ISRG Root X1 issued on : 2015-06-04 11:04:38 expires on : 2035-06-04 11:04:38 signed using : RSA with SHA-256 RSA key size : 4096 bits basic constraints : CA=true key usage : Key Cert �2025-12-10 12:25:39.616 [AIO:ERRO] [-1] HTTP connect failed: NET - Failed to get an IP address for the given hostname 2025-12-10 12:25:39.616 [AIO:DEBU] [-1] HTTP connection shutdown… 2025-12-10 12:25:39.616 [CUP:ERRO] CUPS connect failed - URI: [https://as1.cloud.thethings.network:443](https://as1.cloud.thethings.network/) 2025-12-10 12:25:39.616 [CUP:INFO] Interaction with CUPS failed - retrying in 1m 2025-12-10 12:25:39.616 [TCE:INFO] Starting TC engine 2025-12-10 12:25:39.617 [TCE:ERRO] No TC URI configured 2025-12-10 12:25:39.617 [TCE:INFO] Router rejected or retry limit reached. Invoking CUPS. 2025-12-10 12:25:39.617 [TCE:INFO] Terminating TC engine 2025-12-10 12:25:39.618 [CUP:INFO] Starting a CUPS session in 60 seconds. 2025-12-10 12:25:39.618 [\__\_:INFO] lgw\_stop:1202: — IN Note: LoRa concentrator was not started…

Any guidance from users running **Dragino gateways with LoRa Basics Station on TTS Cloud** would be greatly appreciated, especially regarding correct CUPS endpoints and expected behavior when CUPS connectivity fails.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![dm778866](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/d/c5a1d2/32.png) [@dm778866](https://www.thethingsnetwork.org/forum/u/dm778866)\
**Post date:** [December 11, 2025, 7:45am UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/2 "2025-12-11T07:45:54Z")

</div>

## **Follow-up Update (Clear Summary + New Findings)**

Posting a structured update to make the issue clearer and to request further guidance from the community.

* * *

## **1. Current Problem in One Line**

The gateway is configured for **EU868** in The Things Stack Cloud,  
but the Dragino device continues to run on **AS923 frequencies** , and CUPS never returns a **TCURI**.

Because of this, the correct frequency plan is never applied and EU868 devices cannot communicate.

* * *

## **2. What We Are Observing**

Despite selecting **EU868** in the TTS console, LogRead consistently shows:

- 923.2 MHz
- 923.4 MHz
- 922.2 MHz
- 922.4 MHz
- 922.6 MHz
- … etc.

That means the gateway boots using AS923 defaults instead of the configured EU868 plan.

* * *

## **3. CUPS Behavior**

After switching to **LoRa Basics Station → TTN** , the gateway loops with:

```auto
301 Moved Permanently
Failed to retrieve TCURI from CUPS
No TC URI configured

```

What has been verified:

- Correct CUPS server URI
- Correct CUPS authorization key
- Correct LNS authentication key
- Gateway EUI matches TTS console
- Tried both eu1 and as1 clusters
- Factory reset + reconfiguration

Still no **TCURI** received, and no frequency plan update is applied.

* * *

## **4. Sequence of Actions Performed**

To avoid confusion, here is the step-by-step sequence already completed:

1. Registered gateway on TTS Cloud
2. Set frequency plan to **EU868**
3. Switched gateway to **LoRa Basics Station**
4. Entered:

- CUPS URI
- CUPS auth key
- LNS key

1. Rebooted gateway
2. Tried alternate clusters (eu1 and as1)
3. Deleted + recreated the gateway
4. Double-checked the EUI and keys

But the gateway still:

- Boots up on **AS923** , and
- CUPS keeps returning **301 Moved Permanently** without a TCURI

* * *

## **5. Questions for the Community**

Looking for help from anyone familiar with Dragino + Basic Station + TTS Cloud:

1. **Does TTS enforce frequency plans based on region, ignoring the console selection?**  
(Meaning: could it be overriding EU868 and forcing AS923?)
2. **Why would CUPS refuse to return a TCURI even with correct keys and URIs?**
3. **Is there a specific or alternate CUPS endpoint needed for Basic Station gateways on TTS Cloud (EU868)?**
4. **Is it normal for Dragino gateways to fall back to AS923 when CUPS does not deliver update-info?**
5. **Has anyone successfully run a Dragino gateway in EU868 on TTS Cloud via CUPS?**  
If yes, what exact CUPS/LNS endpoints were used?

* * *

## **6. Request for Assistance**

I am still debugging this and would appreciate guidance from anyone who has faced similar issues.  
If additional logs/screenshots are needed, I can share them.

> **[Connect Dragino LPS8N with Lora Basics™ Station](https://www.thethingsindustries.com/docs/hardware/gateways/models/dragino-lps8/lbs/)**

---

<div class="post-metadata">

**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\
**Post date:** [December 11, 2025, 9:37am UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/3 "2025-12-11T09:37:54Z")

</div>

One question - when running in ‘classic’ vs CUPS mode how did you configure the Dragino GW in local console?

> [@dm778866](#):
>
> While troubleshooting, I checked the gateway logs (`LogRead`) and noticed that the gateway was **operating on 923 MHz frequencies (AS923)** instead of EU868.

Had you actually configured directly for 868Mhz operation? I note you ‘registered’ as 868 in TTN/TTI console but how was actual device set? Might be worth checking/trying again if you are struggling with CUPS based implementation…..

---

<div class="post-metadata">

**Author:** ![dm778866](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/d/c5a1d2/32.png) [@dm778866](https://www.thethingsnetwork.org/forum/u/dm778866)\
**Post date:** [December 11, 2025, 2:35pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/4 "2025-12-11T14:35:33Z")

</div>

Thanks Jeff-UK for your response.

 ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/2/8/2855599a0e43dd3389d6c5a8a6ca06e0a7ca8ec0.jpeg)  
I have done Factory reset to default which means now the Gateway is on reset condition.  
No TTN configured not anything else. (just connected to wifi)

But it is not showing me the options for the reset of the frequencies and this is a very strange behaviour.

Because the Dragino DLSO8N is 868 supported but the web UI is not showing me the option to select this specific band

 ![Dragino cover image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/c/f/cfda2379224b45d71dfcc4902b0fb2397e2b0ae0.jpeg)

and also the LogRead are showing me the AS923 Band frequcies of receiver channels

 ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/6/4/64b3783a140157ea74f02aee97a893e8f3110612.jpeg)

What do you say what is the core issue here?  
Am I missing something important.

Sorry for posting these images but I feel this is the best way to communicate the issue

---

<div class="post-metadata">

**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\
**Post date:** [December 11, 2025, 7:35pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/5 "2025-12-11T19:35:46Z")

</div>

1st try to update the gw firmware version and see if you get EU868 option. If not contact Dragino support. Mispacked or misprogrammed SKU’s are not unheard of so label may not match actual shipped build. In early days of the TTIG I had a mispack where one of a half dozen ordered from a uk disty in single box had external labels saying EU868 but one proved to be a 915 on investigation. Had same problem of devices not being heard…..opening up confirmed a config smt resistor on pcb in 915 vs 868 config position……just got seller to replace.

**Update:** I notice you have the -EC25 variant with embedded Quectel EC25 cellular modem. Which version did you order? What was shipped (invoice/dispatch/shipper docs, box, inners etc.) There seems to be atleast three variants with just the Freq marking block to discriminate on the GW case label so scope for error:

**Regional Variants:** The EC25 version is available in multiple regional configurations to match local cellular frequencies:

- **EC25-E:** Standard for Europe.

- **EC25-AFX:** Optimized for North American carriers.

- **EC25-AUX:** Optimized for regions like Latin America and Australia.

Looks like the E vs AFX vs AUX isnt called out directly on the device?

---

<div class="post-metadata">

**Author:** ![Somsak](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/somsak/32/45700_2.png) [@Somsak](https://www.thethingsnetwork.org/forum/u/Somsak)\
**Post date:** [December 16, 2025, 5:34am UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/6 "2025-12-16T05:34:04Z")

</div>

Your DLOS8N is coming with AS923 firmware. You might need to replace it with international firmware. Download at [click](https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/DLOS8/Firmware/Release/). After flashing the new firmware you will have more freq options.

---

<div class="post-metadata">

**Author:** ![cb9dec](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/c/c2a13f/32.png) [@cb9dec](https://www.thethingsnetwork.org/forum/u/cb9dec)\
**Post date:** [December 16, 2025, 7:51pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/7 "2025-12-16T19:51:50Z")

</div>

I know several/many of these were shipped with the wrong firmware in the last few months - I got 2 of them that had ‘Thai-5.4.1713921192’ installed. I installed to lgw-5.4.1753346938 to get access the EU frequencies.

The firmware upgrade was quite difficult to do I recall but can’t remember why right now.

Contact your supplier?

---

<div class="post-metadata">

**Author:** ![Somsak](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/somsak/32/45700_2.png) [@Somsak](https://www.thethingsnetwork.org/forum/u/Somsak)\
**Post date:** [December 25, 2025, 12:07pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-connects-to-ttn-but-operates-on-as923-instead-of-eu868-moved-to-cups-to-change-frequency-now-cups-not-connecting/72808/8 "2025-12-25T12:07:02Z")

</div>

Firmware upgrade can be done by using Web Admin interface (System/Firmware Upgrade)

 ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/3/1/316f4af94c9096a3dc957445cd35af6112d53d4f.png)
