Voucher Sync over SSL?
I'm trying to sync vouchers between two pfSense (2.0-RC3 (amd64) built on Mon Sep 12 00:52:44 EDT 2011 ) boxes. Both boxes are configured to use HTTPS for the GUI. When entering the master's IP/authentication information into the slave box, I get the following error on the slave:
An error code was received while attempting CaptivePortalVoucherSync XMLRPC sync with http://192.168.xxx.xxx:yyy - Code 2: Invalid return payload: enable debugging to examine incoming payload
It appears as though it's connecting to the correct IP and port, but it's using HTTP instead of HTTPS, and therefore, failing. Moreover, I don't see an option on the voucher sync page to select what protocol to use. Is this a bug, feature or some screw up on my part?
cmb last edited by
It uses the port and protocol used by the system doing the syncing, they must match. If it's trying to sync on HTTP, the source must be using HTTP.
The port and protocol that you mention are referring to that of the webConfigurator, not the captive portal itself, correct? If so, both the master and slave webConfigurators are running HTTPS and both are on the same port.
If you're referring to the capture portal itself, both are running on HTTP.
cmb last edited by
Right, what it's using for the web interface is what it uses to sync vouchers. How the CP itself is set doesn't matter either way.
Unfortunately, I still cannot get this to work. The webConfigurator on both master and slave boxes is set to HTTPS on the same port, but the voucher sync on the slave still appears to access the master on the HTTP port.
I even enabled the WebGUI Redirect option (which actually disables the automatic redirection from HTTP to HTTPS in the webConfigurator) on both master and slave boxes, but that didn't seem like it did anything for the voucher sync issue.
On a side note, I have upgraded both master and slave boxes to v2.0 RELEASE amd64 since my original post. If anyone has any ideas on why this might be happening, I'd really appreciate the insight.
sandern last edited by
I'm having the same issue on Pfsense 2.0 final.
I noticed one thing: in the system logs I get the message "Disallawing CARP sync loop". This happens everytime I try to sync the captive portal database.
And for the record: I only set the sync up on the slave, not on the master.
I'm not seeing that error on my setup, but I don't have CARP setup at all. In fact, I don't see any logs related to the captive portal sync being successful or not on the master. The slave logs the message posted in my original post.