I enabled logging and tried to play a video and got the usual "An error occurred while trying to play this video, please check your connection", I'll put the logs below if anyone smarter than me knows what they mean. I've uninstalled plex and reinstalled on the firestick, restarted client and server, and can't sort out the issue. I can play stuff from my friends server on the firestick, and I can watch stuff from my own server on other devices like my phone or roku in the other room, it appears to be a problem specifically with the firestick plex. I run my own plex server at my home and I've watched stuff with the plex app on my amazon firestick for over a year without issue and today it suddenly stopped working. Please go to the relevant subreddits and support forums, for example: Build help and build shares posts go in their respective megathreads No referral / affiliate links, personal voting / campaigning / funding, or selling posts Welcome to /r/Plex, a subreddit dedicated to Plex, the media server/client solution for enjoying your media! Plex Community Discord Rules Dedicating an IP or port to only PMS should indeed work as well b/c you're falling in the default vhost again, but http2 will need to stay disabled.Latest Regular Threads: No Stupid Q&A: Tool Tuesday: Build Help: Share Your Build: Submit Troubleshooting Post Files not showing up correctly? But I have no idea whether that's possible with nginx (or even technically possible). So next idea I have to workaround this, is to check for user-agent and -always- pipe "okhttp" UA to PMS vhost. See - I posted this issue there and it got cross-reffed :-) If I recall correctly, http2 spec requires a SNI/Host, which explains why http2 never works. I verified it by again putting PMS as default vhost, and it started working again. As soon as I added other vhosts and changed the default, even HTTP1.1 stopped working. At first, I also came to the conclusion http2 was the culprit, however at that time, the PMS interface was the default vhost as well. According to my detective work, it's not related to http2 directly, but rather to the "okhttp" client not sending SNI/Host correctly. I investigated the exact same problem the last couple of days.
0 kommentar(er)
