Hi
I’m seeing this error when updating on an otherwise well running NS8.
There is a core update, and also a NextCloud update available.
Other NS8 servers have not displayed this error.
The above is shown when trying to update the core.
Trying to update Nextcloud shows something almost identical:
→ At least the error seems the same, if not the title. But I’m not a core coder… 
The current running core:
Any ideas?
My 2 cents
Andy
core, nextcloud and other app updates worked fine here on a Rocky test VM.
Your log excerpt shows a certificate error, but don’t know the real meaning (so answer not of much help). Maybe a transitory external issue with docker registry / ghcr.io (I’d expect other message for rate limit)
Core, nextcloud and other app updates worked fine here on about 8 Debian Prod VMs.
Only one barfed…
And this seems strange…
My 2 cents
Andy
online search results (similar but not same error) talk about updating system’s certificate store or the need to restart podman/docker after system’s certificate store update… but who knows…
There were no issues on my NS8 Debians.
You could check if the pull works manually:
podman pull ghcr.io/nethserver/core:3.3.1
It seems the NS8 sees it’s own self-signed traefik certificate instead of the ghcr.io one. Weird.
Could it be that ghcr.io is resolved to 127.0.0.1 because of some DNS list threats/ad blocker?
nslookup ghcr.io
Please also check if you get the right certificate from NS8 view.
openssl s_client -connect ghcr.io:443 </dev/null
The result should contain:
subject=CN = *.ghcr.io
issuer=C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited, CN = Sectigo RSA Domain Validation Secure Server CA
Hi @mrmarkuz
And thanks for the suggestions. I will try a little later, that particular system is not only offsite, but also another country. But I can access / try it later today.
Feedback coming.
My other NS8-Debians (8) had no issues…
My 2 cents
Andy
After the last update (Core, Mail, NextCloud), NextCloud is still in maintenance mode.
You know the drill…
Hi @Andy_Wismer,
will the core update only be offered to a selected audience? Core 3.3.0 is running here, and there is no new offer in the software center.
I think it’s because of subscription.
I’m not on subscription and got 3.3.1
Subscription servers get new versions later when they’re tested by community.
Yes, that will be the case. Then I’ve been lucky, so to speak. 
I must confess that I had misunderstood it.
Hi @mrmarkuz
I can confirm the manual pull worked without issues.
Before doing the manual pull, I tested both questions, and both returned correct…
nslookup ghcr.io
Server: 192.168.45.29
Address: 192.168.45.29#53
Non-authoritative answer:
Name: ghcr.io
Address: 140.82.121.33
openssl s_client -connect ghcr.io:443 </dev/null
openssl s_client -connect ghcr.io:443 </dev/null
CONNECTED(00000003)
depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority
verify return:1
(shortened)
Result: Both Core and NextCloud have updated correctly.
I still needed to triger the update from the Web-GUI, but ran through with no issues.
I do wonder why that strange error cropped up?
It could have been due to a DNS issue the day earlier (Provider related)…
My 2 cents
Andy