Where can I find the list of pages/commands available from the gateway web server at http://things-gateway.local ? I know of
http://things-gateway.local/info -> page as post abovehttp://things-gateway.local/ssids.cgi -> list of seen WiFi networksA few I posted earlier, with emphasis on āNot quite usefulā:
Update. Tried to activate the gateway for a wired Ethernet connection. It goes into a reboot loop again, but the led-patterns are different. It displays āconnect to the internetā, and then āactivateā. I can see the device on my home network. Then, the first two leds are on, no flashing. Then it goes into a reboot.
are these problems
related ?
What can I do here, change my WiFi access-point without any authorization?
I got this information reading the documentation published on the by The Things Network on their site, so if itās I correct then they need to update it ? Only trying to use the information at hand to try and identify more info about this reboot issue and possibly root cause.
https://www.thethingsnetwork.org/wiki/Backend/Connect/Gateway
Thank @arjanvanb , I think this should be available on the FAQ page. When digging in an issue it is difficult to predict what will be useful as the bug is usually in a place that we expect to be clean 
All well, but to my information, there are quite a few initial backers stuck with not usable TTN-gateways at this moment. Some information is becoming available in this thread. But it is mainly from backers, and without a clear identification of root cause and solutions yet. So, be prepared to answer questions from your initial backers as to how this problem is going to be taken up by The Things Network. I would like to see the problem being acknowledged by The Things Network, and a clear outline of the process that is going to be followed.
You are not touching your access point here, you are linking the gateway to the selected WiFi network.
I would say we donāt know exactly at present, if the firmware/hardware reboot is caused by a edge case created by an,issue with backend issue or environment (isp) more information is needed.
there are 160 gateways more active then 5 days ago, active, not activated, many of them are new TTN gateways, how many I donāt know.
trying to figure how many are working correctly and why are they working correctly, its not that every delivered gateway gives problems.
I am surprised that enclosure of the gateway that has some relatively high dissipation components (I measured up to 50Ā°C on some surfaces while ambiant temperature is below 25Ā°C) has no opening and no efficient radiation surfaces (no metal plate or other radiators). I donāt think that it is related to our issue but it it is surprising to me.
I drilled holes in my ZIGGO television decoder for that reason 
Havenāt connected to my TTN-gateway via the serial port. On the home network gateway, it looks like the TTN-gateway is connected (wired or wireless). From the outside, and without proof, it could even be basic networking: like a failed DNS lookup, incorrect gateway address, or comparable. Do you think that can be checked?
There is a condition that forces our gateways to reset instead of continuing trying to connect.
Question to TTN: is there a way to know what is the source of the last reset when we restart ? Any log or trace or LED signature ?
yes i get that, the thing is that anyone on the local network can do this change ā¦
Anybody on your local network can do it. So it is as much protected as your WiFi printer or surveillance camera is.
But I agree that a gateway should be individually password protected as it can send data out of your network.
so what happens when I select a SSID and enter a wrong WPA password, will it fallback to the previously working SSID or will I lose access to the gateway - who knows or tried ā¦
Have not tried this. Based on documentation, I would say that the network connection is initialized once. When you want to do this again, you will first have to reset the TTN-gateway. Meaning: after restart you will start from scratch again. So, no fallback to āpreviously correct settingsā.
Do not get us wrong. We do not complain that 90% (or even 99%, I donāt know) of TTN gateways are starting fine, we are just trying not to have 100% of our sole gateway not working. Itās very good that you can grow the network (I say you as if you are part of TTN, which I donāt know), and we would like to be part of it. We just need help, and knowing that the rest of the gateways is fine does not help our gateway to come in the network.