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

[J_C]

i got this error when trying to update freenas scale "451, message='', url=URL('https://update.freenas.org/scale/trains.json'): Automatic update check failed. Please check system network settings."

I tried almost everything.
The 451 error means Unavailable For Legal Reasons but since i live in Belgium that should be an issue? (ISP: Telenet)

 

[joe28753]

I got this same error today as well. I'm in the US. I thought it had something to do with our daylight savings time switch and NTP service. When I was googling, there were similar cases where people resolved it by restarting NTP service. But my TrueNAS is now displaying the correct time and can ping the NTP server fine. Not sure why it can't check for updates. I'll just wait and see.

 

[BCB57]

Also trying to update today and seeing exact same issue ... glad I found this thread! Guess I'll just try again tomorrow. :)

 

[brymck]

Same issue.

 

[cincibcat9]

Same here.

 

[MuffinTop]

Same issue here. Was trying to update from 22.12.0 to 22.12.1.

Manual update seems to have worked though.

 

[Oceanstorms12]

Successfully upgraded to TrueNAS Code 13.0.-U4 and now get 451 errors when checking for update.

 

[lyricnz]

I am also having this today. I understand that daylight savings ended some places today, maybe it's related.

Even "curl" has the same problem when passing the user-agent

```
admin@truenas[~]$ curl -s -v https://update.freenas.org/scale/trains.json 2>&1 | grep HTTP/2 * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 > GET /scale/trains.json HTTP/2 < HTTP/2 200

admin@truenas[~]$ curl -s -v -A 'Python/3.9 aiohttp/3.7.4' https://update.freenas.org/scale/trains.json 2>&1 | grep HTTP/2 * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 > GET /scale/trains.json HTTP/2 < HTTP/2 451
```

 

[MarkF7]

I'm running TrueNAS CORE 13.0-U3.1 and I *used* to see the automatic update available (for the first few days?) but now I get the same 451 error. Odd because the error mentions TrueNAS Scale even though I'm running CORE. Was going to try rebooting to see if it's fixed; will update if that works.

 

[andrema2]

I'm running TrueNAS-13.0-U4 and I'm seeing the same thing. It doesn't seem a problem with the network. I wonder if the download server isn't having a problem.

Below the result of curl -s -v https://update.freenas.org/scale/trains.json

* Trying 68.70.196.128:443...
* Connected to update.freenas.org (68.70.196.128) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* CAfile: /usr/local/share/certs/ca-root-nss.crt
* CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
* subject: CN=update-master.ixsystems.com
* start date: Oct 20 07:29:18 2022 GMT
* expire date: Oct 18 20:46:12 2023 GMT
* subjectAltName: host "update.freenas.org" matched cert's "update.freenas.org"
* issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* h2h3 [:method: GET]
* h2h3 [:path: /scale/trains.json]
* h2h3 [:scheme: https]
* h2h3 [:authority: update.freenas.org]
* h2h3 [user-agent: curl/7.85.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x8012d6800)
> GET /scale/trains.json HTTP/2
> Host: update.freenas.org
> user-agent: curl/7.85.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200
< server: keycdn-engine
< date: Mon, 13 Mar 2023 15:19:04 GMT
< content-type: application/json
< content-length: 869
< last-modified: Thu, 15 Dec 2022 16:10:18 GMT
< vary: Accept-Encoding
< etag: "639b46ea-365"
< cache-control: max-age=604800
< access-control-allow-headers: *
< access-control-allow-methods: *
< expires: Mon, 20 Mar 2023 15:19:04 GMT
< x-edge-location: usny
< access-control-allow-origin: *
< accept-ranges: bytes
<
{
"trains": {
"TrueNAS-SCALE-Angelfish": {
"description": "TrueNAS SCALE Angelfish [release]"
},
"TrueNAS-SCALE-Bluefin-BETA": {
"description": "TrueNAS SCALE Bluefin BETA"
},
"TrueNAS-SCALE-Bluefin-RC": {
"description": "TrueNAS SCALE Bluefin RC"
},
"TrueNAS-SCALE-Bluefin": {
"description": "TrueNAS SCALE Bluefin [release]"
}
},
"trains_redirection": {
"TrueNAS-SCALE-MASTER": "TrueNAS-SCALE-Angelfish-Nightlies",
"TrueNAS-SCALE-Angelfish-PRERELEASE": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Angelfish-BETA": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Angelfish-RC": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Angelfish-RC-To-Release": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Bluefin-BETA": "TrueNAS-SCALE-Bluefin",
"TrueNAS-SCALE-Bluefin-RC": "TrueNAS-SCALE-Bluefin"
}
}
* Connection #0 to host update.freenas.org left intact

My time seems correct

date
Mon Mar 13 12:24:36 -03 2023

 

[danb35]

@morganL? @Kris Moore? Something seems to be borked with your update servers.

 

[MarkF7]

I'm running TrueNAS CORE 13.0-U3.1 and I *used* to see the automatic update available (for the first few days?) but now I get the same 451 error. Odd because the error mentions TrueNAS Scale even though I'm running CORE. Was going to try rebooting to see if it's fixed; will update if that works.

Rebooting didn't help. When I go to System->Update, the "Apply Pending Update" button is clickable and wants my confirmation before updating. I _assume_ it will install U4, but I'm happy to wait until this situation is sorted first :)

 

[BCB57]

Still same issue this afternoon... will check here periodically for any news.

 

[HoneyBadger]

Odd, I've just successfully fetched the U3.1 -> U4 and 22.12.0 -> 22.12.1 updates without incident.

Based on the varied location of users in here reporting, it doesn't seem to be a geographically specific issue either.

Appreciate the heads-up on this!

 

[skoop]

Same issue

 

[youghta]

Same here.

 

[chilexican]

same here.. started yesterday as noted by others. has to be related to the daylight savings time changing..

 

[MarkF7]

Is it safe to "Apply Pending Update" to upgrade TrueNAS CORE from 13.0-U3.1 -> U4? I'm hoping that there wasn't an issue with the update image being compromised (either corrupted or by something malicious)

 

[wanderer2]

If you pull the file down, it looks like it only has updates for Truenas Scale in it, and not updates for Truenas Core.

{
"trains": {
"TrueNAS-SCALE-Angelfish": {
"description": "TrueNAS SCALE Angelfish [release]"
},
"TrueNAS-SCALE-Bluefin-BETA": {
"description": "TrueNAS SCALE Bluefin BETA"
},
"TrueNAS-SCALE-Bluefin-RC": {
"description": "TrueNAS SCALE Bluefin RC"
},
"TrueNAS-SCALE-Bluefin": {
"description": "TrueNAS SCALE Bluefin [release]"
}
},
"trains_redirection": {
"TrueNAS-SCALE-MASTER": "TrueNAS-SCALE-Angelfish-Nightlies",
"TrueNAS-SCALE-Angelfish-PRERELEASE": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Angelfish-BETA": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Angelfish-RC": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Angelfish-RC-To-Release": "TrueNAS-SCALE-Angelfish",
"TrueNAS-SCALE-Bluefin-BETA": "TrueNAS-SCALE-Bluefin",
"TrueNAS-SCALE-Bluefin-RC": "TrueNAS-SCALE-Bluefin"
}
}

Guess we are just going to have to wait this one out.

 

[Samuel Tai]

I've reported this issue to it@ixsystems.com. This looks like a faulty CDN publish.