Cannot login with PC to configure AX-55 since Firmware Version: 1.3.1 Build 20240129 rel.57815(4341)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Since Firmware Version: 1.3.1 Build 20240129 rel.57815(4341) when I try to login to the router it accepts my TP Link password (Operation successful) then immediately returns me to the login screen. Local password also does the same thing but no "operation successful" message.
The only thing that works is connecting directly the router with my PC with an ethernet cable and bypassing the internet connection.
Also the Tether app is showing my AP mode AX-55 as having no active client connections to it. None of the stats are present on the screen, but the router works just fine. Everything is working just as if the router was in perfect order.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@JP57 The tether app is kinda limited but it does work for the settings that are in there. You can switch the operation mode and then configure the Router settings to DHCP correctly.
- Copy Link
- Report Inappropriate Content
Hi, since we have not reproduced the issue on our end, may I have the configuration .bin file of your AX55 AP mode?
You could upload it to a drive and share with us the download link via private message along with the admin local password, we will test again with the same configuration file.
And before the firmware update, was your previous firmware 1.2.3 or 1.2.6?
- Copy Link
- Report Inappropriate Content
@Sunshine I would absolutely LOVE to give you the file. But i would have to factory reset my router and go through this whole ordeal again. And my router is not accessible at the moment.
If you want to reproduce this problem, here's a quick way.
- Install two AX55s, one in router mode and one in AP mode. Use addresses 192.168.1.1 for the router and 192.168.1.254 for the AP (this is NOT the default addresses, this is what i use, just to be sure).
- Flash both routers on the old version of firmware.
- Upgrade the **AP router** to the latest, bugged version, then switch it to AP mode (dont forget to give it the correct IP first because you wont be able to change it).
- Once the router is rebooted, try to sign in to that AP router using a **PC** connected to the ***main router***. Note that ALL browsers cause issues. I tried. No, I dont have any extensions installed on the test so it's not the browsers. It really is the router refusing connection.
Here's a video showing the result. Notice the absence of "Operation Failed", "Operation Succeeded" or "Bad password". There is simply no message, it looks like the browser is logging you in but then you're immediately kicked out.
https://file.io/9HuwEmKYjfEa
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Yes, this is acceptable. I am a retired IT engineer and available most of the time to help your senior remotely.
P.S. I am in "Eastern Time" time zone (Montreal time)
Regards, J.P.
Please notice: I can reproduce the symptom every time the AX55(CA) reboots after I switch mode (System=>Operating mode) from "Router mode" to "AP mode". The problem also appears on various other occasion after the router rebooted.
Important for the senior support: This is an AX55(CA) V1 and not a AX55(US). For some reason, Canadian version is different and use a different version of firmware. The latest version was updated last Thursday and automatically went from "1.2.3 Build 20230603" to "1.3.1 Build 20240129 rel.57815(4341)"
P.S. You can also simulate the issue by:
1 - Configuring the AX55(CA) through the web page (on a PC). Once configured
2 - Access the AX55(CA) through the an iphone/ipad tether application and swith to AP Mode
3 - Once rebooted, connect to the AX55(CA) with the tether application again
4 - Access the AX55(CA) through the web page (on a PC), enter the password and ask if you want to disconnect the remote tether say YES. You will get the "Operation failure"
- Copy Link
- Report Inappropriate Content
Hi, thanks a lot for the cooperation. We have reported the issue to the support engineers, they will likely reach out to you via email to continue to troubleshoot your issue. Please check your email box and confirm.
- Copy Link
- Report Inappropriate Content
I have received a "BETA" firmware version from "TP-Link Support 2nd Level". I have been testing it since this morning and it seemed to have "corrected" the "locked-out" issue. I will continue experimenting and will report to both the "TP-Link Support 2nd Level" and Community if the problem is completely gone / still there.
J.P.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@JP57 Thank you very much for the update, glad to hear that it works better now.
@Avenger We are not very sure whether the root cause in your case is the same as @JP57 or not, because you didn't see Operation Failed message like him. Would you like to try the beta and debug with our senior engineer as well? If so, I will also escalate your case to our senior engineer via email.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 4398
Replies: 44
Voters 1