I am also getting this problem after changing the hard timeout value from empty to some number. I am using 2.2.3. A temporary fix is to remove the hard timeout value.

Will do that, thank you!

You used to have to upload a null file to clear it. cp /dev/null portal_reset.html Then upload that.

One solution that make you issue work: Back-port the actual code too your pfSense installation. From what I recall, the removal of firewall rules was buggy back then (2.1.5) so they repaired it - which introduces new versions. You you don't want do 'deal' with it (because you can't), but you have the need to have your pfSense modified without being upgraded: switch to this sub-forum https://forum.pfsense.org/index.php?board=34.0 (be SURE that you read the rules FIRST). Be ready to find out that the 'repair' will break squid …...

Hi All, Thanks for your reply,yeah i guess i need to disable the captive portal,,thanks it helps me alot Thanks

Sounds like you have a WiFi AP in routing mode connected to CP. That will not ever work properly.

I'm working on this here: https://forum.pfsense.org/index.php?topic=95680

I'm working on this here: https://forum.pfsense.org/index.php?topic=95680

I'm working on this here: https://forum.pfsense.org/index.php?topic=95680

I'm working on this here: https://forum.pfsense.org/index.php?topic=95680

Perfect!  I already use freeradius, so this shouldn't be too difficult.  Many thanks!

Please, people, don't 'try' pfSense using very old version. It will be confusing for you and difficult to get support.

Thank you cmb, I installed the syslog-ng package to retain and rotate this logs.

I believe this happens on upgrade if the CP .db files  in /var/db didn't get reset. On 2.1.x they were in SQLite 2.x format and on pfSense 2.2+ it's SQLite 3.

^^^ [image: use-the-source-luke.png]

Great ! You just posted in the ENGLISH section. That won't work. Scotty !!! Beam me up, please.

No. Start coding… :P