Server Version#: 1.29.2.6364
Player Version#: PlexWeb 4.94.2
Tuner Make/Model: Fritz!Box 6690 Cable
Hello @sa2000,
I have a question about the EPG refresh.
I’ve noticed for a long time that the EPG refresh doesn’t seem to take place during the maintenance work at night between 4 and 8 a.m., but only in the morning after the maintenance work when you open Plex, for example.
(german translation is also missing)
I’m not sure if the refresh happens at a fixed time or is triggered by calling PlexWeb.- But certainly not at 4 in the morning.
That happens usually when Plex Server has not been running during the maintenance period, so it couldn’t update the EPG.
If the EPG data are too old, it is refreshed automatically after startup of Plex server.
Remember, on Windows Plex server will be closed if you log out.
(unless you are running it as a Windows system service – but that has its own drawbacks)
Maybe it’s employing some cunning power saving, where it shuts down the whole NAS during the night? Or maybe just certain apps?
The same effect could be caused if the network/internet connection would be unavailable during the night. For instance if (part of) the network infrastructure (wireless APs, router, switches) shuts down during the night to save power.
Or some other critical network device is somehow switched off because it happens to be conected to the same switched power bar as your main PC.
there were two maybe timeouts.
But there was no disconnect/new IP in on my router logs.
Nov 13, 2022 03:17:10.378 [0x7f5c10d66b38] DEBUG - CERT: incomplete TLS handshake from 45.227.254.54:64627: wrong version number
Nov 13, 2022 03:20:01.990 [0x7f5bf52f9b38] DEBUG - EPG[cloud]: Next thing to start/end is at 2022-11-13 03:23:00 (in 180 seconds)
Nov 13, 2022 03:21:48.334 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] Failure: 125 - Operation canceled.
Nov 13, 2022 03:21:48.334 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Nov 13, 2022 03:21:48.334 [0x7f5c10d66b38] ERROR - [EventSourceClient/pubsub/172.105.245.168:443] Retrying in 15 seconds.
Nov 13, 2022 03:22:23.335 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] Failure: 125 - Operation canceled.
Nov 13, 2022 03:22:23.335 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Nov 13, 2022 03:22:23.335 [0x7f5c10d66b38] ERROR - [EventSourceClient/pubsub/172.105.245.168:443] Retrying in 15 seconds.
Nov 13, 2022 03:22:38.336 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] Resolving 172.105.245.168 port 443
Nov 13, 2022 03:22:38.336 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] Resolved 172.105.245.168 to 172.105.245.168:443
Nov 13, 2022 03:22:38.377 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] Connected in 41 ms.
Nov 13, 2022 03:22:38.377 [0x7f5c10d66b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] Wrote data, reading reply.
Nov 13, 2022 03:22:38.482 [0x7f5c10f69b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] Read HTTP reply header.
Nov 13, 2022 03:22:38.482 [0x7f5c10f69b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] MyPlex: We appear to have regained Internet connectivity.
Nov 13, 2022 03:22:38.486 [0x7f5c10f69b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] PublicAddressManager: Obtaining public address and mapping port.
Nov 13, 2022 03:22:38.486 [0x7f5c10f69b38] DEBUG - [EventSourceClient/pubsub/172.105.245.168:443] MyPlex: async reachability check - current mapped state: ‘Mapped - Not Published’.
Nov 13, 2022 03:22:38.486 [0x7f5c10f69b38] WARN - [EventSourceClient/pubsub/172.105.245.168:443] MyPlex: we have an existing connectivity refresh request for async identifier 50fdf62f-bcfb-416d-8d5a-35a301d3ef1e, but it has expired so we will try again.
We setup a random time during the maintenance period for the EPG refresh - so in your case a delayed action would be queued within a random time beween 4am and 8am - the scheduled tasks period
I would need to see debug server logs covering the period and into the time when the EPG refresh happens later