Those screenshots show relatively sane network settings, although I personally prefer not hardcoding public DNS servers on computers like that, better to put in the gateway IP as DNS - in your case 10.0.0.1.
Anyway, have you rebooted the server since changing the things outlined in the video?
Thank you @neofusion. I have rebooted since these settings and still the same result. Do you suggest; I get rid of the DNS server settings and just leave the Default Gateway to 10.0.0.1?
You can try it but it’s unlikely to resolve your issue.
Plex crashing and burning is one thing but the fact that TN updates also fail makes me ponder what the issue might be.
Could you try running this in a shell:
wget https://update-master.ixsystems.com/TrueNAS/trains.txt
And post the output here.
root@TrueNAS[~]# wget https://update-master.ixsystems.com/TrueNAS/trains.txt
–2013-01-02 10:16:54-- https://update-master.ixsystems.com/TrueNAS/trains.txt
Resolving update-master.ixsystems.com (update-master.ixsystems.com)… failed: Name does not resolve.
wget: unable to resolve
I removed the DNS Server and restarted to prior to issuing this command. I can add and repeat if needed
Well, for one, your date and time is incorrect.
Set your date and time to the correct values in the BIOS. Set it to GMT/UTC-time and make sure the time zone in TrueNAS is set as you would expect - in one of your images it’s set to Chicago.
In the shell, try ping 8.8.8.8
root@TrueNAS[~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=118 time=15.410 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=12.752 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=11.348 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=13.444 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=10.989 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=118 time=10.305 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=118 time=11.059 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=118 time=17.543 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=118 time=11.603 ms
Also, if you really mean removed, instead of replace with 10.0.0.1 like I suggested, you would have no DNS set up. You need something to act as a DNS server, don’t leave that field empty.
let me try this. thank you for your time @neofusion .
Well, at least you have network connectivity to google’s dns
That doesn’t show you the actual time and date, it just shows your the format it will display the time and date using.
The wget command showed you that the server actually thinks it’s 2013. You need to correct the BIOS time or else all secure connections will fail, since they are dependant on the client and server agreeing on what the date/time is.
But if you ran the wget command with no DNS server at all, it would have failed either way.
The date issue could be causing TLS to fail
(And being out by 10 years is too much of a delta for NTP to resolve)
Which could indicate a flat bios battery.
I agree, that is a likely factor.
No-brainer to replace the battery either way.
YAY. Thank you @neofusion @Stux !!!. I was able to change the time in BIOS and can connect to the update server. Also received meaningful response to the wget command.
NOT SUPPORTED AND WILL RESULT IN UNDEFINED BEHAVIOR AND MAY
RESULT IN SYSTEM FAILURE.
root@TrueNAS[~]# wget https://update-master.ixsystems.com/TrueNAS/trains.txt
–2024-11-26 09:14:43-- https://update-master.ixsystems.com/TrueNAS/trains.txt
Resolving update-master.ixsystems.com (update-master.ixsystems.com)… 136.0.77.2
Connecting to update-master.ixsystems.com (update-master.ixsystems.com)|136.0.77.2|:443… connected.
HTTP request sent, awaiting response… 200 OK
Now Plex is still an issue as I cannot get to the admin portal yet…
I am updating Plex plugin as we speak…
Good to see, still curious time though, is it really 09:14 in Chicago right now?
Anyhow, the Plex issue is out of my league. Perhaps someone else can assist you with that.
Actually it is 15:22 PM in Chicago, not sure why it is 09:14 now in the shell output!
