Plex has refused to work for a long time.ZZkFromTryTry I have tried everything possible on this issue. Deleting codecs, forcing plex to re-download them, reinstalling the whole plex, but nothing helped.
I don’t know why this is, but simply and simply nothing can play because there are no codecs. It would be good if someone fixed this in some update, otherwise plex was a pretty good app.
Using FileStation,
Navigate to PlexMediaServer / AppData / Plex Media Server
Right-click Logs → Compress to Logs.zip
Download the zip file to your computer.
Attach the ZIP file here with your next post.
We will look at what’s happening.
( When nothing works on a Synology, the most common issue is networking )
Logs.zip (3.5 MB)
It worked for a while after completely uninstalling plex and reinstalling, but it worked for a week at most. It always ends up in this state eventually. I access Plex through cloudflare and a subdomain. This used to work perfectly fine before, this error only started appearing after a certain update.
PS: It doesn’t work on the local network (browser) either. But if I play the video in Plex Media Player App instaled in windows, everything works fine.
Syno network config is incorrect.
DNS lookup is failing. Check the IP addresses.
Jul 10, 2023 00:01:34.073 [139786476825400] WARN - [HttpClient/HCl#1] HTTP error requesting GET http://r3.o.lencr.org/MFMwUTBPME0wSzAJBgUrDgMCGgUABBRI2smg%2ByvTLU%2Fw3mjS9We3NfmzxAQUFC6zF7dYVsuuUAlA5h%2BvnYsUwsYCEgQibqL8eQ30RJ5rKDQVdWfhoA%3D%3D (6, Couldn't resolve host name) (Could not resolve host: r3.o.lencr.org)
Jul 10, 2023 00:01:38.992 [139786476825400] WARN - [HttpClient/HCl#5] HTTP error requesting GET https://plex.tv/api/v2/user?includeSubscriptions=1&includeProviders=1 (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
I use both NAS ports. Both are set to local network. I set the other port to DNS 8.8.8.8. so I’ll see if that helps.
If you have both NAS ports on the same LAN subnet, you’ll have problems with PMS and other apps.
This is because how the DSM Internal packet router works.
The best solution here is to BOND both adapters and make a single, bonded, adapter ‘bond0’.
Doing this will give you one interface which, if needed, can handle more than 1Gbps.
Don’t forget to update the ‘Default Gateway’ checkbox after creating the bond from eth0 and eth1
Great info, i will test it !
