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

    Are pfsense package server down?? "Unable to communicate to pfSense.com…

    Scheduled Pinned Locked Moved pfSense Packages
    15 Posts 12 Posters 9.5k 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.
    • A
      albert.hang
      last edited by

      I know this thread is old, but it's the only thing I've figured out on my own since joining the forum. I'm running 1.23RC1 and had the same issue. If you don't want to reinstall, run the setup wizard under the system menu. I noticed that even though I had entered my DNS under the WAN settings the wizard didn't list the DNS servers, so I ran the wizard and entered the DNS and everything worked fine.

      1 Reply Last reply Reply Quote 0
      • R
        rudraansh
        last edited by

        If you are using MultiWAN . and WAN connection is down, you will not be able to communicate with the server. because installing a package on Pfsense always require a WAN connection and it doesnt work with OPT 1 or anything.

        1 Reply Last reply Reply Quote 0
        • L
          lz2kc
          last edited by

          I have the same problem:
          Unable to communicate to pfSense.com. Please check DNS, default gateway, etc.

          From DIagnostic>Ping
          i have a ping to www.google.com, www.yahoo.com …
          but i have no a ping to www.pfsense.com or www.pfsense.org
          Ping output:

          PING pfsense.com (69.64.6.21) from 213.240.xxx.xxx(my ip address): 56 data bytes

          --- pfsense.com ping statistics ---
          3 packets transmitted, 0 packets received, 100.0% packet loss

          Note: Multi-wan is not supported from this utility currently.

          More information:
          STATUS > SYSTEM LOGS:
          php[400]: /pkg_mgr.php: XMLRPC request failed with error 2: Invalid return payload: enable debugging to examine incoming payload

          any ideas?

          1 Reply Last reply Reply Quote 0
          • I
            idelta
            last edited by

            No ideas. I have exactly same problem. Yesterday all was ok.

            1 Reply Last reply Reply Quote 0
            • Z
              Zanotti
              last edited by

              @idelta:

              No ideas. I have exactly same problem. Yesterday all was ok.

              Me too.

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

                Fixed

                /Perry
                doc.pfsense.org

                1 Reply Last reply Reply Quote 0
                • I
                  idelta
                  last edited by

                  Yes ! Thanks. Works.
                  But :
                  On snapshot server also strangeness.
                  From 14.11 "Last modified" for updates and livecd_install folders changes, but no new snapshot-s.

                  1 Reply Last reply Reply Quote 0
                  • L
                    lz2kc
                    last edited by

                    It works!
                    Thanks!

                    1 Reply Last reply Reply Quote 0
                    • L
                      Loewenpapa
                      last edited by

                      Is the package-server down again???

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

                        i have the same problem, how did you fix it?
                        my pfsense was working right but 3 weeks ago fails  and i can't do it work again

                        1 Reply Last reply Reply Quote 0
                        • H
                          hansol
                          last edited by

                          same problem

                          traceroute to pfSense.com

                          9  po1.ar4.FRA3.gblx.net (67.16.137.138)  31.539 ms  31.270 ms  31.196 ms
                          10  ge-6-11.car2.Frankfurt1.Level3.net (195.122.136.245)  31.592 ms  31.654 ms  31.452 ms
                          11  vlan99.csw4.Frankfurt1.Level3.net (4.68.23.254)  41.974 ms  35.432 ms  35.842 ms
                          12  ae-92-92.ebr2.Frankfurt1.Level3.net (4.69.140.29)  31.560 ms  31.946 ms  31.982 ms
                          13  ae-42-42.ebr2.Washington1.Level3.net (4.69.137.54)  120.232 ms  120.268 ms  119.913 ms
                          14  ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  119.874 ms
                              vlan90.csw4.Washington1.Level3.net (4.69.149.254)  120.963 ms  121.956 ms
                          15  ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141)  121.891 ms  120.432 ms  120.195 ms
                          16  ae-2-2.ebr3.Atlanta2.Level3.net (4.69.132.85)  133.780 ms  134.042 ms  134.874 ms
                          17  ae-73-73.csw2.Atlanta2.Level3.net (4.69.148.254)  134.600 ms  134.776 ms  134.621 ms
                          18  ae-72-72.ebr2.Atlanta2.Level3.net (4.69.148.249)  133.407 ms  142.983 ms  143.782 ms
                          19  ae-8-8.car1.Nashville1.Level3.net (4.69.140.229)  146.040 ms  146.072 ms  145.997 ms
                          20  ae-11-11.car2.Nashville1.Level3.net (4.69.140.225)  147.292 ms  147.515 ms  147.122 ms
                          21  ae-2-2.car2.Louisville1.Level3.net (4.69.140.221)  147.103 ms  146.108 ms  146.197 ms
                          22  ae-11-11.car1.Louisville1.Level3.net (4.69.140.217)  147.254 ms  147.031 ms  147.475 ms
                          23  BLUEGRASSNE.car1.Louisville1.Level3.net (4.59.184.6)  146.184 ms  147.547 ms  146.077 ms
                          24  * * *
                          25  * * *
                          26  * * *
                          27  * * *
                          28  * * *
                          29  * * *

                          1 Reply Last reply Reply Quote 0
                          • Cry HavokC
                            Cry Havok
                            last edited by

                            I can reach pfsense.org just fine and pfsense.com. Can your web browser connect?

                            1 Reply Last reply Reply Quote 0
                            • H
                              hansol
                              last edited by

                              yes, borwser connect fsense.org and fsense.com

                              in System: Package Manager >> 1.2.3-RELEASE packages  and  Installed packages is blank .

                              I did restore and reinstall package and

                              Loading package configuration …
                              Starting package deletion for ...
                              done.
                              Removing dns-server components...
                              Configuration... done.
                              Saving updated package information... overwrite!
                              The dns-server package is not installed.

                              Installation aborted.Writing configuration... done.
                              Starting service.

                              All packages reinstalled.

                              My dns is 8.8.8.8

                              relased.jpg
                              relased.jpg_thumb
                              installed.jpg
                              installed.jpg_thumb

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