Emby Alexa Skill Not Working – Extensive Troubleshooting Completed, Still Getting Connection Error

[Gary10 0]

Hello Emby Community and Developers,

I'm hoping someone can help resolve an ongoing problem with the Emby Alexa skill. We've spent several days troubleshooting this issue, and despite numerous configuration changes and successful tests of remote Emby access, Alexa still cannot communicate properly with the skill.

My Current Setup

Emby Server: Running on a TerraMaster NAS (TOS/Linux)

Emby Premiere: Key installed

Reverse Proxy: Caddy, running on the TerraMaster

Domain: shawnhometheater.duckdns.org

HTTPS: Configured with a valid certificate

External HTTPS Port: 443

Internal Emby HTTP Port: 8096

Router: Spectrum

Alexa Devices: Amazon Echo Show 8 and Echo Dot

Playback Device: NVIDIA Shield running Emby

The Problem

The Emby Alexa skill appears to link successfully to my Emby Connect account. However, whenever I attempt to launch or use the skill, Alexa responds:

"Sorry, I'm having trouble accessing your Emby skill right now."

On another occasion, Alexa stated that Emby was not supported on the device.

The Echo Show 8 sometimes displays the Emby interface or prompts me to select a server or movie, but voice commands still fail.

The same connection error occurs on both my Echo Show 8 and Echo Dot.

Troubleshooting We've Already Completed

1. HTTPS and Reverse Proxy

We configured Caddy on the TerraMaster NAS to provide secure HTTPS access using our DuckDNS domain.

Verified HTTPS access

Configured ports 80 and 443 on the Spectrum router

Confirmed the reverse proxy is operational

Adjusted Emby's secure connection settings for reverse proxy operation

Restarted the server and tested again

2. Remote Access Testing

We successfully connected to Emby from outside our home network using a smartphone with Wi-Fi disabled.

Movies play correctly through the Emby mobile app over cellular data.

We also verified playback on the NVIDIA Shield and laptop.

This suggests that Emby's basic remote access is working, although it does not necessarily prove Alexa's cloud service can reach the required endpoints.

3. Emby Connect Account

Verified the Emby Connect email address

Completed email verification

Successfully signed into Emby Connect

Unlinked and relinked the Alexa skill multiple times

Repeated the account-linking process

Confirmed that the skill reports successful linking

Despite successful account linking, Alexa still cannot access the skill.

4. Network and Firewall

Reviewed Windows firewall settings

Tested with Private Internet Access (PIA) VPN enabled and disabled

Investigated differences between local and external access

Restarted network equipment

Checked router port-forwarding configuration

At one point, the DuckDNS address behaved differently depending on whether the VPN was enabled, although external mobile access is now working.

5. Emby Premiere Issue

We previously experienced a problem with the Emby Premiere key screen displaying a continuously spinning blue circle.

We contacted Emby support about this issue and supplied server logs.

We also experienced difficulty with a password/key recovery request that did not appear to complete.

I'm mentioning this in case the Premiere verification issue and Alexa authentication problem are related, although we have not established a connection between them.

6. Alexa Testing and Logs

We tested the skill repeatedly on both Alexa devices, including unlinking, relinking and launching it again.

We also reviewed Emby server logs. During some failed Alexa attempts, we could not identify a corresponding request in the logs.

This raises the possibility that the failure occurs before the request reaches Emby Server.

Current Status

Working:

Emby Server on TerraMaster

Caddy reverse proxy

HTTPS remote access

Emby Connect sign-in

Mobile streaming over cellular

NVIDIA Shield playback

Alexa skill account-linking process

Not Working:

Alexa voice commands through the Emby skill

Reliable communication between Alexa and Emby Server

Questions for Emby Developers

Is the Emby Alexa skill still actively supported and functioning with current Amazon Echo devices?

Are there any known problems with the Alexa skill when Emby runs behind a Caddy reverse proxy?

Does the Alexa skill require any specific server configuration, authentication endpoint, or network setting beyond normal HTTPS remote access?

If the skill links successfully but fails immediately afterward, does that indicate an authentication or server communication problem?

Should an Alexa request appear in the Emby server logs when the skill is launched? If not, where should we look for diagnostic information?

Could an Emby Premiere validation problem affect the Alexa skill?

We would appreciate guidance on how to identify exactly where the communication is failing rather than repeating the basic setup procedures we've already completed.

I'm happy to provide additional logs, screenshots, or configuration information.

Thank you for any assistance!

[Luke 43346]

Hi, besides https, it also requires having an ssl certificate that Alexa accepts.  That’s a big one  that some get tripped up on.

 Were able to login from the skill?