Please help with HTTPS out of network connections

[Geophph 6]

Im really sorry if this is the wrong place to put this I don't really know what im doing. 

I've been pulling my hair out over this for the past few days and I know I probably seem really stupid but I'm just so lost. I am trying to set up my EMBY server so that it can be accessed remotely. I have managed to get it working with HTTP but I cannot get it to work with HTTPS. Ive tried following this guide 

and got all the way to the end but still could not access out of network. I also cannot seem to get Port 8920 to show as open even though it is enabled on my firewall and forewarded on my router. I know im probably missing a bunch of information so please feel free to ask any questions and thank you to anyone that can help.

[Abobader 3464]

Hello Geophph,

** 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

[Geophph 6]

Sorry to necro this thread but I could really use some help. I think I have set everything up, I can see my 8920 port is open andI have generated the SSL Cert using this guide however when I click the address here:

 

All I get is this

 

Im just a bit lost and could really use some guidance. Thanks

[Luke 42077]

@Geophph

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[Geophph 6]

embyserver-63896462069.txt

I hope this is what you need. Sorry im still very new to all this

 

[Geophph 6]

I have performed a restart so here are some more recent logs. I am able to connect if i use my public IP pointing at the 8920 port however I get the security risk ahead screen and that IP must be set in the emby external domain setting. However when I try and use my Domain name thepage comes up as server not found. Im sure I've done something wrong or im missing a step but I just cant for the life of me figure it out. I got my domain from metaname if that helps. Thank you again.embyserver.txtembyserver-63896468003.txthardware_detection-63896468021.txt

Edited October 18, 2025 by Geophph

[Lessaj 467]

It looks like your server is listening on 8920 so that's good that means your certificate should be working otherwise it can't start the listener.

• If you use a service like canyouseeme.org does it show 8920 as open?
• From within your network when you connect to https://192.168.0.42:8920 and you view the certificate, does the CN (common name) of the certificate match your domain name? It's normal to have a security warning since you're using the IP, this is just to make sure it matches what you expect.
  • If yes, when you perform an nslookup on your domain, does it match your public IP?
  • If yes, then you need to use the domain name to access it externally, not the IP, since the certificate would not be valid against the IP.
• You can further test this on your local system by putting in an entry in your hosts file for your domain which points to 192.168.0.42, this will bypass the DNS lookup resolving to your external IP and use the local IP, but still use your domain name. You should not get a security warning using your domain name at this point.

Edited October 18, 2025 by Lessaj

[Geophph 6]

@LessajHoly cow it works! I was able to see the open port on Canyouseeme.org. In your next step I could see the certificate validation had the correct common name however I couldn't quite understand what you meant with nslookup (Again im really new to all this so it probably seems dumb). I logged into my domain registrar and pointed the domain to my public IP and hey presto it just started working! Thank you so much! Now to see if it can be accessed outside of my network.

Edited October 18, 2025 by Geophph

[Lessaj 467]

I'm not sure what OS you're using but I'm going to assume it's Windows. You can run this in a command prompt (obviously replace my.domain.name with your domain).

nslookup my.domain.name

And that will perform a DNS lookup against your configured DNS, which is probably your router or ISP gateway, and it won't know what it is so it'll go out to the public DNS servers that it knows to use (could be your ISP DNS, Google, Cloudflare, Quad9... Whatever is configured on your upstream router) and return your public IP. Hopefully your domain registrar has a way to keep that up to date automatically, maybe with some kind of client that runs on the machine. Your public IP shouldn't really change unless you reboot your ISP gateway, but it still can, so you'd want it to stay updated automatically.

[Geophph 6]

Yeah using windows. Ive done that and it has come back with my public ip and google dns. Next step once it actually works will definitely be to try and get my registrar to update that ip automatically. I dont see any option on Metanames website to do that but if I have to do it manually im not gonna lose sleep over it. Ill have to renew the ssl cert anyway so really its water off a ducks back.

Edited October 18, 2025 by Geophph

[Luke 42077]

Please let us know how things go. Thanks.

[Geophph 6]

Been monitoring it over the last few days and haven't had any issues. Cheers for all the help.