<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>unable to check for updates &#8211; 21點情報網</title>
	<atom:link href="https://ailog.tw/lifelog/tag/unable-to-check-for-updates/feed/" rel="self" type="application/rss+xml" />
	<link>https://ailog.tw/lifelog</link>
	<description></description>
	<lastBuildDate>Wed, 16 Jul 2025 15:58:26 +0000</lastBuildDate>
	<language>zh-TW</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>
	<item>
		<title>pfsense 2.5.X線上升級時出現「unable to check for updates」</title>
		<link>https://ailog.tw/lifelog/2025/07/16/pfsense-2-5-x-upgrade/</link>
		
		<dc:creator><![CDATA[blackjack]]></dc:creator>
		<pubDate>Wed, 16 Jul 2025 15:56:38 +0000</pubDate>
				<category><![CDATA[3C資訊]]></category>
		<category><![CDATA[Firewall]]></category>
		<category><![CDATA[Pfsense]]></category>
		<category><![CDATA[unable to check for updates]]></category>
		<guid isPermaLink="false">https://ailog.tw/lifelog/?p=18052</guid>

					<description><![CDATA[最近遇到一台遠距的pfsense防火牆版本是2.5.1，想更新作業系統版本卻一直出現「unable to ch &#8230; <p class="link-more"><a href="https://ailog.tw/lifelog/2025/07/16/pfsense-2-5-x-upgrade/" class="more-link">閱讀全文<span class="screen-reader-text">〈pfsense 2.5.X線上升級時出現「unable to check for updates」〉</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>最近遇到一台遠距的pfsense防火牆版本是2.5.1，想更新作業系統版本卻一直出現「unable to check for updates」，該如何排除呢?跟小編一起來排查問題吧!</p>
<p><span id="more-18052"></span></p>
<p>一、透過SSH登入</p>
<p>二、手動更新<br />
<span style="font-family: verdana, geneva; font-size: 1rem;">指令語法：</span></p>
<pre>pkg-static update -f</pre>
<p>會出現大量的告警訊息(看起來是憑證失效了)</p>
<pre>Certificate verification failed for /CN=*.netgate.com
34369253376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/local/poudriere/jails/pfSense_v2_5_1_amd64/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /CN=*.netgate.com
34369253376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/local/poudriere/jails/pfSense_v2_5_1_amd64/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /CN=*.netgate.com
34369253376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/local/poudriere/jails/pfSense_v2_5_1_amd64/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /CN=*.netgate.com
34369253376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/local/poudriere/jails/pfSense_v2_5_1_amd64/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /CN=*.netgate.com</pre>
<p><img fetchpriority="high" decoding="async" class="alignnone wp-image-18055 size-full" src="https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-001.png" alt="" width="1534" height="419" srcset="https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-001.png 1534w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-001-300x82.png 300w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-001-1024x280.png 1024w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-001-768x210.png 768w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></p>
<p><img decoding="async" class="alignnone wp-image-18058 size-full" src="https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-003.webp" alt="" width="512" height="512" srcset="https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-003.webp 512w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-003-300x300.webp 300w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-003-150x150.webp 150w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-003-100x100.webp 100w" sizes="(max-width: 512px) 100vw, 512px" /><br />
緩解錯誤訊息的心情，本圖片為示意圖，與本文章內容無關。</p>
<p>三、手動編輯更新檔案<br />
<span style="font-family: verdana, geneva; font-size: 1rem;">指令語法：</span></p>
<pre>vi /usr/local/etc/pkg/repos/pfSense.conf</pre>
<p>※將檔案內的http<span style="color: #ff0000;">s</span>變更為http<br />
<img decoding="async" class="alignnone wp-image-18054 size-full" src="https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-002.png" alt="" width="1027" height="502" srcset="https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-002.png 1027w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-002-300x147.png 300w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-002-1024x501.png 1024w, https://ailog.tw/lifelog/wp-content/uploads/2025/07/pfsense-002-768x375.png 768w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></p>
<p>四、透過web UI進行作業系統更新</p>
<p><span style="color: #ff0000;">※如果還是無法順利進行版本更新檢查，就反覆進行第三跟第四步驟。</span></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
