Failed to sync TRUENAS catalog: [EFAULT] Failed to clone 'https://github.com/truenas/apps' repository at '/mnt/.ix-apps/truenas_catalog' destination: [EFAULT] Failed to clone 'https://github.com/truenas/apps' repository at '/mnt/.ix-apps/truenas_catalog' destination: Cloning into '
I’ve got the failed to sync truenas catalogue error. I’ve seen many other threads of this, most common was BIOS clock out of sync, have checked that, changed to local time, then back to UTC so it was correct the whole time.
Secondly people mention DNS settings. I’ve never had DNS issues before, my ISP is not know for blocking things, and it had been working for a few years.
Regardless, updated DNS to cloudflare and google, both on NAS and router, to help. There was however one moment when it briefly worked, let me connect to the apps services, then after a reboot broke with the same settings.
Is there anything else someone can suggest as I’m quite stuck. Have also tried a rollback in case it was app settings but still didn’t help.
The “briefly worked then failed again” part is the key clue. Since DNS and clock are ruled out, the most likely causes are either a stale partial clone blocking the retry, or a network-level issue with large HTTPS transfers.
First thing to try: SSH into TrueNAS and remove the failed partial clone so it starts fresh: rm -rf /mnt/.ix-apps/truenas_catalog — then trigger a catalog sync again from the UI. Git clones fail silently when a previous partial clone left behind a corrupted directory, and TrueNAS does not always clean that up automatically.
If that does not fix it, check from the TrueNAS shell whether GitHub is actually reachable: curl -I https://github.com/truenas/apps — if that times out or returns errors then something between your NAS and GitHub is blocking.
Also worth checking: if you are on a PPPoE connection your MTU might be 1492 instead of 1500, and large git clones can stall on path MTU discovery issues. You can test with: ping -M do -s 1472 github.com — if that fails but smaller packets work, then MTU is your problem and you need to clamp it on your NAS interface or router.
Thanks for that. I did notice on the time that it did work, the Discover apps page was populated, now that its not working that page always fails to load content, as I assume its the same github page.
Tried clearing the clone, but still can’t connect.
Curl isn’t working, it fails with below.
curl: (35) Recv failure: Connection reset by peer
MTU was 1500 on router and NAS, tried lowering it, but testing looks like it wont ping at any MTU size except all the way down to 10.
have also tried turning off TSO, GSO / GRO & checksum offloading & disabled ipv6.
I can -curl from my windows PC which makes me think its a truenas network setting issue? But I’m unsure of what else to change. Have reset network adapter also
Connection reset by peer on curl to GitHub is telling — that is not a DNS or MTU issue, it means something in the network path is actively terminating the TLS connection. Most likely causes at this point: your ISP is doing deep packet inspection and interfering with certain HTTPS connections, or there is a transparent proxy or firewall device between your NAS and the internet that does not like the TLS handshake to GitHub.
Try this from the NAS shell to narrow it down: curl -v https://github.com/truenas/apps 2>&1 | head -30 — the verbose output will show exactly where in the TLS handshake the reset happens.
Also try connecting through a different path: curl --connect-to github.com:443:140.82.121.3:443 https://github.com/truenas/apps — that bypasses DNS and goes directly to a GitHub IP, which rules out any DNS-level interference.
If that also fails with connection reset, try setting up a simple VPN or SSH tunnel to bypass whatever is blocking. The fact that it worked briefly and then stopped again points to an intermittent filtering system.
Relax and wait a minute. On both my hosts, in the apps list, all the apps want an update. Apps stopped or running, doesn’t matter, everything is flagged.
Recently I think this happens on their side when the framework gets an update, all the apps get a point number boost to keep them in sync with upcoming changes. So this may just be bad timing on your part and they freeze the repos while this thing propagates.
I could be wrong but it sure seems like the timing matches.
Installed a fresh version on a VM on my windows machine, can connect to apps ok. So clearly tied to the machine. But this rules out packet inspection from ISP and DNS issues?
Updated Truenas to 25.10.2.1, and factory settings, same error. Also just to check installed inside a VM in on the Truenas hardware and of course same error.
Also tried removing Static IP from the truenas machine, so different IP, still can’t connect.
Tried diagnosing with AI, came to conclusion TLS traffic is being affected somehow, tried a new cable, new router port, various network settings in truenas and the network controller. Haven’t tried a new network controller or another router, am slightly dubious it would be the router as it manages to connect finde from Windows VM
Not sure what else to try here if anyone has any other suggestions.
