@Kevin_Z 

Thanks for your reply.
By default I have only 5ghz activated.

While wifi does not work, the router in ap mode still provides internet through the ethernet ports without problem.

To answer you, I have activated 2.4 too and surprise! both work without problem being both activated.
The error then occurs with only 5ghz activated.

Do I ever remember that I also solved it with some other change in the 5ghz wifi configuration (ex: channel)

I have only noticed the problem since I have it in AP mode. (capable before it happened, but it was difficult to realize that internet was working and not wifi)

Thanks.

@Kevin_Z 

It happened again, but only with a very particular configuration, which coincidentally is the one I was using.

 

Factory reset -> AP mode -> WIFI 2.4 off and 5ghz on with default values. IT WORKS WELL!.

 

Then I modify SSID and password to the one of frequent use (with a special character).  It works well!

Finally I modify some 5ghz wifi configuration:
-Security Version (WPA2-PSK)
-Encryption AES
And the error occurred again (after turning off the router, when restarting, the wifi does not connect)

Thanks for your time. I hope with the data I can check to see if it is a replicable case in another router.

 

Regards

Marcelo.

@Kevin_Z 

Upgrade.
Changing back
-Security Version: auto
-Encryption auto
It did NOT work.

 

LATER:
I switched to router mode connected to the modem directly and it works fine with WPA2-PSK - AES.

Connected in AP mode, the main router is a Ubiquiti ER-X, and it is connected to the fiber optic modem, with dhcp server activated (deactivated in the Archer C9).

 

BUT when switching it back to AP mode, with WPA2-PSK AES it worked in the first 3 attempts. Could it be that it depends on the randomly assigned channel? (it's the only parameter that I realize is changing)

 

In the log the error I am getting is "LED controller", various warnings and error 934 "Config importing failes" which I don't think has binding but I mention it.

After these tests I was more confused since he did not repeat.

 

 

It kept happening. Anyway, I feel that I am wasting my time doing so many tests if from you (tplink) they do not look for how to solve it, since it is a software failure.

Model: Archer AX50

Hardware Version: V1

Firmware Version: 1.0.9 Build 20200708 rel.55037(5553)

 

Wow !!!! exact the same problem as mine. i thought is hardware problem and gonna sold it and wait..firmware problem causing this unpleasant experience.

 

Please send the solution to me as well other than downgrading the firmware. Thanks.

 

I have exactly the same issue, with Archer AX50 in AP mode with latest firmware as above.

 

Is there any other solution except firmware downgrade?