Step by Step for SSL

[Lola_The_Kook 0]

On 7/16/2019 at 10:51 PM, byusinger84 said:

This is the one I use. Works well.

 

https://mythofechelon.co.uk/blog/2017/01/01/lets-encrypt-emby-server-and-windows

Hello everyone, 

I've followed this step by step tutorial to add SSL to my Emby Server. Unfortunatly for the moment when i try to reach my server using the https adress (https://myserver.com:8920) it does not work. 
Does someone as any clue to give to help me proceed ? Let me know what informations you need.

 

Thanks !

[Spaceboy 2492]

where does it fail? can you access your server at https://local-ip:8920 ?

[Lola_The_Kook 0]

Nope I can't either but i thought SSL was only working with a DNS 

[Spaceboy 2492]

ok, that seems like an incredibly complicated way to get SSL for your emby. personally i use this https://blog.awelswynol.co.uk/2017-06-emby-server-https-reverse-proxy/

but the guide you are following has you forward a port from your router to emby. if you cannot access emby on your LAN using that ip and port combination then its not going to work externally either

[Lola_The_Kook 0]

19 hours ago, Spaceboy said:

ok, that seems like an incredibly complicated way to get SSL for your emby. personally i use this https://blog.awelswynol.co.uk/2017-06-emby-server-https-reverse-proxy/

but the guide you are following has you forward a port from your router to emby. if you cannot access emby on your LAN using that ip and port combination then its not going to work externally either

Your method seems more complicated to me ^^
Actually I probably missed something in all the step cause I've never succeed to access my Emby with https://local-ip:8920 or https://local-ip:443 (I didn't get which one was the good one, s I've tried them both).
I did open the ports on my router so ... I don't really know what's wrong 
Here's a screen cap of my router NAT/PAT configuration (where 192.168.1.34 is my local IP for Emby) 

[Spaceboy 2492]

On 02/10/2021 at 18:23, Lola_The_Kook said:

Your method seems more complicated to me ^^
Actually I probably missed something in all the step cause I've never succeed to access my Emby with https://local-ip:8920 or https://local-ip:443 (I didn't get which one was the good one, s I've tried them both).
I did open the ports on my router so ... I don't really know what's wrong 
Here's a screen cap of my router NAT/PAT configuration (where 192.168.1.34 is my local IP for Emby) 

there's no point in looking at your port forward settings if you can't access emby through the https port on the lan

so questions:

1. i assume your emby server is at 192.168.1.34?
2. and you have fixed it to be there, either by reserving that ip on your router for it or by requesting that ip on your emby server?
3. have you opened windows firewall (or other firewall on your server) for port 8920?
4. if so, you should be able to access your server at http://192.168.1.34:8920. can you?

secondary question, why do you have ports 80 and 443 forwarded to your emby server? are you running nginx or some other software that needs that?

[Lola_The_Kook 0]

6 hours ago, Spaceboy said:

there's no point in looking at your port forward settings if you can't access emby through the https port on the lan

You've said that the guide I've followed "has me forward a port from my router to emby," so I thought it could be useful

6 hours ago, Spaceboy said:

so questions:

1. i assume your emby server is at 192.168.1.34?
2. and you have fixed it to be there, either by reserving that ip on your router for it or by requesting that ip on your emby server?
3. have you opened windows firewall (or other firewall on your server) for port 8920?
4. if so, you should be able to access your server at http://192.168.1.34:8920. can you?

secondary question, why do you have ports 80 and 443 forwarded to your emby server? are you running nginx or some other software that needs that?

So : 

1.  As I said in my previous post yes
2. Yes I've set a static DHCP lease on my router so the IP of my emby server is always 192.168.1.34. I've let the "local IP address" field on emby blank
3. Yes, I've opened the port 8920 in and out for all profils (domain, private, public)
4. Nope

Secondary question : I needed to forward port 80 to proceed  with the guide I've followed with IIS and Certify. I don't know if it still need to be forwarded now. I did some tests with port 443, but I can remove it now, cause I don't need it anymore. 

Following your questions, I'm thibking that maybe the only thing I did wrong is the opening of port 8920 on the Windows Firewall. Is there any specific settings that have to be done ? 

 

Thanks again for guiding and helping me  

 

[Spaceboy 2492]

8 hours ago, Lola_The_Kook said:

You've said that the guide I've followed "has me forward a port from my router to emby," so I thought it could be useful

So : 

1.  As I said in my previous post yes
2. Yes I've set a static DHCP lease on my router so the IP of my emby server is always 192.168.1.34. I've let the "local IP address" field on emby blank
3. Yes, I've opened the port 8920 in and out for all profils (domain, private, public)
4. Nope

Secondary question : I needed to forward port 80 to proceed  with the guide I've followed with IIS and Certify. I don't know if it still need to be forwarded now. I did some tests with port 443, but I can remove it now, cause I don't need it anymore. 

Following your questions, I'm thibking that maybe the only thing I did wrong is the opening of port 8920 on the Windows Firewall. Is there any specific settings that have to be done ? 

 

Thanks again for guiding and helping me  

 

ok, so if you disable Windows Firewall on your emby server, can you then access emby at https://192.168.1.34:8920 ?

if yes, the problem is your configuration of windows firewall for port 8920

If no, the problem is configuration of emby

how about the plain http port? does that work with windows firewall on at http://192.168.1.34:8096 ?

[Lola_The_Kook 0]

41 minutes ago, Spaceboy said:

ok, so if you disable Windows Firewall on your emby server, can you then access emby at https://192.168.1.34:8920 ?

if yes, the problem is your configuration of windows firewall for port 8920

If no, the problem is configuration of emby

how about the plain http port? does that work with windows firewall on at http://192.168.1.34:8096 ?

So i completly turned off the windows firewall and I still can't access https://192.168.1.34:8920 

So it must be coming from Emby ?

HTTP with 8096 works fine LAN and WAN

[Spaceboy 2492]

1 hour ago, Lola_The_Kook said:

So i completly turned off the windows firewall and I still can't access https://192.168.1.34:8920 

So it must be coming from Emby ?

HTTP with 8096 works fine LAN and WAN

then post screenshots of the network page from the emby server dashboard

[Lola_The_Kook 0]

Here it is !

Thanks again

 

 

[richardvrusso 10]

Hi all,

I know I'm late to the game but thought I'd share my experience. I have emby running on Win10 pro, domain name thru namecheap, namecheap's dynamic DNS client and reverse-proxy from Caddy. What is nice about Caddy, true it has no gui, but it does ALL the Let's Encrypt work for you, even renewing the certs.

From what I've learned from using Caddy, apps you want to secure thru it need minimal tweaking. Even apps that do not have built-in 443 can still be secured thru Caddy.

So on my emby network page for the public ports I have 80&443. Then the public url in the external domain field. Then my firewall only has 80&443 forwarded to emby. My friends/family can all access via the emby public url. Internally I only access it with port 8096. Externally only port 443. 

regards,

®Ich

Edited October 5, 2021 by richardvrusso

[Lola_The_Kook 0]

Hi all ! 

Sorry it took so long for me to reply. My NAS crashed and it took me some time to put it back running. 

Si thank you @richardvrusso for the tip. If i'm not able to go through the SSl process, maybe I'll try your way. For the moment I'm using noip DNS so it's free, I'd like to stay that way but I'll keep it in mind.

@Spaceboy : You haven't react to my last screen capture. Any idea what I should do next ?

 

Thanks again for all your ideas guys !

[wonderwond 2]

ive been trying for weeks to get ssl on my emby, cant seem to get it to bind to port 8920,  router is all fine on the porting, even tried dmz.  wont bind. ive tried porting many different ports

[Luke 36997]

4 hours ago, wonderwond said:

ive been trying for weeks to get ssl on my emby, cant seem to get it to bind to port 8920,  router is all fine on the porting, even tried dmz.  wont bind. ive tried porting many different ports

Hi, what exactly happens when you try?

[sskwhiteshadow 2]

Not sure when u mean by not binding .

To check if netstat sees  it listening run the follwoing form admin level cmd shell:

>netstat -anb


Do  u see it listening? share results

Edited December 10, 2023 by sskwhiteshadow