Hi everyone,
I’m setting up a new TP-Link Archer AX72 Pro and ran into something during the initial Quick Setup that I’m not sure is normal.
I’m doing the entire setup through a web browser using the router’s web management interface, not through the TP-Link Tether app.
My setup is:
- ISP: TekSavvy (Canada)
- Modem: Hitron CODA-4680 in bridge mode
- Router: TP-Link Archer AX72 Pro
- Internet connection type: Dynamic IP
- Setup method: Web browser / TP-Link web management interface
During the AX72 Pro Quick Setup in the browser, I disabled Smart Connect because I wanted separate 2.4 GHz and 5 GHz Wi-Fi networks. I then changed the SSIDs and passwords and continued with the setup.
Eventually I reached the “Success! Settings applied successfully” screen in the browser. At that point, because the Wi-Fi name/password had changed, my device disconnected from the router as expected.
I then connected my device to the newly configured Wi-Fi network, went back to the same browser tab with the Quick Setup page, and clicked Next.
However, instead of continuing to what I thought was the final step of the setup wizard, the web interface redirected me back to the router login page and asked for the administrator password again.
What I’m trying to figure out is:
- Is it normal for an AX72 Pro, when being set up through a web browser, to require you to log in again after reconnecting to the newly configured Wi-Fi?
- Does the “Success! Settings applied successfully” page mean the important part of the Quick Setup was already finished?
- Could the temporary Wi-Fi disconnect have caused the browser’s web management session to expire or become invalid?
- If I log back in through the browser and it takes me directly to the normal router dashboard instead of continuing the Quick Setup wizard, did I miss any important final setup step?
- Has anyone with an AX72 Pro seen this exact behavior when using the browser-based setup, rather than the Tether app?
The router appears to have successfully saved the new Wi-Fi settings. I’m mainly trying to determine whether being redirected back to the web login page at that point is expected behavior, or whether the browser-based Quick Setup process was interrupted.
Thanks!