FreeNAS Can't Check for Updates - Resolved

rfielder

Explorer
Joined
Jun 18, 2019
Messages
81
Both of my FreeNAS boxes are unable to check for updates. This is the error message:
HTTPSConnectionPool(host='update-master.ixsystems.com', port=443): Max retries exceeded with url: /FreeNAS/trains.txt (Caused by NewConnectionError('urllib3.connection.VerifiedHTTPSConnection object at 0x81c38cfd0: Failed to establish a new connection: [Errno 8] hostname nor servname provided, or not known',)): Automatic update check failed. Please check system network settings

Both boxes are set up with static IP addresses. That is the only change made to the networking, so I assume this has something to do with the error.

One box uses interface igb0 at 192.168.0.160/24, and the other has igb1 at 192.168.0.150/24.\

There are no problems accessing either box from any PC on my network.

Can someone advise what is wrong? Or do you need more information? The specs for the two boxes should be in my signature.

Thanks in advance!
 

rfielder

Explorer
Joined
Jun 18, 2019
Messages
81
Turns out I had left the Gateway and Nameserver fields blank.

Once these fields were updated, the updates began updating.

Yay!
 

rfielder

Explorer
Joined
Jun 18, 2019
Messages
81
Next question:

After filling in the Gateway and Nameserver fields, both boxes updated to 11.2-U7.

The systems now report that no updates are available. However, 11.3 has been released.

Why are my systems reporting that no updates are available?

Thanks in advance!
 

rfielder

Explorer
Joined
Jun 18, 2019
Messages
81
you need to select the 11.3 train
Where do I select this?

The list for the Train box includes:
FreeNAS - 11 - Nightlies
FreeNAS - 11 - Nightlies SDK
FreeNAS - 11.2 - Stable

There is no 11.3 Train.
 

joeld79

Dabbler
Joined
Apr 15, 2018
Messages
13
right there
yeet.png
 

rfielder

Explorer
Joined
Jun 18, 2019
Messages
81
That does not appear on either of my systems. Both systems are running 11.2-U7.
 

rfielder

Explorer
Joined
Jun 18, 2019
Messages
81
Success!

Booted into the legacy web interface, and 11.3 was visible under Update.

Used this approach on both boxes, and both are now running 11.3!!
 
Top