Red light occasionally after mains failure and reboot
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
My setup has one X60 as principal, the second connected to the principal by copper and two other units (one X60 and one M4R) connected to one of the first two using wifi. After a power loss, the system is showing red lights blinking, steady and errors, specially in the unit connected to the principal by copper. The web interface of the principal desappeared and the Android app couldn't find the network. I then installed the latest firmware, reset everything, part of the problem was solved, but the network is still unstable. What to do? Thanks in advance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Ari_Nascimento
I noticed the system displaying various red blinking lights and steady errors on insignia.com.pk, particularly on the unit connected by copper. The web interface for the main unit disappeared, and the Android app was unable to detect the network. I managed to install the latest firmware and reset the devices, which resolved some issues, but the network remains unstable.
- Copy Link
- Report Inappropriate Content
It's a pitty the support from TPLink is not good. To avoid red lights, I had to disconnect the copper cable from the third unit, but the performance decreased, as the distance from the first and second units are too much (the second unit is usually connected to the third if it's connected by copper).
- Copy Link
- Report Inappropriate Content
Hi,
Which unit would be unstable? Is it connected with Ethernet cable or via WIFI? Please check the light status on the unit.
If only certain unit have the unstable issue, you can also refer to this troubleshooting steps first.
The internet connection is unstable or suddenly stops working when connected to the Deco network?
- Copy Link
- Report Inappropriate Content
@Sunshine thanks by your reply.
The network is configured as access point, not router. The ip assigned to each unit by DHCP and mac addresses are: 192.168.0.20 (first/main), 192.168.0.21 (second, connected to the first by copper), 192.168.0.22 (third, connected to the second by wifi), 192.168.0.23 (fourth, connected to the first by wifi).
The problem began with the second unit connected by copper to the first (main) after a power outage, the second unit showed red light blinking and steady red, and eventually turning to green and back to red again. The third unit, connected to the second by wifi, began to show red light too. Noticed the first unit (main) lost the web interface and the Deco app couldn't find the network, but the Internet access was still working in the clients connected by wifi to the first (main). Noticed the Deco app didn't warned about a new firmware available. I should mention there is a fourth unit (M4R) connected by wifi to the first (main).
Did a full reset in all units, updated the firmware and reconfigured all X60 units, with the units close to each other and just the first connected to the Internet. Moved the second and the third to their original places. After sometime, the problem reapeared. Then I swapped the second (the one that was connected by copper to the first/main) with the third (the one that was connected to the second by wifi). The second is now connected to the third by wifi and the third is connected to the first (main) by copper. The second is still showing red light blinking. When the red light is being shown, the first/main looses its web server and can't be found.
Log of the first and second is impossible to get with red light, there is no web access.
Log of the third while connected to the first by copper (it was originally the second before being swapped):
Tue Sep 10 03:51:38 2024 user.err : Error: ssh_connect: Timeout connecting to 192.168.0.20
Tue Sep 10 03:51:38 2024 user.err : Error: connect
Tue Sep 10 03:51:38 2024 daemon.err conn-indicator: 1th attr(data) not found
Tue Sep 10 03:51:38 2024 daemon.err conn-indicator: Invalid response
Tue Sep 10 03:52:18 2024 daemon.err nrd[23088]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 80:9F:9B:31:CE:CE
Tue Sep 10 03:52:27 2024 daemon.err nrd[23088]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 80:9F:9B:31:CE:CE
Tue Sep 10 03:52:36 2024 daemon.err nrd[23088]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 80:9F:9B:31:CE:CE
Log of the fourth (M4R), warning:
Tue Sep 10 04:23:06 2024 daemon.err nrd[7656]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for BC:FF:EB:16:38:5E
Tue Sep 10 04:23:13 2024 daemon.err nrd[7656]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for BC:FF:EB:16:38:5E
- Copy Link
- Report Inappropriate Content
I noticed the whole system doesn't resume even turning off the second unit, which is the one I suspect. It needs a reset and complete reconfiguration in the first/main to have the web access back. Reset > mode to access point > change ssid to original.
- Copy Link
- Report Inappropriate Content
Downgraded to 1.2.5 and it seems to be working fine, but the webserver in the main unit is still not working. The main is not replying to ping, all others are ok. No red lights so far.
- Copy Link
- Report Inappropriate Content
After sometime, the problem got back, main unit working, green light, no web access, app shows second (connected to the third by wifi) and third (connected to main by copper) units offline, both with red lights.
Main unit responding randomly to ping, no web access. App shows second and third offline.
Second responding to ping. Web access ok. Last lines of log:
Wed Sep 11 07:14:57 2024 daemon.err uhttpd[4505]: ath23 No such device
Wed Sep 11 07:14:57 2024 daemon.err uhttpd[4505]:
Wed Sep 11 07:15:00 2024 daemon.err nrd[6046]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 80:9F:9B:31:CE:CE
Wed Sep 11 07:15:00 2024 user.err : Error: ssh_connect: Timeout connecting to 192.168.0.20
Wed Sep 11 07:15:00 2024 user.err : Error: connect
Wed Sep 11 07:15:00 2024 daemon.err conn-indicator: 1th attr(data) not found
Wed Sep 11 07:15:00 2024 daemon.err conn-indicator: Invalid response
Third responding randomly to ping, no web access.
Tried to find older firmwares, but I couldn't.
- Copy Link
- Report Inappropriate Content
@Ari_Nascimento
I noticed the system displaying various red blinking lights and steady errors on insignia.com.pk, particularly on the unit connected by copper. The web interface for the main unit disappeared, and the Android app was unable to detect the network. I managed to install the latest firmware and reset the devices, which resolved some issues, but the network remains unstable.
- Copy Link
- Report Inappropriate Content
It's a pitty the support from TPLink is not good. To avoid red lights, I had to disconnect the copper cable from the third unit, but the performance decreased, as the distance from the first and second units are too much (the second unit is usually connected to the third if it's connected by copper).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 642
Replies: 7
Voters 0
No one has voted for it yet.