Alexa Can't Reach Emby Server

[prahamovies 0]

Hi, 

Ive currently got an Emby Subscription, I have Emby working internally and externally with SSL Enabled. All works as expected apart from I am unable to use Alexa with Emby. 

I have the Alexa app installed, Emby Connect setup, skill enabled and account has linked fine. When i ask emby to play music, its unable to connect to my server.  

Please see emby server log attached. 

Anything else needed i can provide but i am at a loss here. Ive also tried re-linking the account. 

Any help would be greatly appreciated.

Cheers,

JP 

embyserver.txt

Edited December 13, 2020 by prahamovies

[Abobader 3464]

Hello prahamovies,

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

How to Report a Problem

Thank you.

Emby Team

[Carlo 4561]

Hi, have you tested Emby Connect login via browser with the user account being used for Alexa?

[speechles 2055]

What exactly does Alexa say.. does she say "I can't reach your Emby server"? I have an Echo Show 5 with Alexa and the Emby skill set up and working and had this same response but knew what to do.

Did you forward a port on your router to point to your Emby server?  Alexa connects to your server externally to route your intent.

Edited December 13, 2020 by speechles

[Luke 42079]

And also, what kind of SSL certificate? Where did it come from? It needs to be something that Alexa will trust.

[prahamovies 0]

Hi all, 

Yes Emby Connect works fine, i can access the site both through emby connect and my external domain name with DDNS. The SSL Certificate is provided by LetsEncrypt, is that supported? 

@speechles yea it just says "I cant reach your emby server" and to do the relinking/make sure its accessible from outside.  But even after re-linking and double checking the external connection is working fine. it still gives this message. All other functions/skills on the echo are working fine, even my router is working with it great. 

Cheers, 

JP  

Edited December 16, 2020 by prahamovies

[Luke 42079]

I'm not sure that alexa will trust letencrypt. @cayars have you tried?

[Carlo 4561]

25 minutes ago, Luke said:

I'm not sure that alexa will trust letencrypt. @cayars have you tried?

I have not personally, but the dev said YES it works, when I specifically asked about that cert.

I know both Alexa and Google Home work fine via Cloudflare with a cert assigned by them, which is what I'm testing/using as my daily.

I'm using port 443 on my setup for SSL and Emby Connect goes through that.

@speechlesWhat port are you using?
@prahamoviesWhat port are you using for SSL?

[speechles 2055]

@cayars 8920. The one Emby assigned it. That is how I access the server externally. But I haven't tried this since I've updated the server. When I try lately I get the same "I can't reach your Emby server" response but I think it is timing out. My ISP is horrible right now. Even my Blurams and Blink cameras are having issues with Alexa so I do not think mine is an Emby thing causing the issue. Everything Alexa is laggy even her responses back to me. The cameras lag out and do not even reply with an updated image they fall back to the Echo show home screen. So it must be my horrible ISP in my case.

Edited December 17, 2020 by speechles

[Carlo 4561]

@speechlesAny chance you could reconfigure and try 443?
I could certainly be wrong but I'm thinking these devices might only like 443 (pretty sure this will be required for local playback).

[prahamovies 0]

@cayars Currently im using Port 443 with reverse proxy through IIS so Emby is only listening on the default HTTP Port. 

Im thinking of setting emby directly on 443 with the LetsEncrypt cert and testing again, but would that mean im unable to use reverse proxy to get Alexa to work with emby? hoping to use reverse proxy as im hosting a number of sites. 

[Luke 42079]

It might meant that yes. If you're going to use SSL with Alexa, and then you'll need to use a certificate that Alexa trusts.