@razvan.constantin said:
I am sure once you find your culprit you will laugh saying “was so obvious”.
I did find the culprit. As I wrote, updating PMS to version 1.4.2 eliminated the problem. It wasn’t with my server, my network, wifi, sunspots, or karma. The act of updating PMS to 1.4.2 solved it.
What version of the server were you running previous to 1.4.2?
@cayars said:
What version of the server were you running previous to 1.4.2?
I’m pretty diligent about updating my PMS when a new release comes out so while I can’t say with absolute certainty that I was running 1.4.1 that’s more than likely what I was running immediately prior to the 1.4.2 update. I’ve been running Plex since late 2014, starting with a pre-1.0 version. Plex started failing on me somewhere around April 2016 and more or less completely fell apart around September 2016, to a point where I was using VLC Media Player to watch movies and TV shows on the living room TV. My daughter hated this because it wasn’t as easy, plus it stopped working on her iPad and PlayStation, so that’s when I really started digging in to it. I made my original post here in November 2016 after I’d exhausted all options, but I gave up on this thread when people started telling me how great things were for them and pointing out literally impossible problems (e.g., wifi) in my setup. I recognized that there would be no help for me here.
Then a few months ago a new version was released, I updated, and like magic Plex started working everywhere again. iPad, iPhone, iPod, Roku, PS3, PS4, locally, external wifi, cellular network…it all worked again. Like someone hit a switch. I made no changes to my server or network, other than to keep PMS and PMP updated. It suddenly just started working again. That’s the last time I took note of the version number (1.4.2) because I wanted to check the version notes to see if there was something there, but I saw nothing specific. I don’t know if one of the issues described in the published release notes was the cause of the problem and I just don’t understand it, or if there was another problem going on that was fixed under the radar, but I can pretty assuredly say that a bug was introduced somewhere around April 2016 and was resolved in version 1.4.2.
You need to run 1.5.1 or above now.
@sgodun said:
@dladrach48 said:
I know it is frustrating but you really have to vet out the network portion (especially home wifi networks) before looking at the application. It could be your Server or your router as well seeing you are having remote playback issues too. Just start isolating things down.I did. The problem was with the version of PMS that was running. The update to PMS solved it. But still, way to continue defending PMS.
I did not defend it, I have my own issues with it. I was just trying to assist. In the future I will not put any input in when I see “sgodun”.
You come back seven months later to dog the posters in your thread?
Did you provide logs or anything to anyone that can help?
@sgodun said:
@nigelpb said:
WiFi was not taken out of the equation if you still connected your clients by WiFi.Let me make sure I understand you correctly.
My server is on cabled ethernet in my home, connected to the internet via FiOS. My mother’s Roku box is on wifi, in her home that’s several miles away from mine, connected to the internet via Optimum. Neither setup could possibly be considered “exotic” in any way. With that in mind, you’re telling me that my mother’s wifi is the problem? That because every client — whether in my house or not — connects with wifi, then the problem is with all of those wifi connections?
No, I did not say that “the problem is with all of those wifi connections”. What I said is that WiFi was not taken out of the equation. The only way to exclude WiFi as part or the whole of the problem is to connect your clients by wired Ethernet so that no WiFi is involved anywhere. It’s perfectly logical so why do you find it so difficult to understand & try to argue that black is white?
@sgodun said:
@cayars said:
What version of the server were you running previous to 1.4.2?I’m pretty diligent about updating my PMS when a new release comes out so while I can’t say with absolute certainty that I was running 1.4.1 that’s more than likely what I was running immediately prior to the 1.4.2 update.
Actually you’re not very diligent about the updates. 1.7.3 is the current version you probably want to be running. 1.4.2 has a bad network bug that got fixed in 1.5.2 which is the minimum version you should run. You are presently almost 4 months behind on updates that fix a lot of issues.
Concerning WIFI it was never removed from the equation. If WIFI is being used then there is no way to say it wasn’t the cause of the issue. Keep in mind no one ever said IT WAS the problem, but people were trying to help isolate the issue and WIFI is a known issue that comes up over and over again so it’s always worth eliminating if at all possible.
@danjames92 said:
You need to run 1.5.1 or above now.
Right now I’m at 1.7.3. As I said, I’m pretty diligent about updating when new versions come out.
@dladrach48 said:
I did not defend it, I have my own issues with it. I was just trying to assist. In the future I will not put any input in when I see “sgodun”.
If that’s your choice. Input is very useful. People telling me how wonderful Plex is running on their systems and how it’s a wifi problem when it’s CLEARLY not a wifi problem is not input.
@JeffCrum said:
You come back seven months later to dog the posters in your thread?
No, I came back seven months later to close out this thread; I basically abandoned this thread when the “yay Plex yay” cheerleading started and it became apparent that no useful input was forthcoming. I recently opened another thread elsewhere about another problem I’m currently having with Plex and, in checking that thread, I noticed this was still open. So I posted a follow-up for those who are/were experiencing the same problem so they knew how to fix it. Then suddenly everyone started jumping on board with various accusations and such. Apparently I’ve stumbled into reddit without even knowing it.
Did you provide logs or anything to anyone that can help?
I provided all the discovery information in my original post. Nobody asked for a log so I didn’t post that.
@nigelpb said:
No, I did not say that “the problem is with all of those wifi connections”. What I said is that WiFi was not taken out of the equation. The only way to exclude WiFi as part or the whole of the problem is to connect your clients by wired Ethernet so that no WiFi is involved anywhere. It’s perfectly logical so why do you find it so difficult to understand & try to argue that black is white?
I understand it perfectly. It just makes no sense. You’re arguing that I need to make sure “no WiFi is involved anywhere”. What I’m asking you is, how does eliminating my mother’s Roku box — being on wifi on another network in another house in another town — help troubleshoot my Plex server?
@cayars said:
Actually you’re not very diligent about the updates. 1.7.3 is the current version you probably want to be running. 1.4.2 has a bad network bug that got fixed in 1.5.2 which is the minimum version you should run. You are presently almost 4 months behind on updates that fix a lot of issues.
Actually I am very diligent about the updates. I am currently running 1.7.3. The 1.4.2 update was several months ago, and I’ve updated PMS on every release since then.
Concerning WIFI it was never removed from the equation. If WIFI is being used then there is no way to say it wasn’t the cause of the issue. Keep in mind no one ever said IT WAS the problem, but people were trying to help isolate the issue and WIFI is a known issue that comes up over and over again so it’s always worth eliminating if at all possible.
As I asked another person in this thread, how does eliminating my mother’s Roku box — being on wifi on another network in another house in another town — help troubleshoot my Plex server?
Great to hear your on 1.7.2.
You mom’s Roku being on Wifi would have no bearing on anything unless her device was one having issues.
I think much of this thread is just misunderstand of the facts and the long time periods that passed between posts and really not more than that.
In the future if you find a problem (and there will be) see if you can reproduce it then go to settings/server/help and grab the log ZIP file to post with the initial post. Makes life easier for everyone that way.
Carlo
@sgodun said: …
I provided all the discovery information in my original post. Nobody asked for a log so I didn’t post that.
The logs should not have to be asked for, particularly in complex situations like this:
https://support.plex.tv/hc/en-us/articles/220049328
From a bit down that page:
Here’s what we need to efficiently analyze an issue:
The specific app and/or server version being used and device it is being used on
The steps to reproduce (use screenshots where appropriate)
Provide current and expected behavior
Log files (if possible)
The logs are now VERY easy to get so there really in no reason not to provide them.
See: https://support.plex.tv/hc/en-us/articles/200250417
@Elijah_Baley said:
The logs are now VERY easy to get so there really in no reason not to provide them.
See: https://support.plex.tv/hc/en-us/articles/200250417
Good to know; thanks. Perhaps if someone could have pointed that out to me awhile back, rather than extolling the virtues of their own setups and Plex in general, I could have been informed about that much earlier on.
Get over it. Do you want help or no?
Is it fixed? Or, where are your logs?
@JeffCrum said:
Get over it. Do you want help or no?
Is it fixed? Or, where are your logs?
It’s been my experience that the people with the biggest egos and most arrogant attitudes are the ones who pay the least amount of attention to what’s going on around them. I posted that it was fixed a week ago.
Yeah, I know. God forbid you read more seven months ago.
Speaking of big egos, come in here crying, ignore it for seven months, then finally upgrade to the latest version and act like you actually fixed something.
Great Job!
@JeffCrum said:
Yeah, I know. God forbid you read more seven months ago.
God forbid you read my very justifiable reason for doing so.
@JeffCrum said:
Speaking of big egos, come in here crying, ignore it for seven months, then finally upgrade to the latest version and act like you actually fixed something.
Speaking of complete ignorance, there is absolutely nothing about this part of your statement which is even remotely true. But, good for you for thinking it is, I suppose.
Great Job!
You too!
