I use de only last 3 byte pairs of the ethernet mac and still not giving me access.
Can you try over WiFi as above?
Do you have admin access to network to check if it is perhaps picking up a DHCP assigned IP address?
Also try power off and retry factory reset as may have fallen into intermediate state?!
NOTE: DO NOT JUST DELETE FROM TTN CONSOLE AT ANY POINT AS YOU MAY NOT BE ABLE TO RE-REGISTER GW ID 
1 Like
Solved, thank you every much
What was issue/solution for others reading later?
1 Like
Conection with wifi
Hi Guys, hope everything is ok and well.
I have been trying to get this unit online on the TTN console for almost 3 days without any luck.
I am using version Laird Linux gatwick-laird-93.9.6.30.
I tried using the preset and on the unit dashboard it showed connected but on the TTN console did not change even after several power cycles.
I tried to configure as a basic station but that didn’t do the trick.
I thought it could have been a old firmware but I updated the to last one and I am still without luck.
Can someone point me in the right direction?
How configured, which region/cluster? Which Server settings? What is GW ID? GW EUI? Freq plan?, Console settings… details details - we need info as crystal balls typically a bit misty this time of year 
! Is there an active device nearby sending data? What does TTN GW Console show?
Which one? Be sure targeting V3 not old revs using V2 etc.
Guys thanks for the replies, I was able to connected it! So it is showing online now! I just need it to replace the preset server with the current one! That did the trick!
Hi All,
I’ve run out of ideas on this one after RTFM’ing my little heart out and following all of the guides. I’m failing to connect to TTN due to a certificate validity error (see below). I’ve logged a ticket with Sentrius as well, just thought I would ask here incase anyone knows a fix… firmware version gatwick-laird-93.9.6.44
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | 2023-03-09 23:18:57.633 [TCE:INFO] INFOS reconnect backoff 80s (retry 1) |
|---|---|---|---|---|
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | 2023-03-09 23:18:57.627 [AIO:DEBU] [6] WS connection shutdown… |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | 2023-03-09 23:18:57.627 [AIO:INFO] TLS server certificate verification failed: The certificate validity starts in the future |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | 2023-03-09 23:18:57.507 [AIO:XDEB] [6] ws_connecting state=1 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | 2023-03-09 23:18:57.506 [AIO:XDEB] [6] ws_connecting state=1 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | 2023-03-09 23:18:57.472 [AIO:XDEB] [6] ws_connecting state=1 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | key usage : K |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | basic constraints : CA=true |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | RSA key size : 4096 bits |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | signed using : RSA with SHA-256 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | expires on : 2035-06-04 11:04:38 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | issued on : 2015-06-04 11:04:38 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | subject name : C=US, O=Internet Security Research Group, CN=ISRG Root X1 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | issuer name : C=US, O=Internet Security Research Group, CN=ISRG Root X1 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | serial number : xxx |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | cert. version : 3 |
| RG1xx29DDFF | lora | user.notice | Mar 9 23:18:57 | 2023-03-09 23:18:57.433 [AIO:INFO] /opt/lora/basicstation/tc.trust: |
Thanks…
Solved it. For anyone who gets stuck with the same, I updated the firmware out of the box using this link -
https://connectivity-firmware.s3.amazonaws.com/rg1xx-lora-gateway/firmware/newest/fw.txt
Laird Linux gatwick-laird-93.9.6.44
to try and solve the problem I found a link to an old firmware -
https://connectivity-firmware.s3.amazonaws.com/rg1xx-lora-gateway/firmware/latest/fw.txt
Laird Linux gatwick-laird-93.7.2.10 (March 2018)
…that didn’t work, but then I rolled forward again to the latest and the error went away.
Cheers
1 Like
I’d like to ask I got my Gateway and i’m having problems connecting to the web interface via ethernet. Connecting through the wifi is working, however I cannot get the Gateway to connect to The Things Stack even though I’m following the steps given in their guide. I’ve tried updating the firmware, but that failed too.
I’ve tried connecting both my PC and Gateway to the router to try and access the interface through https://rg1xxMACID.local (where MACID is the last 6 characters of the gateway’s macid) but it won’t work no matter what I did.
If on same router just go direct to the GW’s IP address in your browser - I find that reliable.
Also I need to check but may be http vs https - long time since I tried that!
A .local address is reliant on random versions of mDNS / Bonjour - if you can tell us what OS & browser you are using on the PC I can comment appropriately.
If you don’t, I’ll comment in-appropriately.
PC is running on Windows 10 and the browser i’m using is Chrome
i’ve tried using the IP Address listed in the DHCP didn’t work either. When I ping it it says host is unreachable.
but i might try this tomorrow
Both wireline (recommended until you are fully up and running) or are you on wifi to/via router>
That should work, but it’s dependent on how often the device broadcasts mDNS packets so it can take a few attempts for the dots to be joined up. But at the end of the day the IP address is, if configured correctly, a dead cert.
When accessing the web interface, I have to use the AP Config Mode of the router to change some settings.