I tried a voucher. However other types do not work either.

For testing purposes I have bought a new EAP225. The portal works without problems like on the EAP225-Outdoor (EU). Even after a few minutes or hours, no problem. On the new EAP225 (EU) I use the latest firmware (2.3.0 Build 20180628 Rel. 54512) with the old did not work either.

Apparently the Hotspot portal url adress use a port blocked by our internet Provider : 80

In fact we did'nt know that Omada 3.0.4 with OC200 is not using the same port of the older Omada Linux we was using previously : 8088

We are now front of a security and rules of internet usage  issues, as we didn't found yet a way to change the defaults ports used by OC200.

We don't undersatnd the way TP-Link had thinked about a real CLOUD solution linked with the OC200 but don't give a way to the users to past

thru these CLOUD solution to reach the Hotspot Portal.

And we are really surprised that OC200 don't use an https secure conexion with the hotspot portal access.

We are now waiting some answers from TP-Link ingeneers, and hope we will receive a solution to change/manage the security ports used by OC200

We are still not able to reach the portal page with EAP330.

It work with EAP110, EAP225_Wall

I cant get the portal to work with the EAP330 either. We just got a second one and i thought setting up the Omada Controller might be a good idea now. We do use the voucher methode and have a password on the network. The password will be accepted, but the portal wont come up Browsing to a page doesn't help either.

In this thread here, people referre to version 3.0.4 - new newest i can find is 3.0.2. Has TP-Link pulled back the newer version?

Edit: I might add that we run the Controller on Digital Ocean from the .deb version and i changed to ports to 80 and 443 (using authbind).

Edit: I got i running. Two things did the trick for me. Upgrading the AP to 1.4 (released yesterday) and changing the VLAN to 0.

Yea :-)

it works also with EAP330 under FW 1.4.0