@CallFromUSA:

….
Is there a place where connected users are shown?

For the last 8 years, it was here : (see image).

You need to have "Authentication method" set to "Local User Manager / Vouchers"
You need to declare a user "my_cp_user" with password  (System => User manager) and
Make this user member of the group "captive portal visitors". This group should be assigned to this "right" : "User - Services: Captive Portal login Indicates whether the user is able to login on the captive portal."

Status-Captive-Portal.png
Status-Captive-Portal.png_thumb

@Claylol:

I think, probably its a conflict of my school dns or dhcp ?? not sure, i think the configuration is ok.

Don't think.
Be sure ;)
Check it.

When a client connects to the "pfSense Captive Portal network" it should obtain an IP from pFsense (and from no one else).
You can check so with your device (the IP, gateway and preferred DNS)
You can see the lease showing up in pfSense.
You can see the DHCP server log in pfSense showing the device asking for an IP.

@Claylol:

Now im trying to put 1 Access Point and try it with my Phone.

Be aware that your AP should be AP - remove any DHCP server activities - shut down any router mode functions.
It should be a "transparent radio to wire" device.

@Gertjan:

So people do not mess around with "my_cp_user" and "my_cp_user_password", think about this html magic :

wow thanks even better.

@limona21:

I see there was an updated 2 days ago. That fixed the issue. Very nice :)

yea i also got the 2.3.1 update but today .

try this :

https://sourceforge.net/projects/captiveportalplus/

but i did not test it.

Update,

no more crashes since change to permanent -rw last week. Occured at almost each saving process before the change. So I think it is solved.
Thanks a lot for your help!

If problem reoccures, I'll give an update. But don't think so ;)

You should have a discussion with your AP  :D
It behaving like a router now. It shouldn't.
What also often happens if the AP has a "WAN" network plug : it's been hooked up to pfSense with this port. That's very wrong. Use a normal 'switched' port (there are normally a couple of them on the AP).
You should also switch off DHCP server in the AP.
It should behave like a transparent device for communication.

@mfaridi:

@Gertjan:

@mfaridi:

…..if they use DHCP , they can not access to Temp server and webserver , because IP of temp server and print server and web server is static .

Since when system with a static IP can't be reached by a system which obtained an IP by DHCP ??
You really should detail about your network setup.

I re-read you message several times. I can't understand your problem, and probably I'm not the only one.

Thanks,
My problem is this
in our network each computer has IP like this 192.168.0.1.25 and each computer do not use DHCP for get IP , network administrator set IP for each computer , and they do not want use DHCP , because we have web server , temp server and print server and vmwate server .and IPs of these server can not change.
So I have PFsense with Load balance and Failover and multiwan and squid .
squid has transparent mode.
So I want run Captive portal . Captive portal need DHCP .
what I must do when Captive portal need DHCP for work and computers in our network has IP like this
Computer 1 : 192.168.0.25
Computer 2: 192.168.0.26
.
.
.
computer 100: 192.168.0.125

Incredible.
All this proofs to you that you NEED to use DHCP IP assignment for all your client devices - and you shouldn't use static IP assignment (except maybe servers).
When a device obtains an IP, it also obtains (among other) an IP for a DNS server, which should be pfSense.
Use the DNS server on pfSense ( ServicesDNS => ResolverGeneral => Settings ) to make host overrides, so you can assigns names to servers with static IP's.
Now, your clients could use these names. Always.

Btw : my intranet (LAN) servers also use DHCP (not static), but I instructed my DHCP server (also pfSense) that it should always give the same IP to these servers.

Do not take me wrong, but I think you miss some (basic) network management knowledge ;)

Thank you, that worked like a shamp ;)

Hi!!!

Well, ditch old vouchers… yes I can do that... actually I did... I created new rolls... the system keeps reporting the same crash every now and then (but I haven't had the problem in which clients get disconnected )

But deactivate the vouches, and remove all that's within .... uhmmmm I don't like the idea... I have 200+ voucher logged in...

Now do the same against it on 2.2.x and compare :-)

No known issues. Does the service actually show as stopped? Do clients that were already logged in continue to work? System and captive portal logs would be helpful.

@PSBITGuy:

pfSense 2.3
Trouble getting this to work.
I'm an not using any authentication.
Is this supported? All I want to do is have user click "I agree" Button and be redirected to a google.com or wherever with web access.
Once the button is submitted, it doesn't do anything…
Anyone else doing this? Sample code?

I guess it's easy to do so.

Create a Local user and password on pfSense.
Create a hand made captive portal html file (using the example as a start).
But :
Hard code the user name and password into this html file. Using the html magic to make these two items 'hidden'.
Code a simple OK button.
Done ;)

Something is still broken in your setup.
After a 'dummy' http request like http://www.google.fr, the navigator will be directed to '162.168.0.251:8002', nothing less, nothing more.
The captive portal will show up.

Adding something like "?zone=mdl" isn't needed.

Check this with your PC's:
DHCP activated on PC ?
Did it get an IP ? Gateway IP ? DNS IP (should be as the gateway IP = pfSense) ?

Of course, an initial https:// request won't work, this is normal.

Use the default captive portal 'html login page' to start with.

Already being on 2.3, it's low-risk to upgrade to 2.3.1 development versions if you want the fix now. Instructions in this post.
https://forum.pfsense.org/index.php?topic=110157.0