• Problems upgrading? Check the Troubleshooting Upgrades documentation

    Pinned Locked
    1
    2 Votes
    1 Posts
    15k Views
    No one has replied
  • 0 Votes
    1 Posts
    7k Views
    No one has replied
  • 2 Votes
    1 Posts
    8k Views
    No one has replied
  • 0 Votes
    1 Posts
    6k Views
    No one has replied
  • 0 Votes
    2 Posts
    367 Views
    stephenw10S
    Try running pkg -d update, see what errors it produces. What WAN type do you have? How is your DNS configured?
  • After upgrade from 24.11 to 25.0.7.1 lagg port did not work

    7
    0 Votes
    7 Posts
    2k Views
    stephenw10S
    Hmm, it's a lagg with one member port? Cross chassis?
  • Error when xxtrat PFSENSE ISO file

    5
    0 Votes
    5 Posts
    433 Views
    patient0P
    @Gertjan said in Error when xxtrat PFSENSE ISO file: The error "0x80070522 " implies a lot. I put all my bets on "Microsoft Windows" ^^ You are probably right, not seen any for a long time ... not using the big W.
  • Not being able to install in Proxmox / OVH, WAN gateway out of scope.

    3
    0 Votes
    3 Posts
    182 Views
    S
    @patient0 said in Not being able to install in Proxmox / OVH, WAN gateway out of scope.: @Salva_F use the search, Luke: OVH - cannot set wan interface default gateway. TL;DR: the online installer does not allow you to set a remote gateway (yet). Your best option is to install pfSense CE 2.7.2 (find the offline installer here: https://atxfiles.netgate.com/mirror/downloads/) and upgrade from there to 2.8.1. Thanks, that was one of my options .. but I wanted to be sure that I was not missing anything. BR.
  • 0 Votes
    6 Posts
    963 Views
    R
    One other thing I also did was cp libmd.so.6 to libmd.so.7 to see if I could get pkg to work, and it did work. I don’t think it made a difference in the end, but wanted to mention it. Also after the upgrade finished, it did overwrite that copy with the actual proper file.
  • pfSense+ 24.11 to 25.07 upgrade failed - Netgate 6100 Max appliance

    15
    0 Votes
    15 Posts
    3k Views
    J
    @sandie Cleaning up boot environments also resolved this issue on a Netgate 4100. It would be great if they caught the issue and provided better error message, or remove old boot environments that are over a year old. Went from 1.9GB of free disk space to 4GB of usable space. for others seeing this issue. this output was during the clean up process, there were several more entries at the start, but weren't in my buffer anymore. [25.07.1-RELEASE][root@pfSense.home.arpa]/root: df -h Filesystem Size Used Avail Capacity Mounted on pfSense/ROOT/default 3.2G 1.3G 1.9G 40% / devfs 1.0K 0B 1.0K 0% /dev pfSense/var 1.9G 3.5M 1.9G 0% /var pfSense/tmp 1.9G 888K 1.9G 0% /tmp pfSense/home 1.9G 96K 1.9G 0% /home pfSense/var/db 5.9G 4.0G 1.9G 68% /var/db pfSense/var/log 1.9G 4.1M 1.9G 0% /var/log pfSense/var/cache 1.9G 96K 1.9G 0% /var/cache pfSense/var/tmp 1.9G 112K 1.9G 0% /var/tmp pfSense/ROOT/default/cf 1.9G 1.7M 1.9G 0% /cf pfSense/ROOT/default/var_cache_pkg 2.3G 402M 1.9G 17% /var/cache/pkg pfSense/ROOT/default/var_db_pkg 1.9G 7.9M 1.9G 0% /var/db/pkg tmpfs 4.0M 140K 3.9M 3% /var/run devfs 1.0K 0B 1.0K 0% /var/dhcpd [25.07.1-RELEASE][root@pfSense.home.arpa]/root: bectl list BE Active Mountpoint Space Created auto-default-20240314022141 - - 627M 2024-03-14 02:21 default NR / 5.01G 2025-09-13 14:18 default_20240413162830 - - 29.8M 2024-04-13 16:28 default_20240413162830_20240413162833 - - 532M 2023-05-22 16:08 default_20250913141802 - - 822M 2025-01-21 10:06 [25.07.1-RELEASE][root@pfSense.home.arpa]/root: bectl destroy default_20240413162830_20240413162833 [25.07.1-RELEASE][root@pfSense.home.arpa]/root: bectl list BE Active Mountpoint Space Created default NR / 4.07G 2025-09-13 14:18 default_20240413162830 - - 1.06G 2024-04-13 16:28 default_20250913141802 - - 822M 2025-01-21 10:06 [25.07.1-RELEASE][root@pfSense.home.arpa]/root: df -h Filesystem Size Used Avail Capacity Mounted on pfSense/ROOT/default 5.4G 1.3G 4.1G 24% / devfs 1.0K 0B 1.0K 0% /dev pfSense/var 4.1G 3.5M 4.1G 0% /var pfSense/tmp 4.1G 240K 4.1G 0% /tmp pfSense/home 4.1G 96K 4.1G 0% /home pfSense/var/db 8.1G 4.0G 4.1G 50% /var/db pfSense/var/log 4.1G 4.1M 4.1G 0% /var/log pfSense/var/cache 4.1G 96K 4.1G 0% /var/cache pfSense/var/tmp 4.1G 112K 4.1G 0% /var/tmp pfSense/ROOT/default/cf 4.1G 1.7M 4.1G 0% /cf pfSense/ROOT/default/var_cache_pkg 4.5G 402M 4.1G 9% /var/cache/pkg pfSense/ROOT/default/var_db_pkg 4.1G 7.9M 4.1G 0% /var/db/pkg tmpfs 4.0M 140K 3.9M 3% /var/run devfs 1.0K 0B 1.0K 0% /var/dhcpd/dev
  • pfSense CE 2.8.0 upgrade stalls after reboot and gets stuck in Stage 2

    153
    0 Votes
    153 Posts
    30k Views
    stephenw10S
    It looks like we are close to finding a solution to the HP DL issue (and likely other hardware).
  • check_upgrade: "Updating repositories metadata" returned error code 1

    91
    0 Votes
    91 Posts
    19k Views
    S
    fwiw, after checking a few other systems I am seeing this exact notice on several other 2.8.0 systems. Now I am geussing the above system had the notice before upgrading to 2.8.1.
  • 25.07 upgrade on Netgate 4100 gets rolled back

    13
    0 Votes
    13 Posts
    3k Views
    stephenw10S
    Hmm, I agree. Let me see what we can do here.
  • 0 Votes
    6 Posts
    1k Views
    stephenw10S
    Check for rogue repo files here: [2.8.1-RELEASE][admin@cedev-2.stevew.lan]/root: ls -ls /usr/local/etc/pkg/repos/ total 1 1 -rw-r--r-- 1 root wheel 25 Aug 28 17:10 FreeBSD.conf 1 lrwxr-xr-x 1 root wheel 55 Sep 5 12:02 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-0002.conf It's been a long while since I tried pf2ad but I'm pretty sure it has an install/uninstall script that should do it. Unless it's completely broken!
  • Firmware/Package update slow, missing mirror?

    17
    0 Votes
    17 Posts
    1k Views
    jimpJ
    Everything should be back to normal now for IPv6 connectivity, there was an upstream issue that's been resolved.
  • Upgrade from 2.7.2 to 2.8.0 Failed and now /boot/efi/ empty

    30
    0 Votes
    30 Posts
    2k Views
    stephenw10S
    You can always just reinstall 2.7.2 which will give you the new larger sized EFI partition and then upgrade again from there.
  • Kernel Panic when Upgrading to 2.8.0 beta

    76
    0 Votes
    76 Posts
    13k Views
    stephenw10S
    The driver firmware loading issue is not fixed in 2.8.1. It's still broken upstream AFAIK. You will still need to apply one of the workarounds.
  • Issue with WAN speed negotiation after upgrading to 2.8

    13
    0 Votes
    13 Posts
    3k Views
    J
    @stephenw10 Yeah I am not sure what went wrong originally but glad it is working now!
  • Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare

    58
    0 Votes
    58 Posts
    9k Views
    stephenw10S
    Well that's not a bug if the gateways used were marked as down. That's the expected behaviour in 2.8.X. If the gateway being marked down is a change since 2.7.2 that could be a separate problem.
  • SG1100 to 24.11 failed / Error Code 137

    sg-1100 updates failed
    6
    0 Votes
    6 Posts
    3k Views
    stephenw10S
    Now you can upgrade to 25.07.1.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.