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

    Php: /pkg_mgr.php: XMLRPC communication error: Permission denied

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 2 Posters 3.0k 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
      PaulS
      last edited by

      I just hooked my pfsense 1.2 box up to my DSL modem and I cannot load packages.  When I go to the Packages option I get the error:

      Unable to communicate to pfSense.com. Please check DNS, default gateway, etc.

      The system log shows:

      php: /pkg_mgr.php: XMLRPC communication error: Permission denied

      But I have no problems pinging google.com:

      Ping output:

      PING google.com (72.14.207.99) from 67.76.86.131: 56 data bytes
      64 bytes from 72.14.207.99: icmp_seq=0 ttl=238 time=66.483 ms
      64 bytes from 72.14.207.99: icmp_seq=1 ttl=238 time=65.802 ms
      64 bytes from 72.14.207.99: icmp_seq=2 ttl=238 time=65.902 ms

      –- google.com ping statistics ---
      3 packets transmitted, 3 packets received, 0% packet loss
      round-trip min/avg/max/stddev = 65.802/66.062/66.483/0.300 ms

      Thanks for any help,
      Paul

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

        I wanted to update this with some more info to see if anyone could pin down what is wrong.  Here is the network:

        
                          Internet Conn 1                                                                   Internet Conn 2
                                    |                                                                                     |
                       DSL Modem (Bridged)                                                          2801 Cisco Router(192.168.10.1/24)
                                    |                                                                                     |
                          pfSense WAN(67.76.86.131/25) pfSense LAN(192.168.10.29/24)–--------------------------------------
                                                                                                                          |
                                                                                                                        Client Machine (192.168.10.157/24)
        
        

        Now with the default GW set to 67.76.86.128 (correct for the DSL) the pfSense box has trouble reaching the Internet but not in all cases. My squid install fails with the permission error as well as the internal package manager.  The ping, tracert and NAT routing for the client all work fine with fqdn entered and not just IP addresses.  If I open the WAN adapter properties and change the default GW to 192.168.10.1 and retest everything works without any problems.  Now I am not trying to do dual WAN or load balancing just yet, the production network uses 192.168.10.1 and I just wanted to offload web traffic to 67.76.86.131/24 via squid.  Thanks.

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

          No one even has a shot in the dark on this?  pfsense looks like it could be a great tool - may be I just need to wait until it matures.

          1 Reply Last reply Reply Quote 0
          • C
            cybrsrfr
            last edited by

            The core developers have been working very hard on the upcoming releases pfSense 1.2.1 and 1.3. Today I was work on 2 phone systems so I've also been very busy.

            I believe the package url is: http://files.pfsense.org/packages/
            Can you manually see the location from behind the firewall?

            I just installed squid on my  pfSense 1.2-RELEASE
            built on Wed Apr 23 21:04:50 EDT 2008. It installed fine.

            This could have been a routing issue on the internet.
            Try the package install again and see if it is working now?

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