From the begining...
My TrueNAS and Plex were working fine.
Today, when i try to open the Plex web on my computer, by the IP:PORT/web, when i try to access my local media, a "not authorized / you do not have access to this server" error message prompt, i checked twice if i'm logged to the correct account (even if I never log out of this account), try to google a solution, and the only way i find out was to reinstal my plex enterely.
So i screenshot all the plex network configuration & mounts, and procced with the uninstal of the plugin.
After remove it, i try to reinstall with the same network configuration that was before (same IP, same vnet, default interface, etc...), and opened two CMD in my computer, one performing ping test to the server IP, and the other to the PLEX IP (192.168.100.250 and 192.168.100.252 respectively, my router is set to 192.168.100.1, the DHCP is an 192.168.100.0/24).
After a minute or so on 50% "- ffmpeg", the CMD performing the ping test to 192.168.100.250 (the server) lost 2~4 packages, and return pinging normaly, and so 192.168.100.252 was able to succesfuly ping. So the instalation procced, and when it's reach 75% "- ffmpeg" again, the CMD isn't able to ping both of the IPs, after 2~4 packages loss again, the 192.168.100.250 return, but 192.168.100.252 don't, and the following error message prompt.
i'm aware of the DNS / Gateway manuly set up when not using DHCP on the server, and the configuration ware setup before this (so the plex was up and running). But i revised all the network configuration, tries to change it to DHCP and instal the plugin in DHCP mode, but it's fail in 50% "- ffmpeg" with the following DHCP error message (that I already expected).
So i procced to redo all the network configuration on the server (set the IP to 192.168.100.250, set the DNS to all combinations possible between 8.8.8.8, 8.8.4.4, 1.1.1.1, 208.67.222.222, 208.67.220.220 and 192.168.100.1 (my router), set the IPv4 Default Gateway to 192.168.100.1), but even after this reconfiguration, i wasn't able to setup the plugin (same "coult not resolve host: github.com" error).
I tried to ping to google.com and github.com in the shell, both successfully as follow
After this, i give up the plugin instalation and procced to creat a jail and do it manually, and for my surprise, when i try to add a jail, the follow error prompt appear...
After google the log, some threads on this forum said that this is a certificate error (but the threads were for FreeNAS 11, and i'm not able to perform the shell commands the threads sugest - and I was afraid of ending up bricking my server with FreeNAS commands on TrueNAS). One of the solutions sugests a system update, my version was the 13.0 U3, and the newest version was the 13.0 U5.1, i doubt this was solve the problem, but it's cost nothing, and i go to the automatic update and...
Another connection error, i try to ping this URL, and it was pinging normally as was google and github...
So i tried the manual update, it worked fine, my system is now on the 13.0 U5.1, and its solved nothing, all previous errors continued in the same way...
And i've checked my certificate before and after the update, and it's the same, with the expiring date to "2024-05-05"...
Anyone has any idea if i'm doing anything wrong?
Any suggest for solving this?
Thanks in advance for anyone who spends some minutes reading and trying to understand my problem, since now i apollogies for any english miswriting, it's not my native language.
PS.: Yes, i've try to restart the server, a lot of times, since the plex prompt the first "not authorized" error.
PS².: My home router was instaled by the provides, it's a HG8245W5-6T.
My TrueNAS and Plex were working fine.
Today, when i try to open the Plex web on my computer, by the IP:PORT/web, when i try to access my local media, a "not authorized / you do not have access to this server" error message prompt, i checked twice if i'm logged to the correct account (even if I never log out of this account), try to google a solution, and the only way i find out was to reinstal my plex enterely.
So i screenshot all the plex network configuration & mounts, and procced with the uninstal of the plugin.
After remove it, i try to reinstall with the same network configuration that was before (same IP, same vnet, default interface, etc...), and opened two CMD in my computer, one performing ping test to the server IP, and the other to the PLEX IP (192.168.100.250 and 192.168.100.252 respectively, my router is set to 192.168.100.1, the DHCP is an 192.168.100.0/24).
After a minute or so on 50% "- ffmpeg", the CMD performing the ping test to 192.168.100.250 (the server) lost 2~4 packages, and return pinging normaly, and so 192.168.100.252 was able to succesfuly ping. So the instalation procced, and when it's reach 75% "- ffmpeg" again, the CMD isn't able to ping both of the IPs, after 2~4 packages loss again, the 192.168.100.250 return, but 192.168.100.252 don't, and the following error message prompt.
i'm aware of the DNS / Gateway manuly set up when not using DHCP on the server, and the configuration ware setup before this (so the plex was up and running). But i revised all the network configuration, tries to change it to DHCP and instal the plugin in DHCP mode, but it's fail in 50% "- ffmpeg" with the following DHCP error message (that I already expected).
So i procced to redo all the network configuration on the server (set the IP to 192.168.100.250, set the DNS to all combinations possible between 8.8.8.8, 8.8.4.4, 1.1.1.1, 208.67.222.222, 208.67.220.220 and 192.168.100.1 (my router), set the IPv4 Default Gateway to 192.168.100.1), but even after this reconfiguration, i wasn't able to setup the plugin (same "coult not resolve host: github.com" error).
I tried to ping to google.com and github.com in the shell, both successfully as follow
After this, i give up the plugin instalation and procced to creat a jail and do it manually, and for my surprise, when i try to add a jail, the follow error prompt appear...
After google the log, some threads on this forum said that this is a certificate error (but the threads were for FreeNAS 11, and i'm not able to perform the shell commands the threads sugest - and I was afraid of ending up bricking my server with FreeNAS commands on TrueNAS). One of the solutions sugests a system update, my version was the 13.0 U3, and the newest version was the 13.0 U5.1, i doubt this was solve the problem, but it's cost nothing, and i go to the automatic update and...
Another connection error, i try to ping this URL, and it was pinging normally as was google and github...
So i tried the manual update, it worked fine, my system is now on the 13.0 U5.1, and its solved nothing, all previous errors continued in the same way...
And i've checked my certificate before and after the update, and it's the same, with the expiring date to "2024-05-05"...
Anyone has any idea if i'm doing anything wrong?
Any suggest for solving this?
Thanks in advance for anyone who spends some minutes reading and trying to understand my problem, since now i apollogies for any english miswriting, it's not my native language.
PS.: Yes, i've try to restart the server, a lot of times, since the plex prompt the first "not authorized" error.
PS².: My home router was instaled by the provides, it's a HG8245W5-6T.
Attachments
Last edited:
