Captive portal not redirecting after succesful login

uaxero

hi everyone.

i have update to 2.3 ( a fantastic job) but in my case when i login in captive portal, the browser no redirect to web page ,i need update (F5) the web browser and then i have access to web page.

i have tryed with iexplore, firefox, opera, chrome and with alls the web browser the results is the same

thanks

carzin

I have the same problem. I was going to come here and state it. In our instance, certain devices, not all, fail to redirect after logging in. It normally happens on iOS devices. They successfully authenticate, then the browser spins and they are never redirected.

redeyes

Check whether if you've PORTAL_ZONE in your Captive Portal login form. Are you using custom Captive Portal login page or the default ?

flightsimmer668

I updated one of my pfsense boxes to 2.3 yesterday. I had CP + transparent Squid on one of my vlans. CP would communicate to another openldap/freeradius box. I had the captive portal patch installed in pfSense 2.2.6 This entire setup was working just fine along with a custom captive portal login page.

After I did the update, I got the same problem as you. It would appear to accept my credentials, then just reload the captive portal page again. Looking at the RADIUS server in debug mode, I can tell that it is not even getting contacted by CP.

uaxero

hi redeyes, thanks for you reply.

i have PORTAL_ZONE in my config and the cp is a custom splash page.

thanks

uaxero

hi.

somebody know if this issue is reported as a bug?

thanks

Gertjan

@uaxero:

somebody know if this issue is reported as a bug?

Check it out https://redmine.pfsense.org/projects/pfsense

Did you saw Captive Portal RADIUS authentication doesn't work after upgrade to 2.3 ?

When 'debugging', get rid of more complicated setups:
Get rid of packages
Stop using external authentication
Use default login page.

Then test portal.
Add one piece back at the time.
Test again.
When thing start to "not work" you know where to search …

uaxero

hi.

somebody has some news of this issue. after of updte to 2.3.1_1 the issue it stays the same

thanks

uaxero

it seems that the version 2.3.1_5 the issue is solved

thanks.

Gertjan

Correct.
https://redmine.pfsense.org/issues/6421
Latest versions always kill latest bugs (and add even newer ones ;))

uaxero

:D :D :D :D

great job as always by the pfsense´s team