Unable to connect to url https://update-master.ixsystems.com/TrueNAS/trains.txt: Automatic update check failed. Please check system network settings.

cincibcat9

Dabbler
Joined
May 1, 2014
Messages
12
Screenshot 2023-03-12 at 3.46.29 PM.png




After changing my network global config to the pic above, i get the following error:

451, message='', url=URL('https://update.freenas.org/scale/trains.json'): Automatic update check failed. Please check system network settings.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,464
Seems like there might be a broader issue:
 

vpvitor

Cadet
Joined
Apr 18, 2023
Messages
1
Apenas Acrescentei novos servidores NTP e pra mim esse problema foi corrigido

[via Google Translate]
Just added new NTP servers and for me this problem is fixed

[Moderator Note]
Please post in English in the main forums. It is untenable to support multiple languages in the main forums; there is a dedicated subforum for Portugese over in the International forums. Thank you.
 
Last edited by a moderator:

Hdez

Cadet
Joined
Jun 22, 2020
Messages
6
View attachment 64645



After changing my network global config to the pic above, i get the following error:

451, message='', url=URL('https://update.freenas.org/scale/trains.json'): Automatic update check failed. Please check system network settings.
Hi, I was having this issue and was getting the same exact error. I went into the Network/Global Configuration and changed the Nameserver1 to the same IP address as my Default Gateway. This fixed my problem. In your case, change it to 192.168.1.1 if this is really your Default Gateway IP address. Good luck!
 

jinlsui

Dabbler
Joined
Mar 28, 2021
Messages
10
Hi, I was having this issue and was getting the same exact error. I went into the Network/Global Configuration and changed the Nameserver1 to the same IP address as my Default Gateway. This fixed my problem. In your case, change it to 192.168.1.1 if this is really your Default Gateway IP address. Good luck!
I had exactly the same problem. It turned out that I had an IP address typo on the NameServer1. After fixing it, everything started to work as expected.
 
Top