Emby connect help

[jgauthier 13]

Hello,

 First time emby user.   I can't seem to connect, through a web browser to my server.  I've followed these steps:

• Installed Emby server (docker)
• Exposed ports through firewall
• Created an Emby connect account
• Linked the account to my server.

 

When I log into Emby connect, I see my server.  It shows the internal IP address (not the docker IP, the docker host)

When I click "Connect" I just get a generic message "We're unable to connect to the server"

I can access my server remotely by using http://hostname:8096

Thinking I've done something wrong with the way my server is representing itself to emby connect - but I don't know what.

 

[Abobader 3469]

Hello jgauthier,

** This is an auto reply **

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:

Thank you.

Emby Team

[Luke 42083]

HI, what address is in the browser address bar?

[jgauthier 13]

Here's what I see:

 

Currently there are two "emby" because I blasted my docker container and remade it, and it registered a second one.  Neither one works, though.

[guilty57 4]

I'm having the same problem. I've Emby Premier, and connected to one user only. There is no other user on my server.
I can connect with local ip adress of my Synology NAS.

Or even with the remote ip adress and port number xxx.xxx.xxx.xxx:12486 after port forwarding on my TP-Link Archer Router.

This problem occurs for about a week when I try to connect from "https://app.emby.media/"

The user and server is linked and confirmed to my account.

 

 

embyserver.txt

Edited October 25, 2023 by guilty57

[pwhodges 2012]

22 minutes ago, jgauthier said:

Here's what I see:

I see a padlock, indicating that your connection to app.emby.media is using https.  However, you have not indicated that your server has been set up with https, so I presume it hasn't.  You must contact app.emby.media using the same protocol as your server will accept, or it will fail.

In the address bar, click to expose the protocol and remove the s leaving just http - that should then work.

Are you using Chrome?  Chrome uses https as default in places that previously http was used as default, so this has happened to several posters in the past few days!  I suspect the trouble is that Chrome is checking to see if app.emby.media can use https (which it can), but it has no way of knowing that it is then connecting to a server that can't, and so requires a simple http connection so as not to mislead the user into thinking that the whole chain is secure.

Paul

Edited October 25, 2023 by pwhodges

[Luke 42083]

In other words, if you haven't setup https for your emby server, then you need to use http://app.emby.media, not https://app.emby.media

The latest chrome version is aggressively redirecting you may need to manually change the address in the address bar.

[jgauthier 13]

Oh wow, is that all?  Let me see if I can make it work through my reverse proxy (with SSL) which might complicate things.

But I'd rather not manage certs inside emby directly.

 

[jgauthier 13]

That was much easier! Thanks guys!

[pwhodges 2012]

49 minutes ago, jgauthier said:

Oh wow, is that all? 

A simple thing on the surface, but it's causing no end of trouble.

Another example I've had, apart from Emby users, is that my wife couldn't open an important link in an email until I changed her default browser...

Paul

[guilty57 4]

Thank you all for your support.

I see that there is a lot to do on the server side for https connections.

So i decided to delete emby domain security policies from Chrome.

Here is what i did:

1. Go to chrome://net-internals/#hsts. Enter example.com under Delete domain security policies and press the Delete button.

2. Now go to chrome://settings/clearBrowserData, tick the box Cached images and files and press click the button Clear data.

Now everything works as it used to do.

Edited October 26, 2023 by guilty57