Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PFBlockerNG xmlrpc error

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 948 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      pdrass
      last edited by

      I'm getting lots of xmlrpc errors about "authentication failed" on the new 2.4 upgrade.

      Exception calling XMLRPC method merge_installedpackages_section #-1 : Authentication failed: Invalid username or password @ 2017-11-14 16:00:23
      

      It worked perfectly find in the prior 2.3.x version.  It's replicating to 3 other firewalls.

      A communications error occurred while attempting to call XMLRPC method merge_installedpackages_section: Unable to connect to tls://ip_or_hostname_here(redacted):port#(redacted). Error: Operation timed out @ 2017-11-14 17:00:50
      

      There's another one.  Again, this worked perfectly on the prior version.

      Is this possibly a problem with httpS's cert being self signed?  I'm authenticating to httpS > admin > IP or hostname > port (not 443) and the password.

      Anyone else have this problem?

      Thanks!

      1 Reply Last reply Reply Quote 0
      • P
        pdrass
        last edited by

        Anyone…anyone...Frye...Frye...Beuler...Beuler  ;D

        XMLRPC is still failing on the 3 firewalls I'm replicating to.

        ===[  XMLRPC Sync ]===================================================
        
         Sync with [ https://host1.chickenkiller.com:10000 ] ... Failed!
        
         Sync with [ https://host2.chickenkiller.com:10000 ] ... Failed!
        
         Sync with [ https://x.x.x.x:10000 ] ... Failed!
        

        I can see, manage and access those hosts just fine, ipsecvpn works and everything but xmlrpc won't replicate the settings.  It did just fine in the prior version of PFSense.

        Anyone at PFSense have some insight here?  I suspect it doesn't like the httpS self signed certs that are default on the boxes but it's only a guess.

        1 Reply Last reply Reply Quote 0
        • BBcan177B
          BBcan177 Moderator
          last edited by

          Are both boxes running 2.4? One can't be using 2.3.x as that is incompatible.

          "Experience is something you don't get until just after you need it."

          Website: http://pfBlockerNG.com
          Twitter: @BBcan177  #pfBlockerNG
          Reddit: https://www.reddit.com/r/pfBlockerNG/new/

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.