[SOLVED] Captive portal: cannot enable vouchers after 2011-03-02 update
-
I did auto update today morning and after that I realized I could not add more vouchers (the "+" icon missing). I tried to disable the voucher section and even the whole captive portal. Now I am not able to enable vouchers again - the input fields are all greyed out and I am not able to change their content (except the four in the bottom section "Voucher database synchronization"). But they are filled out (screenshot "before"). If I enable the vouchers and click save, I get errors saying I was supposed to fill these fields (screenshot "after").
I restarted the whole pfSense system, but to no avail.
-
You are sure you do not have removed all the vouchers db by accident?
-
Well, yes, I am. I did nothing abnormal.
I'm going (tomorrow) to reinstall the pfSense from the CD, try vouchers, let the system update and try vouchers again and see if I am able to replicate the problem. -
I cannot wait till tomorrow :) so I went on.
I tried something else: I reverted back to the factory defaults instead of installing from the scratch. The system restarted, I went through the basic setup (wan, lan). After I was done, I looked into the System: Firmware: Auto Update tab. And surprisingly I saw there:
A new version is now available Current version: 2.0-RC1 Built On: Wed Mar 2 17:47:38 EST 2011 New version: Thu Mar 3 02:13:32 EST 2011 Update source: http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters/
Why surprising? I thought that getting back to factory defaults should be just about loading the original configuration files, not binaries.
But OK. I invoked auto-update and it started downloading.
Auto Update Download Status ---------------------------------------------------- Current Version : 2.0-RC1 Latest Version : Thu Mar 3 02:13:32 EST 2011 File size : 90282861 Downloaded : 3629425 Percent : 4% ----------------------------------------------------
Apparently it downloaded the whole pfSense image. BUT: after it had finished I got this:
This image is not digitally signed. Update cannot continue. You can disable this check on the Updater Settings tab.
Interesting that unsigned updates are enabled in default. I tried to manually set the default auto update URL to "pfSense Stable Release Updates" and the Auto update tab then showed that my system was up-to-date. I think this should be the default, huh?
But I continued with checking the "Unsigned images" option and downloaded the update again, this time everything went well, the system updated itself and restarted. After boot-up I checked up the "Services: Captive portal: Vouchers" tab and guess what: it looked OK. :) The buttons for adding/editing/deleting vouchers were where they were supposed to be (now that's a sentence - were were were ;D). And they worked - I tried to create another voucher - no problems. Eventhough I used this unsigned image which I first suspected to be the cause of the vouchers malfunction, now the Captive portal works as expected.
So - the story is over for now. I don't know what could have happened if the first case. I am going to monitor it closely in the future. But I am now setting my system to download only stable and signed images.
-
But I am now setting my system to download only stable and signed images.
I think the image needs to be downloaded before it can be checked for being signed.
Snapshot builds are not signed - see http://doc.pfsense.org/index.php/Can_I_upgrade_my_pfSense_through_the_web_interface%3F
-
A-ha, thanks for information. :)
-
I did auto update today morning and after that I realized I could not add more vouchers (the + icon missing). I tried to disable the voucher section and even the whole captive portal. Now I am not able to enable vouchers again - the input fields are all greyed out and I am not able to change their content (except the four in the bottom section "Voucher database synchronization"). But they are filled out (screenshot "before"). If I enable the vouchers and click save, I get errors saying I was supposed to fill these fields (screenshot "after").
I restarted the whole pfSense system, but to no avail.
Hi,
I had a similar problem in the past with an older snapshot. Don't know why the "+" wasn't there to create vouchers. Not sure, but I think I did a new installation some days later and then it worked. I created a thread here but didn't get any answer.
-
Running 2.0-RC1 (i386) built on Mon Feb 28 18:12:00 EST 2011 on Vmware Server 2
Having exactly the same problem after tweaking around the Captive Portal ( i.e, switching HTTP - HTTPS back and forth with one voucher still logged in, changing the login page content, etc) I get the same empty field error
I remember seeing in the log that pfsense can't bound to port 8000 because it's already in used.
I've tried restarting the machine, but to no avail.
-
Try to backup your config, and revert to factory defaults. Check out the Captive portal whether it works - I suppose it will.
Then load your configuration from backup and check how the portal behaves now.