It may not help with the current outage but once they get things back up and running if you follow the instructions and set it up then the next time this happens or if your internet goes down you will be all set and will not have this problem again.
If I go to 127.0.0.1 and my port number in a browser, I can access my server, even when this happens. I figured this out last time.
Doesn’t help for other devices on my internal network accessing plex though. I agree, this is bullshit and the final straw now.
I will be switching to either Emby or JellyFin over the weekend. I am done with Plex and their bullshit “always connected” requirement for me to be able to access my own content in my own freaking house.
Everything is up and running now. My Plex server is working perfectly now
To Plex CEO: Please use kubernetes infrastructure to host plex services. Then you guys can prevent this kind of outage because all Plex server installations are relies on your API servers. We can’t use Plex servers offline.
This is completely false. I did this last time this happened a month ago and I still could not access my content on my internal network this time. I couldn’t even access my plex server on the server it was hosted on by using the local IP. I had to use 127.0.0.1
Having a plex media server is NOT AN ONLINE SERVICE. Never has been and it is not a necessity. The changes you and your team have made implemented an “always connected” requirement which is completely unnecessary and ridiculous.
That’s what you guys fail to recognize. I should be able to access my server and contents internally on my own network without connection to the outside world.
Just to be clear. I don’t expect the Plex servers to have 100% uptime. I expect to be able to use my server. I’m fine if I can’t update metadata while there is downtime to Plex infrastructure, but I should be able to add media to the library. I can add the metadata later, when stuff is online, and so on.
Allow us to operate within our households independently of Plex. At the very least have a form of failover in place. This is an engineering problem that Plex should have resolved by now.
You can choose to listen to our constructive criticism or you can continue to ignore us until Plex alternatives fully mature, and then watch us all abandon ship.
I would love to vote for that and a few other feature requests, but my max vote was reached years ago… And they don’t seem to be filling those feature requests so I don’t get my votes back…
@elan any chance we could get a few more votes, even better some action on some of the requests that are 5+ years old…
Yes true @elan. As I guess you guys are using amazon AWS. Please use kubernetes infrastructure to host plex services. Then you guys can prevent this kind of outage because all Plex server installations are relies on your API servers. We can’t use Plex servers offline.
I believe this outage occurred due misunderstanding of Denial-of-Service (DoS) attack. Corona virus keeps people at home and force to use PLex more than ever. It’s not a cyber attack.
Exactly! There is absolutely 0 reason, if the Plex infra is having issues that we be locked out of OUR OWN ENVIRONMENT as a result.
This is complete horse-■■■■. It never used to be this way and should never have changed.
If there are settings that prevent this from happening then those settings should be the default. Users should not have to go searching on the internet to fix the crap that Plex broke by not having the best interests of their userbase at the forefront of their thinking.
This is starting to become a continual and regular occurrence and it is quite clear where the root problem stems from–top down. @elan when are you finally going to listen to us and quit holding our own setups hostage every time a ■■■■■ in the Plex infrastructures armour is exposed?
Is the metadata you are gathering on our usage really that valuable that you will inconvenience us all?