Captive Portal issues upgrading Balance 310 to 6.2.1


#1

When I upgrade our Balance 310 to 6.2.1 the captive portal breaks. The captive portal works in 6.2.0.

I am using an external splash page which redirects back to https://captive-portal.peplink.com/portal.cgi where I get the error: This webpage is not available ERR_CONNECTION_REFUSED. This is error exists on both the device that is trying to connect to the captive portal as well as any machine already connected to the network.

When I use the Built-in splash page the captive portal works as expected.


#2

Hi Chris,

Please open ticket for us to investigate.

Please help to turn on Remote Assistance as well.

Thank you.


#3

Hi, it happens to me too, but I resolved it by adding ‘captive-portal.peplink.com’ to walled garden, now my problem is, when user log in by external webpage, https shows error, “NET::ERR_CERT_DATE_INVALID”, I know is a problem with the https://captive-portal.peplink.com but i dont Know how to solve it.



#4

This is the expected behavior. We provided explanation here. You may sign your own certificate and import into the Balance router. Below is the screenshot where you import the certificate.