Hosting Settings

[Spaceboy 2573]

What are the correct hosting settings when you have a reverse proxy? i have ddns so i access remotely at https://mydomain/emby. but since implementing the reverse proxy i can't get the emby / alexa skill to work because it cannot access my server. in the dashboard it currently reports as https://mydomain/emby:8096

[Luke 42079]

You need to ensure that external address is correct. It also could be ssl cert related, meaning, Amazon can reach your address, but is rejecting your cert.

[Guest asrequested]

This might help

https://emby.media/community/index.php?/topic/47060-emby-with-amazon-alexa/?p=469248

Edited August 11, 2017 by Doofus

[Spaceboy 2573]

You need to ensure that external address is correct. It also could be ssl cert related, meaning, Amazon can reach your address, but is rejecting your cert.

yeah its definitely the address thats wrong, the cert seems to be working elsewhere.

 

how do i get emby to just report https://mydomain/emby without the port at the end?

[Spaceboy 2573]

yeah its definitely the address thats wrong, the cert seems to be working elsewhere.

 

how do i get emby to just report https://mydomain/emby without the port at the end?

nevermind, the external https port needs to be set as 443. no /emby. report https as external address

 

so external address is https://mydomain:443 in dashboard

[Spaceboy 2573]

Time to resurrect this.

 

So it seems it only worked before because I had an old pfx file in place allowing me to ask emby to report the external address as the https version. Now without this it doesn’t seem possible to get emby to report the external port as 443

[Luke 42079]

Have you provided an SSL cert?

[Spaceboy 2573]

Have you provided an SSL cert?

i don't need an SSL cert, the reverse proxy does this. i just need emby to report my external address as the https version despite there not being a pfx file. the only way around it is to set the https port i want emby to use to get through the reverse proxy as the public http port on the advanced settings page. this seems like it will work but is counter intuitive to set up. oh no that doesnt work because now the address is http://mydomain:port not https://mydomain.port

 

the only place this becomes a problem is alexa for emby which uses the external address as stated in the dashboard rather than anything you can manually set.

Edited January 6, 2018 by Spaceboy

[CBers 7451]

I can't get Alexa to work with Emby Connect and my Emby server behind a reverse proxy (nginx) either.

 

I can remotely connect to my server in the Web client via Emby Connect, but not Alexa.

 

@@Angelblue05 Any ideas please?

[Angelblue05 4132]

If the address changed in any way since you setup Alexa, have you tried going thru the identification process again? The server address is final at that moment. To update the address, the skill needs to be reset.

 

Let me know if it still doesn't work. Give me the time you tested. I'll check the Alexa logs.

 

 

Sent from my iPhone using Tapatalk

[CBers 7451]

If the address changed in any way since you setup Alexa, have you tried going thru the identification process again? The server address is final at that moment. To update the address, the skill needs to be reset.

 

I have unlinked and re-linked the skill and Emby Connect.

 

I left you a message elsewhere.

[Angelblue05 4132]

@@Luke

 

Can you help out? So we managed to resolved the connection issue.

 

What could cause CustomPrefs to not update server side? I POST an updated DisplayPreference object, with CustomPrefs filled out. When I request the DisplayPreferences from the server, CustomPrefs is empty. I don't understand why my POST is not taking. I compared the ids and it's the same, so I'm definitely talking to the right DisplayPreferences object.

 

Note, this seems to only affect CBers, he's behind reverse proxy.

Edited January 6, 2018 by Angelblue05

[CBers 7451]

@@Luke

 

Note, this seems to only affect CBers, he's behind reverse proxy.

@@Spaceboy

[Luke 42079]

@@Luke

 

Can you help out? So we managed to resolved the connection issue.

 

What could cause CustomPrefs to not update server side? I POST an updated DisplayPreference object, with CustomPrefs filled out. When I request the DisplayPreferences from the server, CustomPrefs is empty. I don't understand why my POST is not taking. I compared the ids and it's the same, so I'm definitely talking to the right DisplayPreferences object.

 

Note, this seems to only affect CBers, he's behind reverse proxy.

 

I'm not sure. We'd have to look at an example. Sounds to me like it didn't save at all.

[Angelblue05 4132]

Yeah that's what it seems like, there's no errors in the server log though. Is there a way to test this quickly via user settings in the webclient? Something that's written to CustomPrefs that we can test to see if the issue is coming from Alexa or not.

Edited January 6, 2018 by Angelblue05

[Luke 42079]

Well remember that CustomPrefs should only be basic key/value string/string pairs. What exactly are you embedding into it?

[Angelblue05 4132]

Well remember that CustomPrefs should only be basic key/value string/string pairs. What exactly are you embedding into it?

 

Key/value, the default player, if it's the first time Alexa is being setup (a bool flag) and the last time premiere was validated. Nothing complex at all. I've tested with a clean setup and I don't have an issue, customprefs are remembered.

 

Ok well, I'll keep digging, hopefully find something. Thanks.

[Luke 42079]

Maybe the proxy is having some kind of impact on the contents of the request. 

[Angelblue05 4132]

I thought that might have been it. Or something like that, I'm just not familiar enough with this that's why I asked.

 

I asked CBers to test with accessing the webclient user home screen settings and modifying the section to see if it was being rememembered and it was. That was while accessing externally via the reverse proxy. It's a really weird one.

 

I believe when I was checking the network traffic, home screen section is one of the things the webclient save to CustomPrefs (which is the same thing I'm doing in Alexa), except it works for him via the webclient and not Alexa. I'm baffled.

Edited January 6, 2018 by Angelblue05

[CBers 7451]

I wonder if @@Swynol has any thoughts.

[Spaceboy 2573]

i am fairly certain that when i had emby behind a caddy reverse proxy and i was able to get emby to correctly report the external address in the dashboard, i.e., https://mydomain:443 this all worked correctly.

 

i was only able to get the external address correct because i had a pfx file in place and linked to emby from when i was previously using it. it had expired however and was doing nothing other than allowing me to get the address correct

 

edit: i think the actual functionality to report the https address when that box is check is broken

 

 

 

i've just linked up an actual pfx file that i found in the emby SSL folder and with the box check it still reports the public http port in the address

apologies for the crazy formatting

Edited January 7, 2018 by Spaceboy

[pir8radio 1312]

i am fairly certain that when i had emby behind a caddy reverse proxy and i was able to get emby to correctly report the external address in the dashboard, i.e., https://mydomain:443 this all worked correctly.

 

i was only able to get the external address correct because i had a pfx file in place and linked to emby from when i was previously using it. it had expired however and was doing nothing other than allowing me to get the address correct

 

edit: i think the actual functionality to report the https address when that box is check is broken

 

 

 

i've just linked up an actual pfx file that i found in the emby SSL folder and with the box check it still reports the public http port in the address

apologies for the crazy formatting

 

If the emby server does not have a valid encryption cert installed, I believe you have to manually edit the system.xml and set <EnableHttps>true</EnableHttps>

[Swynol 375]

my emby is behind NGINX. NGINX manages my certs.

 

In emby server dashboard i have the following filled out in Advanced.

 

Public HTTP port - 80

Public HTTPS port - 443

External domain - https://emby.mydomain.com

Custom SSL Cert path - C:\certs\domain.pfx    ( i have this box filled in with a valid cert, however emby doesnt use it )

Cert password - ********

Require HTTPS for external - NOT TICKED

 

i then edit the system.xml file to change the https from false to true like this <EnableHttps>true</EnableHttps> 

The restart emby.

 

My dashboard then displays my external address as https://emby......:443  and Alexa works great with it.

[Sulman Aslam 0]

What are the correct hosting settings when you have a reverse proxy? i have ddns so i access remotely at https://mydomain/emby. but since implementing the reverse proxy i can't get the emby / alexa skill to work because it cannot access my server. in the dashboard it currently reports as https://mydomain/emby:8096

[Luke 42079]

What settings did you set?