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

    Unable to retrieve package info from https://packages.pfsense.org.

    pfSense Packages
    17
    43
    25.0k
    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.
    • panzP
      panz
      last edited by

      «Unable to retrieve package info from https://packages.pfsense.org. Cached data will be used.»

      Today I'm getting this error message. No changes in the configuration since 2 months.

      pfSense 2.3.2-RELEASE-p1 (amd64)
      motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

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

        Check to see if you have an Blocks in Snort. If your using pfBlocker check the Firewall Logs.

        Or if using Squid maybe it could be blocked there?

        This is the IP that resolves to packages.pfsense.org for me. It might be different for you.
        So check the logs for a similar IP address.

        208.123.73.88

        Or try to    ping packages.pfsense.org and see what the IP is and look at the Logs for any blocks.

        "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
        • panzP
          panz
          last edited by

          It was completely offline for a few hours; now it's back. Thank you!  :)

          pfSense 2.3.2-RELEASE-p1 (amd64)
          motherboard: MSI C847MS-E33 Micro ATX (with Intel Celeron CPU 847 @ 1.10 GHz) ~ PSU: Corsair VS350 ~ RAM: Kingston KVR1333D3E9S 4096 MB 240-pin DIMM DDR3 SDRAM 1.5 volt ~ NIC: Intel EXPI9301CTBLK (LAN) ~ NIC: D-Link DFE-528TX (CAM) ~ Hard Disk: Western Digital WD10JFCX Red ~ Case: Cooler Master HAF XB ~ power consumption: 21 Watts.

          1 Reply Last reply Reply Quote 0
          • N
            NetWiz
            last edited by

            Second day my pfsense machines can not get to package site. Ping OK. When I point my browser to https://packages.pfsense.org/ it shows packages.pfsense.org. WTF?

            1 Reply Last reply Reply Quote 0
            • D
              dmitripr
              last edited by

              @NetWiz:

              Second day my pfsense machines can not get to package site. Ping OK. When I point my browser to https://packages.pfsense.org/ it shows packages.pfsense.org. WTF?

              Same here. Subscribed for updates.

              1 Reply Last reply Reply Quote 0
              • B
                bennyc
                last edited by

                +1

                Just today I tried upgrading HW… after 2h I still had 'reinstalling packages'
                In the end I just swapped the disks (so I have a pfSense with packages  ;)), but still can't access package source from within pfSense.
                I have these nice errors in log, so something must be wrong  ???

                
Aug 7 21:43:09	php: /pkg_mgr_installed.php: XMLRPC communication error:
Aug 7 21:43:09	php: /pkg_mgr_installed.php: XML_RPC_Client: Connection to RPC server packages.pfsense.org:443 failed. 103

                No squid, no snort (yet, because it's down), basic setup. 2.1.4-RELEASE (amd64) on APU1C4.

                4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                1x PC Engines APU2C4, 1x PC Engines APU1C4

                1 Reply Last reply Reply Quote 0
                • B
                  bennyc
                  last edited by

                  Not getting it.

                  at home, still have this when I go to "System: Package Manager" -> "Available Packages"

                  Unable to communicate with https://packages.pfsense.org. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity.

                  But in the office (same ISP, same pfSense level but one is full and other is nano), I can open the page without issue?

                  Any hints on what might be causing this?

                  4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                  1x PC Engines APU2C4, 1x PC Engines APU1C4

                  1 Reply Last reply Reply Quote 0
                  • B
                    bennyc
                    last edited by

                    hmm.

                    dns resolves fine, traceroute brings me after 20 hops here:
                    packages.atx.pfmechanics.com (208.123.73.88)  132.033 ms  132.232 ms  135.681 ms

                    I haven't found any setting for package sources, really open for suggestions here  :-[

                    4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                    1x PC Engines APU2C4, 1x PC Engines APU1C4

                    1 Reply Last reply Reply Quote 0
                    • B
                      bennyc
                      last edited by

                      Extra symptom: going to the packages page makes pfSense gui inaccessible (happened twice too me while searching on the issue), seems it crashes the lighttpd daemon.
                      Going to stop for now, it's clearly not coöperating today  >:(

                      ps: Sorry for hijacking the thread, my bad, I know (even though it is related)

                      –edit spelling--

                      XMLRPC.JPG
                      XMLRPC.JPG_thumb

                      4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                      1x PC Engines APU2C4, 1x PC Engines APU1C4

                      1 Reply Last reply Reply Quote 0
                      • B
                        bennyc
                        last edited by

                        very strange… running 2.1.4-RELEASE (amd64) with custom kernel (no vga) on a mSata, I have this persistent issue on 2 different devices (APU1C and APU1C4)
                        I just created a nano version on a SD card, did a full export of my config (including RRD), uploaded it on the fresh nano, slammed that one in one of the boxes and after boot process I can open the "available packages" page without one issue ! (yes I even see the contents :o)

                        Go figure.

                        Not trying to be the wise-guy here, but now I'm pretty convinced there's something with the full image that is trying to access the packages repository. I found in meantime the file pkg-utils.inc and set it aside from the nano version. Going to boot again from the mSata and try to compare with that one. One never knows I could be lucky and see a difference  ::)

                        –edited to avoid anyone would believe this. see below for update--

                        4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                        1x PC Engines APU2C4, 1x PC Engines APU1C4

                        1 Reply Last reply Reply Quote 0
                        • B
                          bennyc
                          last edited by

                          No luck, the 2 files are identical  :(

                          Maybe I should stop searching here. (I find it strange there aren't more having the same issue)

                          I saw in the file that in turn it calls a bunch of other files, if any of the guru's should have ideas?

                          For the moment I'll just stick with the nano…

                          4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                          1x PC Engines APU2C4, 1x PC Engines APU1C4

                          1 Reply Last reply Reply Quote 0
                          • D
                            dmitripr
                            last edited by

                            The issue was resolved for me last night. I'm not sure what caused the resolution exactly. I had a problem with not being able to ping IPv6 addresses from my LAN (and from pfsense box). I didn't realize it at first, but then noticed that for some reason I didn't get an IPv6 address from my ISP – I had it before, but it was released for some reason.

                            I restarted the cable modem. After cable modem came back up, I did get IPv6 address, but now I noticed that the CPU utilization on my pfsense was staying at 50% (I have Atom D2550, 4 vCPUs, 2 cores). I checked system activity and noticed that processes named something like "services.check" and "debug.rules" were taking up the CPU cycles. I've never seen that before. I let it run for a few minutes, nothing changed, they kept running.

                            At that point I restarted by pfsense. The pfsense came back up, and now I had snort taking up 50% of the CPU, constantly. I killed snort service, and it was auto-restarted by the "services monitoring" package. After that the CPU utilization came back to the usual levels of 0-3%.

                            Everything is running well so far. I got the IPv6 address from ISP and can now ping IPv6 addresses. And can now access the packages site.

                            I'm not sure what caused all of this chaos. It's a little concerning that it just went crazy out of the blue like that. But I guess that's what you get when running multiple packages on the same platform, more chances for conflicts and chaos like that. I'm sure that played a factor in some way.

                            So, that's my story. :)

                            1 Reply Last reply Reply Quote 0
                            • B
                              bennyc
                              last edited by

                              Hi dmitripr, good it sorted out for you.

                              It seems I'm not there yet. I installed the sd card in my production box, loaded latest config again, booted, and it was even worse.
                              I was unable to see the available packages (that pesky XMLRPC msg again), but what was even worse is that I had no longer access to the forum (??)
                              Other pages no issue, pfSense forum did not open. (dns resolved however)
                              Reverted to the full install (has become easy, just change boot order ;D)
                              Now I have access to the forum again, but even though I did not touch the mSata, when I went to my packages page it couldn't display the version column anymore? So I went to the log, and found this new errors:

                              Aug 8 20:18:40	php: /pkg_mgr_installed.php: XMLRPC communication error:
Aug 8 20:18:40	php: /pkg_mgr_installed.php: XML_RPC_Client: Connection to RPC server packages.pfsense.org:443 failed. 103
Aug 8 20:14:16	php: /pkg_mgr_installed.php: XMLRPC request failed with error 5: Didn't receive 200 OK from remote server. (HTTP/1.1 502 Bad Gateway)

                              Pffff  >:(

                              I already restarted the whole, but no avail. I anyway scrapped my earlier statement "nano vs full" before anyone would take it for true  :-[

                              Really puzzled at this moment…

                              -- edit: expanded with other 2 errors --

                              4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                              1x PC Engines APU2C4, 1x PC Engines APU1C4

                              1 Reply Last reply Reply Quote 0
                              • B
                                bennyc
                                last edited by

                                for all reading this… another update. (quickly, who knows how long it continues working  :-)

                                All https from here to pfsense failed. Autoconfig backup, Forum, Portal, even the homepage, all inaccessible. And yes, packages is one of them.

                                So. I'll call it a day. I no longer believe it's a problem with my systems. And I'll check again tomorrow if I have access again. I should have known...  ::)

                                4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                                1x PC Engines APU2C4, 1x PC Engines APU1C4

                                1 Reply Last reply Reply Quote 0
                                • D
                                  dmitripr
                                  last edited by

                                  @bennyc:

                                  I had no longer access to the forum (??)

                                  I also couldn't access pfsense sites (form, packages … nothing). Looks like they were down for some time today. Don't think it has anything to do with the pfsense box, I couldn't access the sites from work either.

                                  Now, they seem to be back up.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    dmitripr
                                    last edited by

                                    Well, I just tried to access packages page again, and what do you know … doesn't work. Same error as before (in the original post of this thread).

                                    I don't think it's the router. Something's gotta be wrong with the packages server. It seems to be a hit or a miss.

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      maartens
                                      last edited by

                                      Definitely seems to be something wrong with the package server. pfSense attempts to do a POST to https://packages.pfsense.org/xmlrpc.php but this results in a 502 Bad Gateway error. Probably something is up with either nginx or PHP on the package server.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        Supermule Banned
                                        last edited by

                                        No go on 42 firewalls…. deffo something with the server...

                                        1 Reply Last reply Reply Quote 0
                                        • E
                                          eduardogoncalves
                                          last edited by

                                          I have a fresh install and isn't working…
                                          I can ping packages.pfsense.org from pfsense box.@dmitripr:

                                          Well, I just tried to access packages page again, and what do you know … doesn't work. Same error as before (in the original post of this thread).

                                          I don't think it's the router. Something's gotta be wrong with the packages server. It seems to be a hit or a miss.

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            Jambro1964
                                            last edited by

                                            So any ETA on a fix for the 502 error? SSL cert expire? ISP gateway change and filtering HTTPS?

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