Unable to access remotely

[pwhodges 2012]

7 hours ago, crusher11 said:

Local Management via HTTPS is disabled. Please access the device via HTTP.

That looks as if the router settings are wrong.

You need to go through your network step by step: router port forwarding; nginx domain recognition and proxying; Emby network settings.  Do it systematically - flailing around will just cause confusion and get you nowhere.  Forget the past ("this was OK till I changed xxx") - set things up correctly now.

Paul

[crusher11 1101]

23 minutes ago, pwhodges said:

That looks as if the router settings are wrong.

Not sure what you mean by that.

23 minutes ago, pwhodges said:

You need to go through your network step by step: router port forwarding; nginx domain recognition and proxying; Emby network settings.  Do it systematically - flailing around will just cause confusion and get you nowhere.  Forget the past ("this was OK till I changed xxx") - set things up correctly now.

Router is forwarding 443 to 4444* and 80 to 8888*.

NGINX is listening on 8888, where it returns a 301. It's listening on 4444, where it does all the reverse proxy stuff. The domain is correct.

Emby has 80 and 443 as its public ports.

CanYouSeeMe.org won't let me change the IP address it's checking, so I'm unable to check the port forward there. Portchecker.co reports 80 and 443 as closed. I have a VPN active at the moment, so I can't double check if NGINX is currently running but I believe it is. Not sure if the VPN would affect the port checkers either, it shouldn't should it?

Not sure what the next step is.

 

*I'm not sure of the security implications of using my real port numbers here, so I'm not.

[crusher11 1101]

CanYouSeeMe.org reports no access on either port 80 or port 443 both with and without NGINX active. I really have no idea where to look at this point.

[Neminem 1518]

Did you ISP flip you to CG-Nat solution?

[crusher11 1101]

53 minutes ago, Neminem said:

Did you ISP flip you to CG-Nat solution?

My WAN IP has not changed, it still matches the one tied to my domain by CloudFlare.

[crusher11 1101]

So, uh....anyone?

[Neminem 1518]

I'm out of ideas, your 20 issues are all over the forum.

And I'm tired of chasing different topics to help you.

And You do not provide any info, besides yes / no.

If you want help, help us, help you.

Edited December 16, 2025 by Neminem

[crusher11 1101]

1 hour ago, Neminem said:

I'm out of ideas, your 20 issues are all over the forum.

And I'm tired of chasing different topics to help you.

To the extent I have different topics, they're about completely unrelated issues, save for the fact that I also posted about this in the NGINX thread because it seemed that may have been the issue (though later troubleshooting seems to indicate that it isn't).

I'm not sure what other information you—or others—require here. I have no idea where to even look for the problem, to be honest, and right now I'm not sure how secure my setup is, so I'm not sure what to provide (as an obvious example, “my router setup page can be accessed at 123.456.789.123:80” would be a very bad thing to post).

[rbjtech 5284]

If you are using reverse proxies and cloudflare to front Emby, then there is a reasonable assumption that you know what you are doing or maybe you have followed some documented process step by step to get it working.   People can give pointers, but unless they have access to the environment, they are 100% guessing.

I suggest you just put emby back to default, use normal port forwarding to get it working.   Follow the Emby guides to add https etc.   Then when it's working - on a parallel system, learn about nginx, cloudflare etc - and then migrate over to it when you can support your own system.

 

[pwhodges 2012]

58 minutes ago, crusher11 said:

I have no idea where to even look for the problem, to be honest, and right now I'm not sure how secure my setup is, so I'm not sure what to provide

It seems to me that you are running a network setup which is beyond your capabilities to manage.  Perhaps you have a friend, or (cliché!) a nephew, who might be able to help you learn how to run it effectively.  Trying to teach you through this forum seems to be largely ineffective.

Paul

[crusher11 1101]

I followed the @pir8radio thread to get set up. But they no longer seem to be active here. 

 

[crusher11 1101]

The other possibility is it's related to the issues I'm having with my VPN. It's not active much, but when it is I'm completely unable to access my Synology NAS, which is what runs my Emby server. Perhaps the VPN has broken something somewhere in the chain.

[Luke 42077]

OK please let us know if you find anything.

[crusher11 1101]

On 12/17/2025 at 12:46 AM, rbjtech said:

I suggest you just put emby back to default, use normal port forwarding to get it working.

What would I need to change in order to go back to that? I don't remember what the defaults were or what settings I changed.

[Luke 42077]

For which Emby settings?

[crusher11 1101]

3 hours ago, Luke said:

For which Emby settings?

Whatever the relevant external access settings are, I guess.

[rbjtech 5284]

2 hours ago, crusher11 said:

Whatever the relevant external access settings are, I guess.

I'm saying go back to basics - use the emby guides to setup remote access - and once that is working, build/enhance and learn from that point on exactly what you are enhancing and why.   Do not just blindly follow guides to implement something you do not properly understand and subsequently cannot resonably support yourself.   Saying 'its broken - please fix' is not going to get you any support.   If people see that you have attempted to find out/narrow down the problem, shown willing to listen & learn, provided examples, tested different scenerio's and fully provide info requested - THEN they may offer their free time and experience to assist.  

Edited December 19, 2025 by rbjtech

[crusher11 1101]

2 hours ago, rbjtech said:

I'm saying go back to basics - use the emby guides to setup remote access

Okay, but my point is that guide is going to assume settings are at the default, so I was wondering if there was anything I needed to revert before trying to follow the guide.

Without altering any Emby settings:

If I forward 8096 to 8096, I can access my server at WANIP:8096.

Forwarding 8920 to 8920 makes my server accessible via WANIP:8920, though I have to click through an “unknown issuer” warning first.

 

EDIT: But that doesn't make sense, because in Emby's network settings the public ports are 80 and 443; 8096 and 8920 are the local ports. So I'm confused. What exactly are the public port settings in Emby's network settings doing?

My server is now also accessible via my domain, so that's progress. That remains true if I boot up NGINX, so...things are back to normal, without me having changed anything? I'm even more confused. Not sure how to tell if it's going through the reverse proxy or not.

Edited December 19, 2025 by crusher11

[pwhodges 2012]

36 minutes ago, crusher11 said:

Without altering any Emby settings:
If I forward 8096 to 8096, I can access my server at WANIP:8096.

Is that using the WAN IP on your local network or from outside?  Either way it appears that you are able to connect through your router, in which case I'm left wondering what you're trying to solve.  If your problem is that forwarding from 80 to 8096 isn't working, a possible cause is that the router is using 80 to connect to its configuration pages, and you need to change that in the router.

39 minutes ago, crusher11 said:

Forwarding 8920 to 8920 makes my server accessible via WANIP:8920, though I have to click through an “unknown issuer” warning first.

That's a certificate issue, and can be looked at separately.

Paul

[crusher11 1101]

2 minutes ago, pwhodges said:

Is that using the WAN IP on your local network or from outside?  Either way it appears that you are able to connect through your router, in which case I'm left wondering what you're trying to solve.  If your problem is that forwarding from 80 to 8096 isn't working, a possible cause is that the router is using 80 to connect to its configuration pages, and you need to change that in the router.

That's a certificate issue, and can be looked at separately.

Paul

I think I may have edited while you were posting.

[Lessaj 467]

2 hours ago, crusher11 said:

EDIT: But that doesn't make sense, because in Emby's network settings the public ports are 80 and 443; 8096 and 8920 are the local ports. So I'm confused. What exactly are the public port settings in Emby's network settings doing?

Telling the client apps what to use when considered remote from the server. It will try the local address first, fail, then try the remote address. I use the same domain name inside and outside my network with 443, all traffic is forced through my reverse proxy because 8096 is blocked even in my local network, but 8920 I left open. If I really need to I can enable the ACL rule on my switch that enables my machine to connect to it, or I can ssh into the server and use port forwarding to access it from localhost:<whateverPortIUsed>.