Problems with captiveportal after upgrading to 2.2
-
Try to rename current captive portal database and see if it get's working again.
file is under /var/db/captiveportal….db
I've tried, I've called it captiveportalNEW.db but it seems not working yet.
-
Try to rename current captive portal database and see if it get's working again.
file is under /var/db/captiveportal….db
ok…but if I rename the db how can the pfsense know which is the db?
The active users database is created automatically on captive user login process. 2.1 uses sqlite2 and 2.2 uses sqlite3. As pfsense does not comes with sqlite 2.2, database can't be migrated but can be recreated.
Can you see if there are only this captive database on your dir? Did ou tried to reinstall the service after renaming it?
-
Try to rename current captive portal database and see if it get's working again.
file is under /var/db/captiveportal….db
ok…but if I rename the db how can the pfsense know which is the db?
The active users database is created automatically on captive user login process. 2.1 uses sqlite2 and 2.2 uses sqlite3. As pfsense does not comes with sqlite 2.2, database can't be migrated but can be recreated.
Can you see if there are only this captive database on your dir? Did ou tried to reinstall the service after renaming it?
There is also captiveportalcpzone.db
I've only tried to restart the service. -
There is also captiveportalcpzone.db
I've only tried to restart the service.Try to rename that too.
-
There is also captiveportalcpzone.db
I've only tried to restart the service.Try to rename that too.
Nothing it doesn't work
-
I have captive portal working on 2.2. I guess you're still with old database files being called.
The errors shows what database file is broken?
-
I have captive portal working on 2.2. I guess you're still with old database files being called.
The errors shows what database file is broken?
I get this:Zone: cpzone - Error during table cpzone creation. Error message: file is encrypted or is not a database
-
Make a config backp and then disable captive portal and move/delete old databases to another folder.
Captive portal configuration stays on xml. -
Make a config backp and then disable captive portal and move/delete old databases to another folder.
Captive portal configuration stays on xml.I've already done config backup before upgrade to 2.2. Anyway which database in /var/db have I to delete?
-
Captive portal databases.
You move to another folder instead of deleting it if you prefer. -
Captive portal databases.
You move to another folder instead of deleting it if you prefer.ok I've copied all files captiveportal***.db and then deleted.
These are the logs:
Jan 31 19:20:05 logportalauth[95869]: Zone: cpzone - Reconfiguring captive portal().
Jan 31 19:20:27 check_reload_status: Reloading filter
Jan 31 19:20:05 check_reload_status: Syncing firewall
and this lighttpd[89587]: (server.c.1558) server stopped by UID = 0 PID = 27770But it seems not working yet…
-
Did you disabled/enabled the service after removing the database files?
-
Did you disabled/enabled the service after removing the database files?
yes done! it doesn't work.
-
Well, I have it working. You need somebody else experience with 2.1 to 2.2 captive portal migration.
Postfix package will have similar issues but I'm writing a guide for package migration when pbi binaries get working…
-
No problems with migration here… (If you cannot get it working, a clean install and config restore takes minutes.)
-
No problems with migration here… (If you cannot get it working, a clean install and config restore takes minutes.)
a clean install of 2.1.5 or 2.2?
-
Up to you, though 2.1 is pretty much a dead end.
-
Up to you, though 2.1 is pretty much a dead end.
I will try a clean install of 2.2 on another machine.
-
No problems with migration here… (If you cannot get it working, a clean install and config restore takes minutes.)
Minutes??? I've tried to reinstall pfsense n times and it doesn't work. After restore I get mismatch error and I've tried but I am not able to set the right interfaces.
I don't understand. Error in the backup file? -
You won't have much luck with restoring 2.2 configuration backup on 2.1.x
