Can't connect Laird RG186 gateway to TTN

Hi guys,

I have bought a new Laird RG186 gateway and I can’t get it to connect to TTN.
Following the guide at Application Note - Setting up Basic station on the Things Stack v3 I did the following steps:

  1. Connected the gateway via ethernet, changed my credentials and updated the firmware to the latest version (Laird Linux gatwick-laird-93.9.6.30).
  2. Logged in to the TTN console > go to gateways > Register gateway
  3. Entered the gateway EUI (C0EE40FFFF2A378C), gateway ID, name, frequency plan (Europe 863-870 MHz (SF9))
  4. Not in the manual, but I guess this is necessary: enabled ‘Require authenticated connection’ and enabled ‘generate API key for’ CUPS and LNS.
  5. Registered the gateway.
  6. Logged in to the gateway again, LoRa > Forwarder, set the mode to ‘Semtech Basics Station’.
  7. Set the LNS address to wss://eu1.cloud.thethings.network:8887
  8. Uploaded the ISRG Root X1 server certificate file I downloaded from https://letsencrypt.org/certs/isrgrootx1.pem
  9. Uploaded the tc.key file that was generated earlier.
  10. Pressed the ‘Update’ button.
  11. Connection state remains ‘false’ and nothing new in the TTN console, so I rebooted the gateway.
  12. Still nothing, so I checked the gateway logs:
RG1xx2A378C	root	user.notice	Jan 16 20:04:19	restarting the lora packet forwarder
RG1xx2A378C	root	user.notice	Jan 16 20:04:15	resetting the lora concentrator
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/tc-boot.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/tc-bak.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/tc.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/cups-boot.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/cups-bak.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/cups.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	No server URIs configured - expecting at least one of the following files to exist:
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/tc-bak.uri: Misconfigured URI - expecting scheme ws: wss://eu1.cloud.thethings.network:8887/
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	/opt/lora/basicstation/tc.uri: Misconfigured URI - expecting scheme ws: wss://eu1.cloud.thethings.network:8887/
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	2023-01-16 20:04:15.588 [AIO:ERRO] Malformed URI - expecting ws(s)://host:port (no path, port mandatory) but found: wss://eu1.cloud.thethings.network:8887/
RG1xx2A378C	lora	user.notice	Jan 16 20:04:15	2023-01-16 20:04:15.587 [AIO:ERRO] Malformed URI - expecting ws(s)://host:port (no path, port mandatory) but found: wss://eu1.cloud.thethings.network:8887/
RG1xx2A378C	root	user.notice	Jan 16 20:04:15	restarting the lora packet forwarder
RG1xx2A378C	root	user.notice	Jan 16 20:04:11	resetting the lora concentrator
RG1xx2A378C	lora	user.notice	Jan 16 20:04:11	/opt/lora/basicstation/tc-boot.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:11	/opt/lora/basicstation/tc-bak.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:11	/opt/lora/basicstation/tc.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:11	/opt/lora/basicstation/cups-boot.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:11	/opt/lora/basicstation/cups-bak.uri
RG1xx2A378C	lora	user.notice	Jan 16 20:04:11	/opt/lora/basicstation/cups.uri

I also tried LNS address wss://eu1.cloud.thethings.network:8887/ (with the trailing slash), but still nothing.

Could anyone please help me? Thanks in advance for your help.

Paul

The error message in the log says there shouldn’t be a trailing slash …

True, but this message also appears in the logs if I try it without the trailing slash:

I have tried using CUPS instead of LNS, but this also didn’t work.
Then I tried the solution posted here: Can’t get Laird RG1xx Basics Station Forwarder working with TTN - Gateways - The Things Network
Also, no dice. What’s even more strange is that whatever server addresses I use, I always get this error:
2023-01-17 10:49:40.972 [AIO:ERRO] Malformed URI - expecting ws(s)://host:port (no path, port mandatory) but found: wss://eu1.cloud.thethings.network:8887/
I guess I will have to ask Laird for support.

I managed to solve the problem with the help of Laird. For others who might encounter the same issue: there’s a bug in the latest firmware release that might cause corrupt configuration files, preventing the gateway from connecting to a CUPS or LNS server (bug ID 21421). The solution is to factory reset the gateway (power off the gateway, hold the user button and keep holding it while you turn on the gateway, release the button when all LEDs start flashing) and configure it again.

4 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.