Business Community > Controllers > Captive portal redirects to http://192.168.0.65:8088/login and gives error
< Controllers

Captive portal redirects to http://192.168.0.65:8088/login and gives error

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Captive portal redirects to http://192.168.0.65:8088/login and gives error

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Captive portal redirects to http://192.168.0.65:8088/login and gives error
Captive portal redirects to http://192.168.0.65:8088/login and gives error
2021-10-01 08:44:01 - last edited 2021-11-28 08:55:23
Model: OC200  
Hardware Version: V1
Firmware Version: 4.4.4 / 1.9.1 Build 20210721 Rel.39263

Hi,

 

When I try to setup a captive portal via the OC200 everything looks ok, and when I try to connect to the guest wifi I get a popup but it is complete blank and timeouts with an error. I investigate to which url to portal page is linked and it is linked to https://192.168.0.65:8088/login and shows only a blank screen.

The IP of the controller is reachable for the guest network.

 

Tried to reach the URL via the browser and got the same issue.

 

What is this and how can I fix this?

 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Captive portal redirects to http://192.168.0.65:8088/login and gives error-Solution
2021-11-19 15:46:03 - last edited 2021-11-28 08:55:23
Yes this problem is solved. It was an issue with the network ACL and blocking the IP of the OC controller.
Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:Captive portal redirects to http://192.168.0.65:8088/login and gives error
2021-11-18 03:35:25

@DennisDJP 

Do your solve this issue yet?

Try to clear your cookies and caches. Change browser

  0  
  0  
#2
Options
Re:Captive portal redirects to http://192.168.0.65:8088/login and gives error-Solution
2021-11-19 15:46:03 - last edited 2021-11-28 08:55:23
Yes this problem is solved. It was an issue with the network ACL and blocking the IP of the OC controller.
Recommended Solution
  0  
  0  
#3
Options

Information

Helpful: 0

Views: 1067

Replies: 2

About Us
Press
Copyright © TP-Link Corporation Limited. All rights reserved.