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

    Cannot connect to netgate servers during fresh pfsense install

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    47 Posts 12 Posters 15.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.
    • T
      timboau 0
      last edited by

      What a S&^t show - someone needs their head read trying to make an online only router installer. Have to be the most $$ driven decision ive seen from Netgate to date.

      1 Reply Last reply Reply Quote 3
      • N
        nardo
        last edited by

        I have the very similar issue, but the problem is not with ntp but with PING. In my setup there is no option to allow ICMP packets. With this installer I can't install pfSense+ without functional ping?
        curl -I to group3.sites.hscoscdn00.net get no error

        stephenw10S 1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator @nardo
          last edited by

          @nardo said in Cannot connect to netgate servers during fresh pfsense install:

          curl -I to group3.sites.hscoscdn00.net get no error

          From the installer after it fails?

          Can you curl https://ews.netgate.com?

          N 2 Replies Last reply Reply Quote 0
          • N
            nardo @stephenw10
            last edited by

            @stephenw10
            09d6af56-bd7c-4ca4-8a5e-27400847f3a0-image.png

            Yes it is working.

            1 Reply Last reply Reply Quote 0
            • N
              nardo @stephenw10
              last edited by

              @stephenw10
              And this is the error log from which I think that the issue is PING result ;(

              c44c356a-3e03-473b-901a-097234d64091-image.png

              It is in daemon.log

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Hmm, the next version will not require any other link check, including ping.

                1 Reply Last reply Reply Quote 0
                • F
                  firefly2299
                  last edited by

                  After a lot of struggle this was my solution;

                  1. It seems a static ip in the 192.168.1.x range is restricted so I changed the ip address of my isp router to 192.168.13.x.

                  2. Powered off my pfsense1100 booted with usb (only the righter slot works) and pressed the [y] button a couple of times to prevent autoboot. Then I started the ‘recovery’ instead of ‘install’. And in the recovery I only opened the shell to ping a website and confirmed that my internetconnection was working. Then I typed exit to start with the install. And everything worked instantly.

                  3. During the install you get at 3 moments the feeling that everything is stuck. Especially during the last stage, -the real install- just wait for like 10 minutes.

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