a communications error occurred while attempting to call xmlrpc method host_firmware_version: request timed out due to default_socket_timeout php.ini setting
-
Hello everyone,
Maybe a good soul can give me a clue.
So, I am with Netgate 7100 hardware and in pfsense+ version and in HA
I just updated to 22.01 and since then the config sync no longer works with the following message:
a communications error occurred while attempting to call xmlrpc method host_firmware_version: request timed out due to default_socket_timeout php.ini setting
I read everything I found that might be related but that didn't solve my problem.
I would like to point out that before the update everything was working perfectly.
I also specify that my HA does not go through an int Wan but has its vlan and dedicated interface.
Thank you in advance those who have seen this problem on a forum somewhere or those who have had this problem.
Have a good day. -
Hello,
Same issue here with HA and dedicated link.
Did you found some fix for it ?pfsense 2.6.0-RELEASE (amd64)
-
@gringorion said in a communications error occurred while attempting to call xmlrpc method host_firmware_version: request timed out due to default_socket_timeout php.ini setting:
pfsense 2.6.0-RELEASE (amd64)
Hello,
We have worked a lot with Netgate support but there is no improvement.
In 15 days, I have to migrate my 7100 to version 22.05 and I will see if that solved the problem.
I come back to you to give you news -
@philippe-richard Same problem here on 2.7.0 ... complains about different fw versions, but they are the same.
Did you find a solution? @Gringorion
A communications error occurred while attempting to call XMLRPC method host_firmware_version
-
@hoegge
Hello
"Unfortunately", I migrated to "plus" and is much more stable/reliable for me -
@Gringorion
Hello, Last year when I posted the message, we were using pfSense+.
I think that sometimes updates go wrong and the only solution to fix it is to export the configuration, perform a clean installation with the new version, and then re-import the configuration file. -
@philippe-richard
FYI, and all :)
This is what I did with 2.6 and 2.7 without very much progress.
But a clean install plus with 2.7 config was ok for me -
@Gringorion Annoying. I'll try to take a look at the config files or some of the xmlrpc settings if I can find them in the file system - and compare to a clean install version of the same after clean install and then try to restore configs and see if it helps.