Error connecting to your emby user

[cUfffs 0]

I'm losing my mind, what am I doing wrong?

I have tried with and without the automatic port forwarding option in Emby, and with or without adding manual forwarding per picture.

I can connect to https://emby.xxx.cc fine off my phone (different network), but it does say insecure even though it is https verified by ZeroSSL

I cannot see any errors in the latest log, but with automatic port forwarding there was an error to do with duplicate port mappings or something.

Alexa mainly tells me "Error connecting to your emby user", when I was setting up SSL it did say some other errors like connection or skills issue.

Test prompts: "ask m. b. home who is the active user?" (usually no response) & "tell m. b. home to change user to cal" ( error connecting to your emby user) & "tell m. b. home pause" ( error connecting to your emby user)

embyserver.txt

[cUfffs 0]

**FIXED AND WORKING**

if anyone finds themselves in same boat, the above screenshots was correct (except i changed secure connection mode to required for all remote connections) but the SSL was not good enough. When I now connect from outside of home network, it shows as SSL secured connection and now alexa is working fine.

I ended up removing the SSL and using cloudflare instead, steps:
Add A record: Name: `emby` (since using emby.xxx.com), content is my static ip, proxy status proxied, TTL Auto

create origin server certificate, and follow the steps in the official emby documentation for converting it and adding it to emby
I also made sure universal ssl is on, min version tls 1.2, always use https inside cloudflare edge certificate section
restart server
wait 20mins or so.
Had to tell alexa "change the player" then iterate through to the main tv player.

[Luke 39395]

HI, thanks for following up !

[SirGantyAlexa 0]

Hi guys,

Sorry to revive this thread, but I'm getting the same issue.

Do I need to use port 443 to connect to my emby server via SSL in order for alexa to work? (I can't currently as I have another service running on 443)

I can log in fine directly to my emby server using 8920 using my ddns name, and have it hooked up with emby connect and can connect to it using app.emby.media too, however when I try and use the alexa app, after the initial prompt, she always says "Error connecting to your emby user"

Does the alexa skill come in via app.emby.media (via 443) or directly to my server (in which case it needs to use 8920)?

Any help appreciated

[SirGanty 1]

Worth noting that I'm running emby in a docker container, which in turn is through a gluetun vpn network, so only 8920 is exposed on my local network, and then also to the outside world via port forwarding
The fact I can get to it directly via the ddns from outside my network, the SSL certificate is working perfectly, and app.emby.media also works (whilst pointing at the same ddns and port) is confusing me.
Surely alexa should be routed through too?
The linking worked fine, and allowed me to select the server

I'm normally half-decent at these things, but this one has me flummoxed

[Luke 39395]

1 hour ago, SirGantyAlexa said:

Hi guys,

Sorry to revive this thread, but I'm getting the same issue.

Do I need to use port 443 to connect to my emby server via SSL in order for alexa to work? (I can't currently as I have another service running on 443)

I can log in fine directly to my emby server using 8920 using my ddns name, and have it hooked up with emby connect and can connect to it using app.emby.media too, however when I try and use the alexa app, after the initial prompt, she always says "Error connecting to your emby user"

Does the alexa skill come in via app.emby.media (via 443) or directly to my server (in which case it needs to use 8920)?

Any help appreciated

Are you able to test without ssl so that your Emby server dashboard displays your remote address as http? 

[SirGanty 1]

When I disable https on the server, and open up 8096

and then try to add that to emby connect I get

although I can get in directly

Then if I switch to http://app.emby.media I can add the server (although not via emby connect, I have to add the server details manually)

Although bizarrely enough, as I play around with these settings I notice the emby connect login drops of my user... is that expected? that might have been be the reason I couldn't use connect option

However, when using http, if I disable and re-link the alexa skill, I don't see any servers to choose from, so cannot complete the linking.

So I go back, added back in https (i have tried bith "preferred" and "required for remote" settings), reconnected via https...

re-linked the skill, and selected the server, logged in my user

"Hi I'm Emby...."
"Play some songs"
"Error connecting to your emby user"

[SirGanty 1]

Not sure what I've done as part of all this faffing, but I can no longer select a server when linking the account in the skill
Emby connect no longer returns it either, when logging in to app.emby.media, I can only connect when I add the server manually using the ddns and 8920 port
Although my emby connect email is attached to my local user (I've removed and re-entered several times)

I'm now suspecting that its the emby connect linking that is stopping the alexa app working correctly.
No idea how it was managing to pull through the server before (despite it not being able to connect to my user anyway).

Is my VPN causing issues with emby connect? if so, how can I workaround it?
the VPN isn't optional

Many thanks for your help

[SirGanty 1]

I restarted the server, removed and re-added my connect email to my user
disabled and re-linked the skill

ta-dah!

No idea what is different now, but alexa is singing at me so I'm happy

nothing to see here, please move along.

thanks for your help.

[Luke 39395]

Thanks for following up !