Hi  @Wayne-TP 

All devices are on the whitelist (with device MACs). And all the Android devices (Samsung Galaxy Tab A, Pixel 2, Pixel 4A) and the Chromebook (Acer R13) have the same issue. The Pixel 4A is Android 12, and the Pixel 2 is either Android 10 or 11 (I don't have access to the device at the moment), and the Galaxy Tab A is Android 11/One UI version 3.1.

This is what happens: After I turn on access control (the whitelist is already loaded with all the devices I had put in) the devices have access. After a device leaves the network and comes back (you can also simulate this by rebooting the device) it cannot connect. If I disable access control, the device has access again.

The error I get trying to access the non-hidden network through a browser at tplinkwifi.net is "This site can't be reached... ERR_CONNECTION_TIMED_OUT" after a long "hang".

@Wayne-TP 

Further information: I tried with a MacBook Pro and had the same problem. Also, when I added the MacBook to the whitelist through the "add from list" option it got "operation failed" (in the web admin page), even though the device did end up appearing on the whitelist. (This has happened with other devices now that I recall, but I don't remember which.)

  @Wayne-TP 

After multiple email exchanges with TP-Link support the response was that TP-Link does not support using a hidden SSID with access control with Android, Chromebook, and MacBook devices. (I don't know about iPhones since I never tried and didn't ask.). This seems a little odd because that combination worked on all my prior (non-TP-Link) routers. At a minimum it seems this should be noted in the user guide.

  @Rick_ 

Hi Rick,

Thank you for the post. I have the same problem with TP_LINK AX5400. I bought it a few days ago and kept wondering why it doesn't work.

My SSID is hidden and I'm trying to use the "Whitelist". When my device is off WIFI and then comes back. Device cannon connect until I disable "Access Control". I didn't have such a problem with my old D-LINK router. It is a pity that there is no such information in the documentation.