<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Upgrade 2.4.3 -&gt; 2.4.3_1 - no download?]]></title><description><![CDATA[<p dir="auto">Trying to upgrade but both WebUI and Console (13) sat there saying "upgrading" but process seemed stalled. Followed blog entry and see this:</p>
<pre><code>[2.4.3-RELEASE][admin@senser.home]/root: pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
pkg-static: Impossible to open /var/cache/pkg: No such file or directory
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.
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pfSense-upgrade: 0.42 -&gt; 0.44 [pfSense]

Installed packages to be REINSTALLED:
        pkg-1.10.3_1 [pfSense]
        pfSense-repo-2.4.3_2 [pfSense]

Number of packages to be upgraded: 1
Number of packages to be reinstalled: 2

3 MiB to be downloaded.

</code></pre>
<p dir="auto">Unchanged since about 10mins. Is the pfSense upgrade server down or what am I missing here? Syslog shows no errors, everything else seems to be working ok.</p>
<p dir="auto">Thanks!</p>
<p dir="auto">[Edit] I had the repo config rewritten btw (changed to testing, checked for update, returned to stable). System sat there showing the above for another 20mins before I hit ^C. Rebooted and see 2.4.3 installed and 2.4.3_1 available as before. Guess I'll just wait for 2.4.3_2 ;)</p>
]]></description><link>https://forum.netgate.com/topic/130910/upgrade-2-4-3-2-4-3_1-no-download</link><generator>RSS for Node</generator><lastBuildDate>Mon, 20 Apr 2026 12:07:35 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/130910.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 15 May 2018 16:35:08 GMT</pubDate><ttl>60</ttl></channel></rss>