plex.tv down?

General Discussions
41

I turned on verbose but I don’t seem to be able to find where I delete the logs. help please

42

Since only two of you answered but both say they are on Cox, are you both using the cox dns servers?

43

Here are my plex logs.

44

@sulliplex said:
I turned on verbose but I don’t seem to be able to find where I delete the logs. help please

just go delete the Log files themselves (it’s a manual step)… If you aren’t comfortable going in and doing that manually. that’s fine.

45

Same problem here - I’m using Chrome and if you do the F12 developer tools and refresh the plex page, you can clearly see it’s just not able to connect to https://plex.tv/pms/

Tried from a couple other computers at home, none worked, same issue. RDC’d to a server I have at EC2 and another datacenter and tried, both work. With all of them I’m just trying Chrome directly, so I don’t see anything else being an issue. I even tried curl for the heck of it and it didn’t work either. My home network is provided by Cox, so perhaps they’re having some routing issue? DNS doesn’t seem to be the issue, as I tried the IP directly and machines here still couldn’t connect (you’ll get a cert warning if you do connect because you’re not using a domain name).

46

@ChuckPa said:

@mostlyhuman said:
once I saw the issues the first thing I tried was rebooting but the problem still persists .

Let’s walk through this and capture a detailed / verbose log for me please. (anyone else wishing to contribute, please feel free)

  1. Turn on Verbose logging.
  2. Stop Plex
  3. Delete the old log files
  4. Start Plex
  5. Sign in (attempt) in Settings - Server - General and in the bundled web app itself (let’s get both login attempts)
  6. wait 30-45 second after the login attempt failures
  7. Nicely shutdown Plex and capture the logs or get the logs using the ‘Help’ feature.
  8. attach here to your next post.

9… On next restart, you can turn Verbose logging off and go back to “Debug” logging.

Which log should I delete?

47

@Anx2k said:
Same problem here - I’m using Chrome and if you do the F12 developer tools and refresh the plex page, you can clearly see it’s just not able to connect to https://plex.tv/pms/

Tried from a couple other computers at home, none worked, same issue. RDC’d to a server I have at EC2 and another datacenter and tried, both work. With all of them I’m just trying Chrome directly, so I don’t see anything else being an issue. I even tried curl for the heck of it and it didn’t work either. My home network is provided by Cox, so perhaps they’re having some routing issue? DNS doesn’t seem to be the issue, as I tried the IP directly and machines here still couldn’t connect (you’ll get a cert warning if you do connect because you’re not using a domain name).

Thanks for the heads up, yeah could be an ISP issue.

48

yes, using cox dns servers

49

@sulliplex said:
yes, using cox dns servers

same here, Cox

50

Cox for me also. I tried changing DNS in windows settings to 8.8.4.4 still does not work.

51

@ChuckPa said:

@mostlyhuman said:
once I saw the issues the first thing I tried was rebooting but the problem still persists .

Let’s walk through this and capture a detailed / verbose log for me please. (anyone else wishing to contribute, please feel free)

  1. Turn on Verbose logging.
  2. Stop Plex
  3. Delete the old log files
  4. Start Plex
  5. Sign in (attempt) in Settings - Server - General and in the bundled web app itself (let’s get both login attempts)
  6. wait 30-45 second after the login attempt failures
  7. Nicely shutdown Plex and capture the logs or get the logs using the ‘Help’ feature.
  8. attach here to your next post.

9… On next restart, you can turn Verbose logging off and go back to “Debug” logging.

Here’s the new log with verbose on.

52

guys looking at downdetector, looks like cox is having some issues and it’s not with all sites, so maybe that your issues. http://downdetector.com/status/cox-communications/map/

53

so any work arounds available? or are we stuck waiting for cox to fix the problem?

54

@jmcgeejr said:
guys looking at downdetector, looks like cox is having some issues and it’s not with all sites, so maybe that your issues. http://downdetector.com/status/cox-communications/map/

Yah I see that now!

5 October: Problems at Cox
Cox is having issues since 10:11 AM EDT. Are you also affected? Leave a message in the comments.

55

It’s not DNS related, I’m not using Cox’s DNS, and as I stated above I tried the direct IP’s into my home Cox machines and Chrome couldn’t open the page, while the ones on both my servers can. This would indicate to me it’s either an explicit blocking at some point or a routing (BGP) issue - I’m not saying they did it because of Plex, but if plex was routed through some network that was involved in a DDoS, then it might get null routed.

56

@Anx2k said:
It’s not DNS related, I’m not using Cox’s DNS, and as I stated above I tried the direct IP’s into my home Cox machines and Chrome couldn’t open the page, while the ones on both my servers can. This would indicate to me it’s either an explicit blocking at some point or a routing (BGP) issue - I’m not saying they did it because of Plex, but if plex was routed through some network that was involved in a DDoS, then it might get null routed.

Yes I agreed above that it wasn’t a dns issue, guessing you may have missed that. does appear to be a routing issue, sadly at this point there isn’t much plex can do, but I will speak with the higher ups to keep them informed.

57

sucks, ok ill check back later then.

58

I do not have the Cox as my ISP either so it is not because of them.

59

@jwh70 said:
I do not have the Cox as my ISP either so it is not because of them.

jw you’re the only one who wasnt, who is your isp? Maybe you’re on a small ISP that tags off the backhaul of Cox?

60

I also have recent got this browser error.! While viewing this thread.