Remote connection lost

[Daisuke88 3]

Hey yall, 

 

Had to reset my router at home because, life. Anyway, before the reboot my remote connection worked as expected, I have mu domain name from godaddy, i use cloudflare for dns and a record, but now for some silly reason, i cant connect remotely to my emby server.

 

I have been at this for hours and I just cant get it running at all. No changes were made on the emby server software side, again, just on the router. I have enabled port forwarding, and added my rules to it. 

 

Again, it used to work before, on the same router, Asus ROG GT-AX11000 Pro

 

 

 

Router settings below:

 

 

And I cant access it at all

 

 

I had to reset the router because I had forgotten my password... and well, here I am now.

[Daisuke88 3]

I am able to reach the server by deleting the a record and typing my wan ip plus port. I also tested port 8096 for http, and 8920 for https/ 8096 works fine, but 8920 does not. My ssl doesnt expire until next month, so im ready to renew it. but still. Everything was working fine before I resetted the router.

 

Im honestly lost

[Daisuke88 3]

Ports 80 and 443 show closed... but again, it was working right before the router reset. I have not changed anything on ubuntu side, if anything I tried adding the ports to the ufw to no avail.

If anyone has this router please help

[darkassassin07 652]

Your 'emby-ssl' rule is set to forward external port 443 to internal port 443.

Are you using a reverse proxy? 

If not and you intend to connect to emby server directly; the internal port of that rule should be 8920 (or whatever local https port you have set in emby server).

 

 

/edit for clarity:

 

There are two set of ports in emby server; 'local' and 'public' (http/https).

The 'local' ports are what emby server is actually listening to on the machine it's running on.

The 'public' ports are what Emby tells the clients to use to connect. If these are different than the 'local' ports, you need some infrastructure to receive that connection and route it to the local ports; such as a reverse proxy, or simply a port forwarding rule with the correct external(public) and internal(local) ports.

Edited August 17, 2024 by darkassassin07

[Daisuke88 3]

Solved. I had my rules all wrong, i guess it was such a while a go that I configured it I forgot how it was.

 

external port 443 forwarded to internal port 8920 on my local IP.