I have three echo dot on my home wifi lan. I use Plex as my media manager. Alexa voice commands were used to play music on the echos. I have recently switched from Orange dsl to Free fiber. As part of the switch I have moved my Plex server from an outside host to a host inside my network. I have opened ALL the required ports on the Freebox Pop and on the server firewall. Plex settings show that the plex server has remote access enables, with internet going to the freebox on port 32400/TCP and the freebox then connecting to the Plex server on port 32400/TCP. The Plex app on my phone can connect to plex and play songs both from inside and outside my lan. Alexa skill has been linked with the correct email and password for the plex account. |Alexa recognizes the existence of my Plex server, but on being asked to play music the answer is Oh Oh something went wrong.
How did you move the server? Did you physically move it, or build a new one? If so, then the server might technically be a different one than before. If so, Alexa might be attempting to connect to the old server rather than the current one?
I integrated Alexa with my home, but I don’t know the exact details on how it accesses shares. If it’s like Plexamp, which lets you pick from only a single library at a time, then it may be trying to “contact” the share on the old server?
I don’t know. Just spitballing here. Try deleting the Alexa skill and setting it back up.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
