Alexa error “uh-oh, something went wrong, I’ve alerted the Plex team so they can take a look”

mine is doing the same after v 1.18.1.1973

1 Like

Same here yesterday morning everything worked. Yesterday afternoon, nothing works. 1.18.1.1973. For what it is worth, plex works on every other device in my home.

1 Like

FWIW I recall updating to 1.18.1.1973 a few days before this appeared. And while trying to debug this, I rolled back to 1.18.0.1944 and it made no difference. So it doesn’t seem to me like this is an issue specifically with 1.18.1.1973, more likely something broke in the Alexa and/or skill backend.

1 Like

My Plex skill for Alexa stopped working a couple of days age. I am also on Plex version 1.18.1.1973. I have been using the Plex skill for Alexa to access my Plex music library for over a year with few issues. Now it either gives me the “uh oh” message, fails to respond at all, or indicates it found the music I requested but fails to actually start playing. .

@vanstinator, Add me to the list. Plex skill either does not respond at all or I get the “uh oh” .

2 Likes

Ditto; I have experienced Plex skill starting to fail in last day or so. I DID NOT update to 1973 but stayed on 1944 (Synology NAS Server).

Finally glad to see I am not the only one.

2 Likes

Now that you mention it, I believe I updated a few days before the symptoms too.

1 Like

I also lost the ability to use Alexa Plex skill from few days ago.

I solved the problem by using Emby Alexa.

Same here yesterday morning everything worked. Yesterday afternoon, nothing works. 1.18.1.1973.

Good to know that Emby is a viable alternative; unfortunately I am not going to spend $$ on another media server when I’ve already spent $$ on this media server :smiley:

and ‘me too’, plex was working fine on a raspberry pi v3 via my echo dots up until I ran a plex server update a few days ago … from the dates on this thread, this is a recurring issue - is this actually amazon routinely trying to make it difficult to use plex, to ‘persuade’ people to use amazon music instead?! :slight_smile:

1 Like

My symptoms change from oops error etc to some devices have started “sorta working” (no more oops) but playback stops after a single track, depending on if I have tried rolling back disabling and re enabling skill just never works correctly…Will this ever get fixed…?

The Alexa skill stopped working for me to over the last couple days. If I ask Alexa to tell Plex to play something specific, nothing happens at all, only silence. If I tell Alexa to open Plex, I get the “Uh oh” error message.

1 Like

! googling for other possible solutions, I found https://support.plex.tv/articles/115000320808-getting-started-with-alexa-voice-control/ and a reference to ‘Ask Plex to change my server’ - and it said it could only find one, and was using that as default.

Since then, it’s been working ok ! - Full disclaimer, I do have multiple (distinct) servers due to setting up a Pi (constantly on, but not enough storage to hold my full music collection until a new SD card arrives) and a new PC, which was a test…

So - Try this ‘alexa ask plex to change my server’ ! it could be a fix.

1 Like

I tried again just now, and suddenly it’s working again. I have changed nothing in my setup since yesterday. Anybody else find this is fixed?

2 Likes

Yes, just tried now after reading your post. Didn’t work earlier this morning. However I have also been rearranging libraries all morning so I could try Emby as well.

I had tried changing server a few days ago and got only silence. After reading MediaGriffin’s note, just tried it again, and it worked. Everything working again.

Emby is a lot trickier to set up, but once you do, it’s great to have as a backup, or alternate music library. Or even primary, though it doesn’t shuffle music playlists yet.

1 Like

Well done media griffin your solution worked for me as well…!

Same here… attempted to change the server when the issues started and received only silence; tried it again today and it is now working. Something broken was fixed, somewhere :wink: Would love to know what it was when/if it happens again…