• After upgrade 1100 has failed

    11
    0 Votes
    11 Posts
    2k Views
    S
    @stephenw10 ah, ‘twas late, didn’t look…step 9: https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html
  • Post 2.7 upgrade from 2.6 No Pkg Mgr Access

    5
    0 Votes
    5 Posts
    272 Views
    D
    @stephenw10 I appreciate that. You might consider making it easier to find this for others. I spent a few hours with this... frustrating! Thanks for a great product !
  • Problem installing net gate 4200

    33
    0 Votes
    33 Posts
    2k Views
    M
    @bigbob said in Problem installing net gate 4200: @bigbob the connection I'm looking at says usb10/100/1000 LAN and then all those numbers I posted above. @SteveITS also says domain is home.arpa When you buy a SG-4200, or any other appliance from Netgate, you get a TAC Lite plan, which includes zero to ping support. https://www.netgate.com/support I suggest you check that, they are very good and the support is amazing.
  • unable to check for updates

    7
    2
    0 Votes
    7 Posts
    822 Views
    X
    @viragomann thank you
  • Unable to check for updates

    updates
    15
    0 Votes
    15 Posts
    2k Views
    D
    @stephenw10 @Gertjan Reinstall succeeded, thanks for troubleshooting with me! [image: Wk0l-UTk-Mu-G.png]
  • Unable to upgrade 2.6.0 to 2.7.2

    9
    0 Votes
    9 Posts
    1k Views
    stephenw10S
    Just refresh the page. When you first change branch it refreshes the pkg system in the background.
  • migrating from chinese hardware to an SG-1100 ?

    8
    0 Votes
    8 Posts
    795 Views
    stephenw10S
    Nope I think that is a real bug. I just replicated it. It's fixed in 24.03.
  • Pfsense Plus upgraded to beta 24.03.b.20240322.1708 caused crash report

    4
    0 Votes
    4 Posts
    827 Views
    M
    Thanks all
  • 0 Votes
    5 Posts
    661 Views
    B
    @stephenw10 Thank you very much! It was a great idea and it works perfectly!
  • Unable to boot to new beta: 2023.09.1 to 24.03.b.20240322.1708

    6
    0 Votes
    6 Posts
    727 Views
    stephenw10S
    Thanks. We managed to replicate it locally. Fix is in the works....
  • Netgate 2100 pfsense+ update path

    3
    0 Votes
    3 Posts
    655 Views
    K
    @SteveITS Thanks, that fixed my problem!
  • unable to check for updates | pfsense 3100 | 23.09

    Moved
    2
    0 Votes
    2 Posts
    316 Views
    S
    @dduckluk https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors
  • 0 Votes
    4 Posts
    625 Views
    D
    @stephenw10 OK, I had a typo. Not egal but legal. My eyes, not 23 anymore
  • 0 Votes
    11 Posts
    2k Views
    D
    I had the same issue. Went 2.7.0 first, then 2.7.2. (Oops, the rest was lost) I switched branches back and forth. Tried command line stuff as described on the upgrade help page - also on 2.7.0 branch. And at some point I was able to go to 2.7.2. But I don't know what was the problem and I don't know what was the solution. On another machine I just reinstalled with 2.7.2 because trying took too long.
  • Unable to upgrade from 23.05.1 to 23.09.1

    8
    0 Votes
    8 Posts
    778 Views
    stephenw10S
    Indeed, adding more cores should not change the NDI. Send me your current NDI in chat again and I'll check it.
  • dashboard of 2.7.2 shows 23.09.1 available - why?

    5
    0 Votes
    5 Posts
    591 Views
    D
    @stephenw10 They show 23.09.1. Last Plus version on these devices was 23.05. 23.09.1 already costs money. And back to 23.05 (if possible), I see no reason. So just drop them.
  • Netgate 8200 Max pfsense+ v22.05.1 local disk boot after install.

    10
    0 Votes
    10 Posts
    1k Views
    Sergei_ShablovskyS
    @emmdee said in Netgate 8200 Max pfsense+ v22.05.1 local disk boot after install.: After install, at least on the 7100 devices, I can always just load the boot menu and choose the internal disk after installing and it bypasses the USB as expected. This avoids having to get someone physically near the device the pull the USB for initial boot. I do realize the installer instructions say to physically remove the USB to reboot, however it also says this for the 7100 device and it works fine choosing from the boot loader. The reason I'm trying to avoid physically removing the USB for each of these installs (I have to do several of these) is because these devices are located globally and it can take days for an international support request to the local datacenter to pull the drive, then I "hope" it works, and they have to then reinstall the drive when I'm done again anyways (for ECL usage) and there is back & forth with the facility crews and it can take days just to work with the datacenter depending on their location and facility SLA and it costs my company money every time I open a remote hands request. Screenshot hopefully gives a good indicator of what I'm seeing. [image: Screenshot-2024-02-22-at-12-12-27.png] Here is the menu option after selecting < to show the path: [image: Screenshot-2024-02-22-at-13-10-32.png] I can boot to USB with no issue and reinstall as needed. I've tried reinstalling several times and with different options. …… I'm on a serial connection so it's a little difficult to catch all messages. I'm just looking for some insight or ideas on what I could try or diagnose remotely over a serial console without giving on-site teams the runaround. I can hop into an installer shell chrooted…. Let’s ask one question: how You connect to the pfSense itself in data center: by SSH on a dedicated uplink; OR by “Special request for KVM access” to DC crew for extra payment? Because of issues like this I ALWAYS prefer bare metal servers that have 2xPSU and BMC (iRMC, iRMC, etc…) on NON-SHARED (multiplexed) ETH. And Yes, 2 physical uplinks better than 1 (even in same DC, even link aggregator switch are above in the same rack). Even TOC in this case may be decrease because less numbers of “Special Requests” to DC crew. But You ALWAYS have FULL server MANAGEMENT, MONITORING through SSL serts, and even MOUNTING REMOTE STORAGE.
  • Upgrading from 2.3.4 to 2.7.2

    4
    0 Votes
    4 Posts
    864 Views
    S
    @stephenw10 Yep, I that resolved the error for one of the configs. Let me try editing the configs on the other 2 firewalls.
  • SG 3100 m.2 515GB SSD and how to install OS

    3
    0 Votes
    3 Posts
    490 Views
    stephenw10S
    Yup open a ticket and request the recovery image: https://www.netgate.com/tac-support-request
  • Upgrade from 23.01 to 23.05 or 23.09?

    3
    1
    0 Votes
    3 Posts
    771 Views
    stephenw10S
    Yup you should be able to upgrade to 23.09 then to 23.09.1. Though you could also upgrade to 23.05.1 then 23.09.1. It shouldn't matter which way you do that. Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.