Alert "XMLRPC method captive_portal_sync" in 2.5
-
@luca-de-andreis Please provide more info about your CP configuration
-
Thanks for reply !!!!
I tried to completely delete all the configuration imported from version 2.4.5p1.
-
If I disable the captive portal everything works without warning.
-
If I set even a minimal configuration: define a zone, enable captive portal, select the interface and everything else set by default, no MAC no voucher no customization, nothing ...
-
-
I tried to convert NICs from virtio (vtnet) to e1000 (em) getting exactly the same error.
With the latest versions of PfSense the virtio works correctly even in HA mode. I double-checked everything and I don't think there are any errors in the HA configuration. It seems a problem of version 2.5, with 2.4.5p1 it works perfectly, I don't know .... -
I keep trying, with no results.
I updated to the latest version: 2.5.0.a.20210124 without success, the behavior is absolutely the same.
-
If I disable the "Captive portal" item in XMLRPC sync everything works correctly, the problem disappears.
-
No problems in the LOG regarding the gateways or network, everything works as it should and there are no alerts.
The alert occurs during the transition from secondary to primary.
I ran out of ideas :(
-
-
... I use 15 interfaces and 14 CARP VIPs (other several ALIAS VIPs).
Possible internal timeout ? -
YESSSSSSSSSSSS found the solution !!!!!!!!!!!!!!!!!!!!!
It's a bug. The problem disappears if I use the default web interface port (443) I used to use a non-standard port before (8443)
It is not an ACL problem, it's a bug.
-
@luca-de-andreis Hi,
I'm the user who developed this feature
I am actually a bit sorry for this issue... It's basically a stupid copy paste issue (coming from from there) where I forgot to properly rename a variable (
$port=>$xmlrpc_port) ...It also passed through all my tests (and the ones of Netgate) because I didn't think of changing the GUI port during them...I guess everyone's make mistakes
.It's not really critical through : the issue can easily be fixed by updating the file (using the Services->File manager menu. It's a one-line fix so it's ok i guess), by using the patch package (with this URL), or by simply reverting the GUI to the port 443 (which may not be an acceptable workaround...I understand)
I'm not entirely sure of what Netgate will do now that 2.5.0 is out there. If I read correctly @jimp comment on the issue i guess there will be a day-one patch containing few hotfixes including this one ?
-
Hi, no problem, for now the version 2.5.0 still presents this problem, however it is sufficient to modify the php file as you specified and everything will work again.
It's really not a problem, I just went crazy for at least a month because I thought it was my configuration problem and I couldn't find a solution ... everything seemed correct.Thanks so much
-
@luca-de-andreis the day-one patch just got applied on git. I'm guessing the new ISO is being generated, it should be available for everyone soon
-
We don't re-roll releases like that. There isn't really a "day one patch" per se. I committed a fix into git but that doesn't mean it goes anywhere beyond that yet.
You can install the System Patches package and then create an entry for
fef846ce7ec4158a140f359b0fb35182f6ae9db9to apply the fix, or you can make the change manually. -
@jimp Oh ok
But wait...What's the point to backport the fix into RELENG_2_5_0 then ?
-
@free4 said in Alert "XMLRPC method captive_portal_sync" in 2.5:
@jimp Oh ok
But wait...What's the point to backport the fix into RELENG_2_5_0 then ?
So it will be included in the next patch release, whenever that may be.
