Omada Hotspot Portal NOT WORKING with OC200 !
Hello
We are trying to use the Portal Hotspot with User Login managed with an OC200
but when a user connect to the SSID managed by this portal, nothing happend
no webpage at all, no portal at all.
Verry disapointed
|
Model
:
OC200 1.0
|
|
Controller Version
:
3.0.4
|
EAP330 v2 Latest EU firmware
EAP110 v1 Latest EU firmware
Any help or support from TP-Link much apreciate
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I am very sorry for this
Please help to provide the following information to help us locate the problem.
1. the firmware version of EAP330 V2 and EAP110 V1
2. the portal type you used.
3. Do you confirm that both the two EAP models managed by OC200 have the same issue? If possible, please do the follwoing test.
a) disable radio of EAP330 , enable the radio of EAP110, (i.e., force the device connect to EAP110), set the portal on OC200, connect your device to the SSID, check if the issue still exist.
b) enable the radio of EAP330, disable the radio of EAP110, (force the device connect to EAP330), connect your device to the SSID you have created, check if the issue still exist.
- Copy Link
- Report Inappropriate Content
Hello Robert.Jiang,
what's about the Javascript erros being thrown in Chrome browser? I compared this Javascript file with the one from version 3.0.2 and it contains errors in 3.0.4 not present in 3.0.2 (maybe due to changes of variable named 'r' to 'n', but didn't investigate further).
- Copy Link
- Report Inappropriate Content
Hi Chris,
Could you please tell me the specific Hardware version and Firmware version of your EAP330 and EAP225?
So I can help test about the issue you encountered.
- Copy Link
- Report Inappropriate Content
Hi @R1D2,
sorry for the late reply.
which version is your chrome browser?
You mentioned in another post that "It even renders the Omada Controller User Interface totally unuseable on some older browsers which are still in use by our customers and might be used by guests visiting a hotspot. I'll stick with previous version for now."
Which browser do you customers use? and the version is? How to reproduce the bugs?
Controller 3.0.4 has modified some UI design and it may introduce some compatibility problems.
- Copy Link
- Report Inappropriate Content
Robert.Jiang wrote
which version is your chrome browser?
Hi Robert.Jiang,
we test with several versions, most often with latest and oldest browsers present in operating systems over a range of last 5 years. That's currently Safari v5 to v11 and Chrome v32 to v69. The one I used for the test which failed was v38.0.2125.122.
Which browser do you customers use? and the version is? How to reproduce the bugs?
Honestly, I can't tell. We have ~120,000 hotspot users each month in hotels, hospitals, cafes and other public places and several hundred hotspot owners, all using a broad range of Windows, Linux and MacOS systems.
The WWW once had a basic principle to be device-independent and IMO it's a pity that more and more developers make software even depending on OS versions. It's o.k. to use new features of browsers as long as there is still a fall-back if older systems are detected.
In case of Omada Controller v3.0.4 the bug is that the main window just remains blank in older browsers no matter which tab is selected. I have not yet tested wether the portal page and redirection mechanism is affected too, but from Pascal's description it seems so.
Please consider to not make software depending on user's browser versions. If websites do so and risk to lose visitors it's their decision, but if a hotspot system just granting access to the Internet depends on browser versions this is a no-go in my opinion. For hotspot users we can compensate by creating own portal pages, but for paying customers we cannot tell them to upgrade their hard- and software and unfortunately average people not being IT specialists often use old computers running outdated software.
- Copy Link
- Report Inappropriate Content
Here are the firmware version from all the EAP:
EAP330 v2 Latest EU firmware
1.2.0 Build 20170930 Rel. 31933
|
|
EAP110 v1 Latest EU firmware
1.2.0 Build 20180418 Rel. 74942
|
|
We are actualy making the test into an isolate geographic site with only the EAP110-Outdoor, to not disturbe production sites.
this EAP was tried with 4 differents sites configurations A,B,C,D and got the firmware 1.2.0 Build 20180418 Rel. 74942
the production sites list:
Site A is using two EAP225-Wall with firmware 1.0.0 Build 20180418 Rel.57167
Site B is using nine EAP330 with firmware 1.1.2 Build 20170411 Rel.51586
Site C is using four EAP330 with firmware 1.2.0 Build 20170930 Rel.31933
SITE D is using one EAP330 with firmware 1.2.0 Build 20170930 Rel.31933
we tried voucher portal and local user portal
We made test with configuration sites A,B,C, and fall always on same issue, portal page can't be reach.
We tried with 2 smartphones device (iPhone X and Samsung S7) and 1 computer Win7 with chrome 69.0.3497.100 (Build officiel) (64 bits) and Firefox 62.0.3 (64 bits)
On the production sites, there was a lot of try with many differents smartphones, all the same issue, portal page can't be reach.
If we reboot the OC200, the page can be reach 1 time, but error (error please contact your administrator) append once we try to login as user, and then the portal page can't be reach anymore.
- Copy Link
- Report Inappropriate Content
I noticed that the portal is running and always works with the AP EAP225. It still does not work on the EAP330. Can it be that the AP has an error?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Chris wrote
I noticed that the portal is running and always works with the AP EAP225. It still does not work on the EAP330. Can it be that the AP has an error?
Hi Chris
Did you opened a case support with TP-Link engineers ?
From my syde I received a test firmware for the EAP330
but this one don't fix the problem in my case.
Wich type of portal is working with your EAP225 ? (voucher, user,...?)
- Copy Link
- Report Inappropriate Content
Pascal wrote
Chris wrote
I noticed that the portal is running and always works with the AP EAP225. It still does not work on the EAP330. Can it be that the AP has an error?
Hi Chris
Did you opened a case support with TP-Link engineers ?
From my syde I received a test firmware for the EAP330
but this one don't fix the problem in my case.
Wich type of portal is working with your EAP225 ? (voucher, user,...?)
We are actually making test into an isolate geographic site with only ONE EAP110-Outdoor with firmware 1.2.0 Build 20180418 Rel. 74942, to not disturb production sites.
EAP/OMADA 3.0.4 portals issues append with 5 different controller sites configurations A,B,C,D and E dedicated for the test.
THE OC200 got actually 4 remotes sites in production + 1 default factory site + 1 test site
the production sites list:
Site A is using two EAP225-Wall with firmware 1.0.0 Build 20180418 Rel.57167
Site B is using nine EAP330 with firmware 1.1.2 Build 20170411 Rel.51586
Site C is using four EAP330 with firmware 1.2.0 Build 20170930 Rel.31933
SITE D is using one EAP330 with BETA firmware 1.4.0 Build 20180925 Rel.37155
The test site:
Site E is using ONE EAP110-Outdoor with firmware 1.2.0 Build 20180418 Rel. 74942
we tried voucher portal and local user portal
We made test with configuration sites A,B,C, and fall always on same issue, portal page can't be reach.
We tried with 2 smartphones device (iPhone X and Samsung S7) and 1 computer Win7 with chrome 69.0.3497.100 (Build officiel) (64 bits) and Firefox 62.0.3 (64 bits)
On the production sites, there was a lot of try with many differents smartphones, all the same issue, portal page can't be reach.
If we reboot the OC200, the page can be reach 1 time, but error (error please contact your administrator) append once we try to login as user, and then the portal page can't be reach anymore.
To be sure there is no other influence from others EAP model firmware, we created 1 dedicated SITE for testing purpose (site E)
In this SITE there is ONLY ONE EAP110-Outdoor with firmware 1.2.0 Build 20180418 Rel. 74942. and use an SSID name that is not present in others sites configuration
The OC200 is physically connected in the same subnet and wire network of the EAP110.
The test made, showed again ERROR , page can’t be load.
After upgrading the EAP330 from the production site D with a BETA version firmware provide by TP-Link support, we are still facing the same issue with this beta firmware.
We will now send to TP-LINK the configuration file from our OC200 and an remote agrement meeting is being performe to look inside the logs systems.
Keep In Touch
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 18181
Replies: 26
Voters 0
No one has voted for it yet.