something wrong with logon

[plessers@gmail.com 32]

Hello,

 

- My Emby server is up-and-running

- I can connect to http://public-ip-address:8096 and https://public-ip-address:8920

- I can connect to http://internal-ip-address:8096 and https://internal-ip-address:8920

 

However,

If I want to connect with emby-connect (https://app.emby.media/connectlogin.html)  and I try to add my server to the list, I get:

 

Is there something wrong with emby connect?

 

Kind regards,

Bart

 

[ebr 16193]

Hi.  Can you please translate that message?

[Luke 42085]

Try the http version at 

 

http://app.emby.media

[plessers@gmail.com 32]

@luke:

 

http is not an option (password in clear text over the wire, really?), but that works...

 

I still miss something in the "emby connect" concept.

- I have 2 servers with local accounts defined

- I have 3 emby connect accounts

 

When I log in on emby connect, with an account, I can add servers and select them afterwards on the page

But if I want to connect to my server, I still have to logon on my server with the local password.

Also, If I added a server to my emby connect, it's not added permanently. 

Connection to my backend server can not be over https.

 

 

Is this normal? It's sounds not very safe to me...

 

Will emby connect support https in the future?

 

kind regards,

Bart

[Luke 42085]

It does support HTTPS, but the devices need to accept your SSL cert. What kind of cert are you using? Is it just the default self-signed cert?

[plessers@gmail.com 32]

Hi Luke,

 

sorry for the delay.

Yes, indeed. I use the standard self-signed certificate.

 

kind regards,

Bart

[Luke 42085]

It does support it but the browser will not accept your self signed certificate. You will need a trusted cert, like LetsEncrypt for example.

[plessers@gmail.com 32]

Hi luke,

 

can you redirect me how to attach such a certificate to Emby?

I already succeed to get an LetsEncrypt cert for my IIS on WIN10. Can I use it for Emby?

[Tur0k 148]

You should be able to reuse it. You will need to get the private key exported as a PFX file. Your ACME client may be able to support this. Alternatively, you should be able to use the Microsoft certificate MMC to convert a P7B file to a PFX file. Once exported you can point your Emby server to the .pfx file in your server's folder structure from manage server-advanced (under expert) menu. The latest version of Emby supports password protected PFX files. Don't forget to enter your external domain in manage server-advanced (under expert) menu as well. If you have multiple web services accessible through your firewall you will want to ensure that Emby is on its own unique port.

 

 

Sent from my iPhone using Tapatalk

Edited May 24, 2017 by Tur0k

[plessers@gmail.com 32]

Great! Up'n running.
- I can connect to https://www.mydomain.com:8920

- it's running with Let's Encrypt cert

 

 

Thanx for support!

B

[Luke 42085]

Thanks for the feedback.