v2.6.0 to Plus. No address record.

Onecut

"Unable to check for updates" in Dashboard for some months on a Minnow Turbot Netgate appliance. I purchased it several years ago from Netgate.

I followed the 'Troubleshooting Upgrades' document to no avail.

[2.6.0-RELEASE][admin@pfSense.bmrr]/root: pkg install -y pfSense-upgrade    
Updating pfSense-core repository catalogue...
pkg: https://packages.netgate.com/pfSense_v2_6_0_amd64-core/meta.txz: No address record
repository pfSense-core has no meta file, using default settings
pkg: https://packages.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.pkg: No address record
pkg: https://packages.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.txz: No address record
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz: No address record
repository pfSense has no meta file, using default settings
pkg: https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg: No address record
pkg: https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz: No address record
Unable to update repository pfSense
Error updating repositories!
[2.6.0-RELEASE][admin@pfSense.bmrr]/root:

Regarding 'No Address Record' a "ping yahoo.com" would show if address resolution is working. I am a regular user as to expertise.

upgrade_log.latest.txt
upgrade_log.txt

Any help would be appreciated.

Onecut

Gertjan

@onecut said in v2.6.0 to Plus. No address record.:

upgrade_log.txt

These 3 lines tell me that your pfSense version (2.6.0 AMD) couldn't be compared to the current repo version : because "No address record" which means the scripts could reach the repo servers.

The first file is probably from the latest update, check the file date to see if this is true.

"No address record" says to me : pfSense itself has DNS issue.
The issue is mentioned and explained here https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html

Onecut

@gertjan said in v2.6.0 to Plus. No address record.:

The first file is probably from the latest update, check the file date to see if this is true.

[2.6.0-RELEASE][admin@pfSense.bmrr]/root: ls -l /conf/upgrade_log.*
-rw-r--r--  1 root  wheel  76717 Feb 16 04:14 /conf/upgrade_log.latest.txt
-rw-r--r--  1 root  wheel    258 Jul 14 01:42 /conf/upgrade_log.txt

I noted the 'Feb 16' date earlier but forgot to include in OP. Beg pardon.

[2.6.0-RELEASE][admin@pfSense.bmrr]/root: cat /conf/upgrade_log.txt 
>>> Updating repositories metadata... 
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.
Your system is up to date

@gertjan said in v2.6.0 to Plus. No address record.:

"No address record" says to me : pfSense itself has DNS issue.

Since DNS resolution worked from client PCs I did not comprehend 'itself'. But indeed, Diagnostics>DNSlookup failed. An adjustment in System/General Setup/DNS Server/DNS Resolution Behavior/(Default) has corrected 'pfsense DNS issue'.

Screenshot 2022-07-13 at 22-35-15 pfSense.bmrr - Status Dashboard.png

This solves the "No Address record" problem so I consider this thread closed. A new problem is why is 'pfsense Plus' not shown as a upgrade choice in General/Upgrade?

Thank you very much for your help.

Onecut