I recently updated from TrueNAS Core to Scale to get into Apps setups rather than running my Minecraft server and plex server on a VM in Core. I first updated to Cobia in the GUI, and everything was working well, I could see the apps I wanted to install. Then after a restart I was unable to connect to see any apps, and starting an apps catalog refresh would simply never finish. After hours of troubleshooting to no avail I decided to jump to Electric Eel and start over as I didn’t have that much data on the drives anyway.
Today I finished the install and SMB share setup in Electric Eel, and spent another 4 hours troubleshooting networking issues:
I can Ping google and github
I have also verfied the Date and Time stamp.
But, apps don’t sync, fails to manually clone in shell also.
Furthermore, the GUI Update feature is also not connecting to the servers:
Attempting to Unset and Reset the Pool assigned to apps gets stuck in the Unset pool process docker.update step ‘applying requested configuration’.
The only thing I have not checked is Firewall settings, but I know that my AT&T internet router is using the default config apart from some Port Forwarding rules.
Main Error:
Critical
Failed to sync TRUENAS catalog: [EFAULT] Failed to clone ‘insert link to github here (I couldn’t post the link)’ repository at ‘/mnt/.ix-apps/truenas_catalog’ destination: [EFAULT] Failed to clone ‘(CAN’T POST LINKS’ repository at ‘/mnt/.ix-apps/truenas_catalog’ destination: Cloning into ‘/mnt/.ix-apps/truenas_catalog’…
I just wanted to setup one machine that could host multiple Minecraft servers using MineOS and Plex and a file share…
Any advice would be helpful
I have setup a Static Ip Address by disabling DHCP and setting the alias in the Interfaces section. Not sure If I need to setup the “Static Routes” but I didn’t understand how to define the Destination when I went to add a static route.
How did you do this? The time should be set to the time in UTC (18:38 at the time of writing) and then (optionally) adjusted using the time zone settings in TrueNAS. Anything else is invalid.
Don’t touch the static routes, that’s only for advanced usage.
To have a working static IP configuration, you need to pick unique IP that isn’t used for anything else in your network. You also need to specify an address for your gateway and at least one DNS. Typically, in a home environment, the IP of your router will work for gateway and DNS.
Example configuration:
TrueNAS IP: 192.168.0.10/24
Gateway: 192.168.0.1
DNS1: 192.168.0.1
Adapt the network range to whatever is used in your local network.
Since you don’t specifically say it, did you verify that the time is set to the time in UTC in your BIOS?
Running “date” in a shell doesn’t necessarily show you that.
Edit: What’s the output if you run this command in the shell, simulating trying to reach the github page: wget --verbose https://github.com/truenas/apps -O /dev/null
Here’s the output from the shell.
I can’t get into the BIOS to check the Date until I’m home this afternoon. Thank you again for your help troubleshooting.
A possible reason for that is the date/time issue I mentioned previously. SSL connections require you and the server you’re trying to connect to both agree on what date and time it is.
Result:
Last login: Sat Feb 15 16:32:42 EST 2025 on pts/0
truenas_admin@truenas[~]$ timedatectl
Local time: Sat 2025-02-15 16:56:56 EST
Universal time: Sat 2025-02-15 21:56:56 UTC
RTC time: Sat 2025-02-15 21:56:56
Time zone: America/New_York (EST, -0500)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
truenas_admin@truenas[~]$ openssl s_client -connect github.com:443 < /dev/null
CONNECTED(00000003)
Still waiting on the this command to finish resolving.
This should be essentially immediate, as in a few milliseconds.
That to me suggests you have something funky going on in your network (or possibly your ISP).
But I have reached the end of the road, I can’t help you, sorry.
SSL handshake has read 0 bytes and written 316 bytes
Verification: OK
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
I do have a mesh wifi system, but the server is plugged into the main router from AT&T, the 5Gig port. I have 1 Gig AT&T fiber. The only thing that I have changed on the network is the the Port Forwarding rules for minecraft server I was running before. Sunshine for Game streaming and Plex server on the same minecraft server, a windows machine I have since dismantled.
My googling that error code (110) leads me to believe:
You either have MTU issues, if there’s a VPN involved somewhere.
Or your firewall/port forwarding is set too aggressively, catching the SSL responses. Resulting in those replies not reaching TrueNAS as intended, hence a 15 minute timeout while your server waits for a reply.
I believe that you are correct. I am going to undo some settings on “Smart Home Manager” app from AT&T to see if that fixes my issue. Last night I install Ubuntu to see if I could get that working on the machine, and I am unable to access the web at all for anything. When I open a browser I am prompted with an AT&T screen that says this activity has been blocked due to parental controls or due to amount of activity, so I’m thinking that when I was playing around with the AT&T app I screwed something up and blocked connections from this machine somehow. Hopefully this will fix my issue and I’ll go back to TrueNAS Scale if this fixes my connectivity issue with Ubuntu. Thank you for your help!!! @neofusion
Thank you for continually pointing me to the ISP. I think AT&T has something against linux Distros because both Ubuntu desktop and Truenas Scale all versions get blocked in the “Smart Home Manager” app. In the app go to users, the bottom middle button on android, select the hostname of your device and click unblock device… I hope this helps anyone else struggling with a similar issue. Thank you @neofusion for your continued support I gave you the solution, because any kind of ISP related blockage would cause this issue and pointing there is more helpful than what specifically helped me, though it’s important to document both. Thanks!
