@Solla-topee 

Thank you very much for your fast reply.

My Network map is very simple. I have a L3 Switch, which does every routing in my network and there is currently no acl which restrict the access to the management vlan.

The management vlan is untagged on the connected switch port where the access-point is plugged in.

I can also ping the devices, only the webinterface do a redirect to this URL:" http://[IP]/login/domain-redirect/https_blocking.htm " and then nothing. When i want to open "http://[IP]/login/login.css" from another vlan this works also, i can see the css source code. But i can´t access the webinterface, only the redirect which i described before occurs.

The Accesspoints operate in Multi-SSID Mode.

When i opened this topic i can´t select the right model, but that´s the model what i use and that have the problem: https://www.tp-link.com/de/home-networking/access-point/tl-wa901n/v6/

The old "https://www.tp-link.com/de/home-networking/access-point/tl-wa901nd/" model that i also use, does not have this problem.

@Solla-topee I too am getting exactly the same issue.  

I too am using vlans.  I am trying to access the admin interface from a different vlan.  I can tracert to the AP, I can ping the AP.  But if I try and browse to the AP I get the ERR_EMPTY_RESPONSE on https_blocking.htm as the OP.

Like th OP, I can access the AP interface locally within the same network.

Can you please advise of a resolution to this issue?

@BSP-Tech did you manage to find a work around to his issue as I notice there is no response from TPLINK?

Thanks

Lake

@Solla-topee 

@lakesol 

Unfortunately I have not found a way to fix the error myself, but I don't think it's great that TP-Link does not fix the error in the firmware.

@BSP-Tech 

Thanks for the update.  Sorry to hear you are still having the same issue.

Agreed, thus should be fixed.  Its not like we cannot reproduce this issue quite reliably and they have known about it now for quite some time.

Would someone from tp-link care to comment?

Thanks

@BSP-Tech 

FYI I have just got of a long conversation with support.  There is beta firmware to fix this issue.  I have just been sent it but also been assured that it will be made available soon.  I will update here on my findings.

Lake

@Solla-topee 

For me, it seems to be working for now. Access to the Webinterface is now working very well.

I too seem to be working now with the beta firmware.  Many thanks.