Hi All, I think its important to see whats happening to each of us all at a glance. I’m heading out of town today but tomorrow I’m going to create a spreadsheet which we all can edit and fill in out details.
SA2000, is there any way we can get someone from operations that is familiar with this issue to join this discussion?
This problem can’t be good for Plex’s bottom line if new or existing clients cancel their subscriptions cause they can’t get it to work.
List of users - I have not included the few US users reporting here as I have not seen any logs to establish if same issue. However, I have assumed that anyone new reporting the issue in Ontario, is the same issue
@Markdreid said:
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
The route is to tmsapi.plex.tv
OK, my last attempt to soften the focus on region. My EPG is not updating, I have to “kick it” multiple times a day, and I’m missing more recordings than I’m getting as a result. This session capture is over the past two days.
Microsoft Windows [Version 10.0.16299.309]
© 2017 Microsoft Corporation. All rights reserved.
C:\Users\rak>nslookup tmsapi.plex.tv
Server: IBB_NET.local
Address: 192.168.110.1
Non-authoritative answer:
Name: tmsapi.plex.tv.cdn.cloudflare.net
Addresses: 2400:cb00:2048:1::6814:609
2400:cb00:2048:1::6814:709
104.20.7.9
104.20.6.9
Aliases: tmsapi.plex.tv
C:\Users\rak>tracert tmsapi.plex.tv
Tracing route to tmsapi.plex.tv.cdn.cloudflare.net [104.20.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms IBB_NET.local [192.168.110.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 6 ms 6 ms 6 ms 47.185.128.1
4 9 ms 13 ms 13 ms 172.102.55.118
5 7 ms 8 ms 7 ms ae8—0.scr02.dlls.tx.frontiernet.net [74.40.3.25]
6 8 ms 10 ms 7 ms ae1—0.cbr01.dlls.tx.frontiernet.net [74.40.1.82]
7 8 ms 7 ms 6 ms 13335.dal.equinix.com [206.223.118.145]
8 7 ms 6 ms 7 ms 104.20.6.9
Trace complete.
C:\Users\rak>tracert tmsapi.plex.tv
Tracing route to tmsapi.plex.tv.cdn.cloudflare.net [104.20.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms IBB_NET.local [192.168.110.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 28 ms 5 ms 5 ms 47.185.128.1
4 46 ms 12 ms 205 ms 172.102.55.112
5 6 ms 6 ms 6 ms ae7—0.scr01.dlls.tx.frontiernet.net [74.40.3.17]
6 6 ms 5 ms 7 ms ae0—0.cbr01.dlls.tx.frontiernet.net [74.40.4.14]
7 7 ms 5 ms 6 ms 13335.dal.equinix.com [206.223.118.145]
8 6 ms 6 ms 5 ms 104.20.6.9
Trace complete.
I’m in Markham, Ontario. ISP is Primus a reseller of Bell.
AtaboyX1
You can add me to the list @sa2000 I’m in Oakville, Ontario and ISP is Cogeco
@sa2000 me as well. Toronto, Teksavvy with Rogers last mile.
Routing 104.20.7.9 and 104.20.6.9 over a VPN works. So far…
Symptom while not rerouted EPG: received http response of 408 from request to https://tmsapi.plex.tv/v1.1.....
traceroute to tmsapi.plex.tv (104.20.6.9), 30 hops max, 60 byte packets
1 * * *
2 104-195-128-22.cpe.teksavvy.com (104.195.128.22) 19.352 ms 19.236 ms 19.102 ms
3 104-195-128-21.cpe.teksavvy.com (104.195.128.21) 18.892 ms 17.759 ms 18.865 ms
4 ae2-0-bdr01-tor2.teksavvy.com (206.248.155.17) 20.893 ms 21.746 ms 21.465 ms
5 198.32.181.56 (198.32.181.56) 21.185 ms 21.059 ms ae12-0-bdr01-tor.teksavvy.com (206.248.155.10) 19.533 ms
6 104.20.6.9 (104.20.6.9) 19.551 ms 12.871 ms 16.530 ms
Hey smokindog
It looks like in the US you guys can at least download something to your
EPG however wrong the data may be. In Ontario we can’t download anything.
Did you provide your logs to sa2000.
When I create my spreadsheet, all regions will be included.
On Wed, Apr 4, 2018, 9:58 AM Smokindog, forums+d299084-s6025034@plex.tv
wrote:
Plex Forums https://forums.plex.tv/
Smokindog commented on EPG fails to updateOK, my last attempt to soften the focus on region. My EPG is not
updating, I have to “kick it” multiple times a day, and I’m missing more
recordings than I’m getting as a result. This session capture is over the
past two days.Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\rak>nslookup tmsapi.plex.tv
Server: IBB_NET.local
Address: 192.168.110.1
Non-authoritative answer:
Name: tmsapi.plex.tv.cdn.cloudflare.net
Addresses: 2400:cb00:2048:1::6814:609
2400:cb00:2048:1::6814:709 104.20.7.9 104.20.6.9Aliases: tmsapi.plex.tv
C:\Users\rak>tracert tmsapi.plex.tv
Tracing route to tmsapi.plex.tv.cdn.cloudflare.net [104.20.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms IBB_NET.local [192.168.110.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 6 ms 6 ms 6 ms 47.185.128.1
4 9 ms 13 ms 13 ms 172.102.55.118
5 7 ms 8 ms 7 ms ae8---0.scr02.dlls.tx.frontiernet.net
[74.40.3.25]6 8 ms 10 ms 7 ms ae1---0.cbr01.dlls.tx.frontiernet.net
[74.40.1.82]7 8 ms 7 ms 6 ms 13335.dal.equinix.com [206.223.118.145]
8 7 ms 6 ms 7 ms 104.20.6.9
Trace complete.
C:\Users\rak>tracert tmsapi.plex.tv
Tracing route to tmsapi.plex.tv.cdn.cloudflare.net [104.20.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms IBB_NET.local [192.168.110.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 28 ms 5 ms 5 ms 47.185.128.1
4 46 ms 12 ms 205 ms 172.102.55.112
5 6 ms 6 ms 6 ms ae7---0.scr01.dlls.tx.frontiernet.net
[74.40.3.17]6 6 ms 5 ms 7 ms ae0---0.cbr01.dlls.tx.frontiernet.net
[74.40.4.14]7 7 ms 5 ms 6 ms 13335.dal.equinix.com [206.223.118.145]
8 6 ms 6 ms 5 ms 104.20.6.9
Trace complete.
–
Reply to this email directly or follow the link below to check it out:
https://forums.plex.tv/discussion/comment/1646782#Comment_1646782Note: Your signature will be included when replying directly by email
unless you remove it first. Attachments will not be included when replying.Check it out:
https://forums.plex.tv/discussion/comment/1646782#Comment_1646782
@Markdreid said:
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
Anything said from your buddy @ Rogers?
Updated the spreadsheet view here http://forums.plex.tv/discussion/comment/1646747/#Comment_1646747
Update: @Gerk is now working with the operations team and liaising with Cloudflare tech support to isolate the issue
@sa2000 said:
@CSB001 said:
@bwe @sa2000 I"m on Start which resells Cogeco.They appear to offer Rogers or Cogeco
Start Communications - new TPIA Rogers/Cogeco - Canadian Broadband | DSLReports Forums
I’m definitely in the Cogeco territory. Rogers isn’t available in my area.
I’m out of town today. Got confirmation from sa2000 on the end point. Will
give him a call tomorrow.
On Wed, 4 Apr 2018 at 14:52 chyjinx forums+d299084-s6025034@plex.tv wrote:
Plex Forums http://forums.plex.tv/
chyjinx mentioned you in EPG fails to update@Markdreid said:
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
Anything said from your buddy @ Rogers?
–
Reply to this email directly or follow the link below to check it out:
http://forums.plex.tv/discussion/comment/1646935#Comment_1646935Note: Your signature will be included when replying directly by email
unless you remove it first. Attachments will not be included when replying.Check it out:
http://forums.plex.tv/discussion/comment/1646935#Comment_1646935
Add me to the list.
Teksavvy, KW, Ontario
Tracing route to tmsapi.plex.tv.cdn.cloudflare.net [104.20.7.9]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DD-WRT [192.168.79.1]
2 264 ms 18 ms 14 ms 69.63.242.182
3 21 ms 33 ms 12 ms 104-195-128-70.cpe.teksavvy.com [104.195.128.70]
4 22 ms 16 ms 15 ms 104-195-128-213.cpe.teksavvy.com [104.195.128.213]
5 25 ms 16 ms 20 ms ae1-0-bdr01-tor.teksavvy.com [206.248.155.13]
6 26 ms 13 ms 15 ms 198.32.181.56
7 20 ms 20 ms 18 ms 104.20.7.9
Trace complete.
Me too. I’m on Teksavvy DSL (Bell, not Rogers) from Toronto (ish). My last day of guide listings is Apr 2 so I guess I lost the guide about 2 weeks ago.
Note that a very large percentage of Canadian users would be Ontario. A large percentage of those would be Toronto (ish) and a large percentage of those would be Rogers. I say this because I suspect it isn’t Rogers but may be simply Canada. I’m going to try 74174 (edit) 14174 as my zip (near Buffalo) as I get everything OTA and the listing should be almost perfect.
Note: I have fixed IP so I can’t try rebooting modem. Also it is very difficult for me to try VPN from server.
(edit) Forgot to mention. Mine failed with no (edit) plex update. Had been working for at least a month (I update manually) and failed before I got around to the latest update. I just applied update and no improvement.
@sa2000 You can add me to the list of affected users. I am also with Rogers in Ontario Canada. I will wait for your escalation with CloudFlair and will attempt to send in logs and address information tomorrow, if you still need it. My new router with Rogers supports ipv6, but I have disabled it and disabled IPv6 on my Windows 10 Plex server. Waiting to see if that makes a difference.
I’m in Halifax, NS, and use Eastlink. Having (I think) the same issue. I only have two OTA channels via HD HomeRun Extend tuner. I used to use Shaw Direct Classic. I have tried deleting my DVR, and I have tried all the listed providers. What I see is that most of the EPG provider entries show up twice. So I see two Shaw Direct Classic, two Shaw Direct Advanced, two Bell TV, but interestingly only one Telus Satellite. Most of the time the EPG remains blank after completion, but sometimes I do see some ‘shows’ showing, but even then a bunch of the tiles show black and stay stuck in “loading”. I am using Version 1.10.1.4602 on FreeBSD 11.1-RELEASE.
if you list me on your list, do not publish my email address please. Use CrazyDiamond698 as user.
Add me to the list as well. Rogers, Ontario. Gets stuck at 3%. Managed to update it via VPN but the next time it runs a refresh when not on VPN it kills the EPG.
If this is hosted/protected via CloudFlare then wouldn’t the solution be with the account manager of the CloudFlare account in question? Not Rogers… I’m not overly technical but seems like there is some CloudFlare setting blocking a large Rogers subnet.
Hi all,
Here is the link to a spreadsheet and updated diagram. Feel free to update.
https://drive.google.com/drive/folders/18-eajgyvoo_8mI0Cjlp2WY44M-BO7HzV?usp=sharing
Seems like we have multiple versions of PMS with the same issue or is this just because some are unix and some are unix and the version numbers don’t match?
Would the USA plex users also use tmsapi.plex.tv or another? When smokingdog did the traceroute it came to the canadian cloudflare?
Has anyone done and nslookup / tracert via VPN? How does in compare in terms of timing and route?
I tend to agree with user02010 that this issue should be resolved between cloudflare and the ISPs if there is an issue with the ISP.
@sa2000 me too.
Thanks for all the input.
As an update:
Information requested by Cloudflare has been submitted to them and they are investigating the problem. We suspect may be they have a misconfiguration in one of their servers that the traffic is going through
Last update from them was that they are still investigating
