EPG fails to update

Plex Media Server NAS & Devices
121

@sa2000
Teksavvy - cable - so it’s rogers backbone I believe. Does it make any sense to call Rogers on this?

122

@bwe said:
@sa2000
Teksavvy - cable - so it’s rogers backbone I believe. Does it make any sense to call Rogers on this?

There is no harm in users doing that. We have raised a support request with cloudflare

123

@bwe @sa2000 I"m on Start which resells Cogeco.

124

I’m with Teksavvy as well. Toronto, Canada.

125

@CSB001 said:
@bwe @sa2000 I"m on Start which resells Cogeco.

They appear to offer Rogers or Cogeco

126

I’m back up and running - I didn’t change anything… anyone else?

127

Having issues as well. Teksavvy. Toronto, Ontario

128

I can call my buddy at Rogers on the network team.
I need to confirm the network path/ip addresses traceroutes etc so I can provide him with the information required to do diagnostics.
sa2000 can you confirm for me? thanks

129

Also from Ontario on Rogers, and the VPN is the only thing that works right now for me.

130

I don’t pretend to have digested the many threads on the EPG issues and all the responses in this thread but I did see a theme that this was somehow region based. If I’m wrong, sorry in advance. I can tell you that the EPG update has been a huge problem and I’m in Texas and using Frontier. I have 8 tuners in my server with the same 35 stations provisioned for each. I believe the EPG issues to be causing problems with missed recordings and some of the crashes. It’s gotten worse with the most recent PMS update. I did delete the cache files and turned off the “more frequent updates”. I also refreshed my WAN IP.

EPG IS A SERIOUS ISSUE HERE FOLKS!

131

I’m also having this problem in Ontario. I’m using Start Communications.

132

TekSavvy and Start Communications both use lines from Rogers. I’m starting to think Rogers is the culprit.

133

I can say with high certainty that Rogers is NOT the culprit — I’m with Beanfield (totally separate network) and have the same issue.

The problem did seem to appear around the same time as the last PMS update (about 10 days ago), but I can’t say for sure that it’s PMS-related.

134

@mjsuhonos said:
I can say with high certainty that Rogers is NOT the culprit — I’m with Beanfield (totally separate network) and have the same issue.

The problem did seem to appear around the same time as the last PMS update (about 10 days ago), but I can’t say for sure that it’s PMS-related.

YUP, it started with the last update (or returned if you will). I am no where near Canada :slight_smile: I am in TEXAS using FRONTIER. BIG BIG BIG ISSUES!

135

I don’t know what else to tell you, When I’m using my VPN it refreshes fine.

136

@chyjinx where is your VPN terminating? I tried using TunnelBear USA and it didn’t work any better.

137

@mjsuhonos said:
@chyjinx where is your VPN terminating? I tried using TunnelBear USA and it didn’t work any better.

I use PIA, the last place I was connected to was Mountain View CA, before that was somewhere in NJ.

138

I was able to uninstall my beta version (thanks SA2000)
I uninstalled the latest version and installed 1.10.0.4523 from 2017 and had the same issue.

605×454 39 KB

When I ran SWAT teams at Rogers I always did a diagram to help us in problem determination. I’ve created one and I’m sure there are lots of errors, but its a start.
I’m not sure what happens past cloudflare. I guess it has to go to plex and/or gracenote.

What we know: (true statements)

  1. Most of the customers who have reported issues are from Ontario.
  2. Most of the customers have Rogers as an ISP.
  3. When using a VPN, sometimes it solves the issue.
  4. VPN allows you to create a secure tunnel through your ISP to the internet. This tunnel stops the ISP from doing seeing anything your doing and stops them from shaping the traffic based on the content.
  5. When tethering from a cell phone through tellus, this issue disappears.
  6. Those who have uninstalled the new PMS and installed an older version have not seen improvement.
  7. Where the path goes to cloudflare from the internet, the physical path is the same regardless of whether it is via vpn or from the ISP.

Please feel free to update/correct my What we Knows
You may copy my diagram and update and repost if you wish…
https://docs.google.com/drawings/d/1jqX_EW53vZVYL5bseLNlQg1zI1z0rzNG9wqyf2M8bmI/edit?usp=sharing

Mark

139

What we know: (true statements)

  1. When tethering from a cell phone through tellus, this issue disappears.

Item 5 is incorrect. The opposite happened - it did not make a difference. I am attempting to tether and download the EPG information again.

UPDATE
I just did a tracert and noticed Rogers is still part of the equation even when using Telus. It happens several hops down the line just prior to Cloudflare:
racing route to tmsapi.plex.tv.cdn.cloudflare.net [104.20.7.9]
over a maximum of 30 hops:

1 287 ms 2 ms 2 ms 172.20.10.1
2 * * * Request timed out.
3 195 ms * * 192.168.159.2
4 48 ms 47 ms 30 ms 10.118.50.41
5 48 ms 38 ms 38 ms 10.118.48.5
6 52 ms 30 ms 45 ms 24.156.157.141
7 39 ms 34 ms 38 ms 24.156.146.50
8 27 ms 37 ms 36 ms 24.156.157.117
9 44 ms 31 ms 42 ms 9906-cgw01.wlfdle.rmgt.net.rogers.com [209.148.231.9]
10 50 ms 27 ms 50 ms 209.148.233.38
11 * * * Request timed out.
12 49 ms 37 ms 34 ms 104.20.7.9

The EPG update is very slow and stops to update at 3%.

140

I only recently got Plex with DVR, but seems way slower than 1+ weeks ago. It was so bad I reset my shield to factory defaults. It’s been updating from scratch for 2.5 hours…it’s at 59% and seems to be continuing…Another US data point in Grand Rapids, MI