(Update at end, I now have it partially working.)
I’m having a similar issue - I just got an echo yesterday and Alexa can talk to my server and says it’s playing music, but then I don’t hear anything. The music shows up on a card in the “Home” section of the Alexa app on my phone, but not in the “Now Playing” section.
I have a double-router setup, where the first router is from my ISP and handles the bonded DSL connection but nothing else. It sets my second router to the DMZ host, and the second router does all of the regular router stuff. (Before I had a bonded connection, I was able to put the ISP router into Bridge Mode, but I can’t get that to work with the bonded connection.)
The first router is a F@ST 4320 and it uses 192.168.254.x internally.
My second router is a Netgear R7800 and it uses 192.168.1.x internally.
My Plex server is Version 1.10.0.4516, it’s accessible on my LAN at 192.168.1.6:32400. It’s running on a RockStor (Fedora Linux) server using the Docker image from Linuxserver.io.
In the Remote Access settings, when I let Plex pick it’s own port via UPnP, it picks a port like 23039 and reports that it is “Fully accessible outside your network”. However, when I manually assign a port and set up the appropriate Port Forwarding entry in my Netgear router, it reports “Not available outside your network” and warns me about a Double-NAT scenario. This happens whether I set the external port to 32400 or something else like 9134.
Manual port-forwards for other things seem to work fine, so I’m not sure why I can’t get them to work for Plex.
Under the Network settings, Secure connections is set to Preferred. On the Web settings, I always set Allow Fallback to Insecure Connections to “On same network as server”, although it seems to reset itself sometimes.
A couple of other curious notes:
- When I first set a custom port, it spins and then I see a brief flash of the green success message before it switches to the error message
- When I switch back to upnp mode, I sometimes get the red error message, but clicking the Retry button always fixes it. (And, the button changes from Retry to Apply.)
These are the only interesting-looking lines in the logs:
Dec 01, 2017 15:16:10.805 [0x7f0c6c7fd700] WARN - PublicAddressManager: WAN IP is a private IP address
Dec 01, 2017 15:16:12.089 [0x7f0ca37fe700] ERROR - MyPlex: mapping failed due to potential double NAT configuration
Dec 01, 2017 15:16:12.200 [0x7f0ca37fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (f0e6970f-ca39-4648-927b-4e7079f3f264, expected c17aafc2-39f2-444e-8b0f-1663a2cc3618)
Although I can post the entire file if you’re interested.
The plex server settings always shows the correct external IP.
Update:
I decided to try bridge mode again today and it worked!
It had been a year or two since the last time I tried to get bridge mode working, and I know that at least my netgear router had received a couple of firmware updates (and the ISP one may have also, I think they just push changes to it whenever they want to).
I did have to manually specify a port, the UPnP one didn’t work, but once I set it to 32400, the echo was able to play my music.
So, hopefully this is helpful to someone, I’m glad to finally have it working! (And a slightly more sane home network too!)
Update 2
I have experienced a couple of cases where the sound just stops near the end of the song. The second time it happened, I said “alexa resume” and it started playing the next song. Not sure what’s up there.
Also, it seems completely unable of playing a second song without prompting. Whenever I ask for an artist/album/playlist/etc, it usually plays the first one, but it never plays any further without an “alexa resume” or “alexa next track”. Not sure what the deal is there.
