Thanks for the logs.
I’ve found the problem.
The Synology DNS isn’t resolving (pointing to) your modem/router.
As a result, PMS can’t contact Plex.tv to complete all the tasks.
Jul 28, 2022 20:58:56.685 [0x7fa1ef6aa0] DEBUG - Subscription: Refreshed all content in 3 ms.
Jul 28, 2022 20:58:56.708 [0x7fa1ec5aa0] WARN - [HttpClient/HCl#12] HTTP error requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxe host name) (Could not resolve host: plex.tv)
Jul 28, 2022 20:58:56.709 [0x7fa1d14aa0] WARN - [AutoUpdateRequestHandler] Couldn't get update channels. Trying again soon.
Control Panel - Network - eth0 AND eth1.
Make certain they resolve to either your modem/router or google (8.8.8.8 or 8.8.4.4)
I do caution you, putting both adapters on the same subnet causes problems.
If you want to use both, I recommend a BOND adapter.
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - Network interfaces:
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 2 eth0 (172.17.2.21) (00-11-32-96-08-EE) (loopback: 0)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 4 eth1 (172.17.2.22) (00-11-32-96-08-EF) (loopback: 0)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - Creating NetworkServices singleton.
Bond merges both adapters into one IP address with twice the bandwidth.
(however no one connection can exceed gigabit… you’ll get 2 Gbps total bandwidth)
After PMS is claimed, I’d do this next.
It’s unfortunate you deleted everything because you didn’t need to
