That was part of the issue. Yes, it said server was 'nearby; but all my traffic was going the long way around, and not staying local. Not a big deal for setting up, but when streaming via roku, things slow way down and buffering starts to occur.
Granted, I realize that my network mess is also partially to blame for speeds and buffering. Is also one of the reasons about replacing hardware and moving to a different platform to help speed things up overall.
I’m not sure what all you’ve changed or haven’t.
It sounds like the browser sign in issue has improved.
How’s Roku playback now?
ROKU playback…
That will have to wait a bit. As of yesterday, the pms was brand new. I have to get everything setup (add drives, create / configure folders, etc).
Its interesting that pin code is still in place. I thought that was on server side, didn’t realize it was on account. My youngest son hates it that I use a code and restricts his access to anything I feel is inappropriate.
The only real thing that was changed was removing the login information for plex. Once that was done, problem disappeared. At least for the moment.
Btw, Edge has its own “DNS rebinding protection” built-in, which cannot be disabled nor can you define exceptions.
Update!
TL:DR I stand by my resolution of FFox sign in script as problem or at least biggest factor.
Its been a few days, and so far all is going well per original sign in issue.
I decided that I would update Open Media Vault to v5.5.5 and things skewed way sideways. PMS in docker container is bad for me. Might as well be v6.6.6. Tried wiping and reinstalling, started getting crazy common cdrom not found. Ultimately discovered I wasnt writing usb disks correctly. Using Rufus (vs Balena Etcher) in DD legacy/uefi mode did the trick, but only for Debian 10. OMV would not cooperate. Same errors.
So, headless Debian 10, OMV 5.5.5, and Plex Media 1.19.5.3112 is all setup and working as anticipated. Still have yet to put my media or nas drives on and setup.
Thought I would try and reproduce the error. So, signed in with FFox 79 to <ip#>:32400/web and the games began again. This was not private page either. Removed sign in info for auto sign in, and everything works as expected. Cannot verify with Chrome / Chromium / Opera, as no longer installed. Repeated process, saving info, and problem crept back in. Cured with removing info again from FFox.
I am 99% confident that problem has been rectified (Games! Get it?).
My Winegard WF3000 extender and booster is working much better now that I am in latest and greatest firmware. Tech I spoke with suggested incremental updates from v1, and 6 updates later I am rocking and rolling. Tech also tols me that I was misinformed regarding traffic handling. The bridge / extender / booster is indeed viewable and to take note of Mac Address of WAN side to facilitate sifning into single device wifi networks. Make sure I use bridge Mac instead of my router or laptop MAC.
I gueas that means NAT is enabled with no way to turn off. Same with DHCP.
Going to play with ReactOS to see why exactly PMS wont install onto it. Hopefully can get devs to mitigate that issue.
Another Update!
Moving plex to another computer, of course that did not go smoothly. Ended up reinstalling OMV all over again. No big deal until I ran into the Fast Start / Hibernation bug but that is for another forum.
Absolutely no problems signing in to Plex (manually) using FFox 79. Seriously, no issues whatsoever.
Pushing my luck, I kept my sign in information stored in/on FFox, and the exact same errors returned. Deleting the sign-in information also removed the errors that I was experiencing. So, I know that I have found the solution, but do not know what the cause is: Why would stored information cause sign-in issues upon the redirect?
Had a few problems getting into the forums as well. If I open a new page to forums.plex.tv and try to sign in, a message is returned along the lines of “User Not Found”. But, if I sign into plex.tv first, and then goto the forums, then I walk right in and see list of posts / categories / my stuff.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
