Problem upgrade from 25.11 to 25.11.1 - Netgate 4200

[Airone 0]

I received this Netgate 4200 two days ago and am trying to upgrade the firmware from 25.11 to 25.11.1 (as suggested by the system), but after about 15 minutes I am still stuck on the first fetch even though it is only 218 MB and the processing time up to this point has been very short.

Proceed with upgrade? (y/N) y
>>> Renaming current boot environment from default to default_20260827163541...done.
>>> Cloning current boot environment default_20260827163541...done.
>>> Removing vital flag from php84...done.
>>> Upgrading packages in cloned boot environment default...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (200 candidates): .......... done
Processing candidates (200 candidates): . done
The following 11 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        openvpn: 2.6.16 -> 2.6.20 [pfSense]
        pfSense: 25.11 -> 25.11.1 [pfSense]
        pfSense-base: 25.11 -> 25.11.1 [pfSense-core]
        pfSense-boot: 25.11 -> 25.11.1 [pfSense-core]
        pfSense-default-config-serial: 25.11 -> 25.11.1 [pfSense]
        pfSense-kernel-pfSense: 25.11 -> 25.11.1 [pfSense-core]
        pfSense-pkg-Nexus: 25.11 -> 25.11.1_1 [pfSense]
        pfSense-pkg-WireGuard: 0.2.11 -> 0.2.11_1 [pfSense]
        pfSense-system: 25.11.1600001 -> 25.11.1600002 [pfSense]
        php84-pfSense-module: 25.11 -> 25.11.1 [pfSense]
        strongswan: 6.0.3 -> 6.0.6 [pfSense]

Number of packages to be upgraded: 11

The process will require 3 MiB more space.
218 MiB to be downloaded.
[1/11] Fetching pfSense-base-25.11.1.pkg: ....Proceed with upgrade? (y/N) y
>>> Renaming current boot environment from default to default_20260827163541...done.
>>> Cloning current boot environment default_20260827163541...done.
>>> Removing vital flag from php84...done.
>>> Upgrading packages in cloned boot environment default...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (200 candidates): .......... done
Processing candidates (200 candidates): . done
The following 11 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        openvpn: 2.6.16 -> 2.6.20 [pfSense]
        pfSense: 25.11 -> 25.11.1 [pfSense]
        pfSense-base: 25.11 -> 25.11.1 [pfSense-core]
        pfSense-boot: 25.11 -> 25.11.1 [pfSense-core]
        pfSense-default-config-serial: 25.11 -> 25.11.1 [pfSense]
        pfSense-kernel-pfSense: 25.11 -> 25.11.1 [pfSense-core]
        pfSense-pkg-Nexus: 25.11 -> 25.11.1_1 [pfSense]
        pfSense-pkg-WireGuard: 0.2.11 -> 0.2.11_1 [pfSense]
        pfSense-system: 25.11.1600001 -> 25.11.1600002 [pfSense]
        php84-pfSense-module: 25.11 -> 25.11.1 [pfSense]
        strongswan: 6.0.3 -> 6.0.6 [pfSense]

Number of packages to be upgraded: 11

The process will require 3 MiB more space.
218 MiB to be downloaded.
[1/11] Fetching pfSense-base-25.11.1.pkg: ....

The speed test gave me 900/200, so I don't think it's a speed issue. Can anyone tell me what the problem might be?

[stephenw10]

Hmm, I'm not aware of any issue there. Possibly an IPv6 issue?

If you run the upgrade with: pfSense-upgrade -d you will get more debug output.

[stephenw10]

Oh it actually looks like there was a routing issue affecting our repo hosting that may well have been in play. Looks to be resolved now.

[Airone 0]

Hello @stephenw10 , thank you for reply.

All IPv6 settings are disabled, and I've already tried SSH, but nothing changed. Keep in mind that the first fetch (the last one in the code I posted) has been running for about an hour (218 MB??).

[stephenw10]

Mmm, I would stop and restart it with -d so you can see what it's trying to do.

It may have got stuck on whatever routing issue was happening an hour a ago. There's a good chance it will just work normally if you restart it now.

[Airone 0]

I ran it now, and it froze on the first fetch. I'll let it run and see how long it takes, assuming it doesn't time out.

[Airone 0]

About 20 minutes in SSH... and counting .

[Airone 0]

23 minutes.

[Airone 0]

32 minutes.

[Airone 0]

50 minutes... and I'll stop with the screenshots.

[stephenw10]

Hmm, so it's going just very slowly. Did it eventually finish?

[Airone 0]

The whole thing took about an hour and ten minutes.

[stephenw10]

Huh. But it did eventually complete without errors?

[Airone 0]

Yes, no errors, but too long for a few MB.