Problems with captiveportal after upgrading to 2.2

fakkundo

Hello guys, new in the forum. Got exactly the same error after upgrading my box from v2.1.5 to v2.2.2. Captive portal isn't working, and many of the registered MAC pass thru users have reported access issues.

Has anyone been able to make it work?

Gertjan

Hi,

People that are asking question nearly never post back to say : "it works now, I did this … and this .... and after that all was well".
So, consider thatb if your question IS identical to the OP, you can find the soluition in this thread.

Btw: Don't say "me to same problem" because, if we want to answer, we have to read all the thread again. Which, of course, nobody does .... ;)
It's up to YOU to details a max. The quality of the reply will be at the same level.

fakkundo

@Gertjan:

Hi,

People that are asking question nearly never post back to say : "it works now, I did this … and this .... and after that all was well".
So, consider thatb if your question IS identical to the OP, you can find the soluition in this thread.

Btw: Don't say "me to same problem" because, if we want to answer, we have to read all the thread again. Which, of course, nobody does .... ;)
It's up to YOU to details a max. The quality of the reply will be at the same level.

Good morning Gertjan, I appreciate your feedback. I've been trying to submit a new post yesterday to not update an old post like this one, but for any reason the forum is showing some errors while posting the new topic. Here's the information:

Behaviour: Captive Portal is partially operational after the v2.2.2 upgrade.
Scenario: PfSense v2.1.5 upgraded to v2.2.2. Upgrade was correct, but unreacheable via SSH/Web GUI after this process. Unit came back after a manual power cycle. My current setup includes voucher rolls + MAC pass thru auth, both methods were working before the upgrade.
Checking for related topics, I've found the following error in the auth log:

XXX logportalauth[36185]: Zone: XXX_sales - Error during table XXX_sales creation. Error message: file is encrypted or is not a database

Found a similar behaviour in an external website, indicating that stopping the CP service, saving/removing the captiveportalxxx.db file and starting the service again would fix the problem. I've completed this process but CP is still not working. Some MAC auth users have been reporting access issues, and voucher access seems to not work. Users goes back to captive portal auth page after insert their voucher.

Found this topic as well: https://forum.pfsense.org/index.php?topic=87864.0, no clear solution stated.

Any thoughts?

Gertjan

@fakkundo:

Any thoughts?

Yep.
I guess everything is said here https://forum.pfsense.org/index.php?topic=87864.0
In case of doubt: you have a pfSEnse config XML file, so re- install from scratch. One of the advantages will be : clean system files.

fakkundo

@Gertjan:

I guess everything is said here https://forum.pfsense.org/index.php?topic=87864.0
In case of doubt: you have a pfSEnse config XML file, so re- install from scratch. One of the advantages will be : clean system files.

Hello again Gertjan. I've installed v2.1.5 from the scratch, then restored the sys config using the xml file. Everything is working as a charm AGAIN, I'll keep this version for a while until the captive portal issues is solved.

Thanks again for your assistance

Gertjan

Captive portal issues solved ?
Meanwhile I'm using 2.2.2 some time now. This is a graphical result (real time) : http://www.test-domaine.fr/munin/brit-hotel-fumel.net/pfsense.brit-hotel-fumel.net/portalusers.html
These stats are from an hotel, so I do NOT control the device of our users (clients), neither what and how the clients are working with the portal.
All I know is that pfSense + captive portal works.
2.2.2 is rock solid.

Btw : I consider 2.1.5 completely different to 2.2.2 - it's a major kernel upgrade, PHP upgrade ad much more.
Something as a "in place" upgrade when it concerns BIG changes are not logic neither usable. Servers aren't upgraded like that, neither desktop PC's, neither firewall and routers.
Going from 2.1.4 to 2.1.5, ok, but 2.1.5 to 2.2.2 is another ball game.
Put the config file on a clean install - and it rocks.
And yes, sometimes its needed to look into the config XML file (its just a clear, readable file) to do some final trimming.
Stay away from packages if you can't stand the hard-core code parching.