NGINX - troubleshooting

[crusher11 851]

4 minutes ago, vdatanet said:

and using public IP, it works?

On port 8096, yes. On any other port, no.

 

4 minutes ago, cayars said:

Don't trust a test done from inside your LAN.  Test this from a remote location or cell phone not using WIFI.

Your router could be doing some "loopback" magic getting in the way and making your testing confusing.

Same result.

 

2 minutes ago, rodainas said:

I set a remote vps with nginx, similar config like you, I could still access with public ip and 8096, I closed it, now the only way to access if by using the listening on nginx

It was impossible for me to test locally because the vps is outside my network, am sure you only need to close it, and use what nginx listens to.

I don't understand any of this.

[rodainas 188]

1 minute ago, crusher11 said:

On port 8096, yes. On any other port, no.

 

Same result.

 

I don't understand any of this.

You have to close port 8096

on router level or the machine that is running emby with firewall. 

 

better on router for you to still access it locally.

Edited July 10, 2021 by rodainas

[crusher11 851]

I don't know how to do that.

And if I do...it just makes remote access completely impossible, because the domain doesn't work either.

 

Edited July 10, 2021 by crusher11

[Carlo 4330]

Just now, rodainas said:

You have to close port 8096

on router level or the machine that is running emby with firewall. 

Do it at the firewall level since obviously this needs adjusting.  Doing a local firewall might have repercussions with NGINX we don't need to introduce right now!!!

[vdatanet 1549]

In your local netwok, if you type:

https://nasip and http//nasip

What happens?

[crusher11 851]

2 minutes ago, cayars said:

Do it at the firewall level since obviously this needs adjusting.  Doing a local firewall might have repercussions with NGINX we don't need to introduce right now!!!

You've lost me.

Do it at the firewall level, to avoid doing it at the firewall level?

[rodainas 188]

You can google how

look for port filtering rules something like that, remember you are closing it to the internet, you want to keep it locally running.

https://www.xfinity.com/support/articles/port-blocking-forwarding-comcast-networking

 

[crusher11 851]

Just now, vdatanet said:

In your local netwok, if you type:

https://nasip and http//nasip

What happens?

HTTP gets me the Synology dashboard, HTTPS gets me a "this connection is not secure" error followed by the Synology dashboard.

[rodainas 188]

3 minutes ago, crusher11 said:

You've lost me.

Do it at the firewall level, to avoid doing it at the firewall level?

He is talking about router firewall, not the device running emby firewall.

 

it is important to keep 8096 open locally, but closed to the outside (internet)

Edited July 10, 2021 by rodainas

[Carlo 4330]

3 minutes ago, crusher11 said:

You've lost me.

Do it at the firewall level, to avoid doing it at the firewall level?

router vs local firewall running on the machine

[crusher11 851]

3 minutes ago, rodainas said:

You can google how

look for port filtering rules something like that, remember you are closing it to the internet, you want to keep it locally running.

https://www.xfinity.com/support/articles/port-blocking-forwarding-comcast-networking

 

I can't find anything except port forwarding.

[crusher11 851]

Just now, cayars said:

router vs local firewall running on the machine

Which is which?

[vdatanet 1549]

2 minutes ago, crusher11 said:

HTTP gets me the Synology dashboard, HTTPS gets me a "this connection is not secure" error followed by the Synology dashboard.

Nginx is listening the same ports that your NAS, so you have to change nginx ports

 

[rodainas 188]

Just now, crusher11 said:

I can't find anything except port forwarding.

Post screenshots of those port sections of firewall to help people to help you. 

[rodainas 188]

2 minutes ago, vdatanet said:

Nginx is listening the same ports that your NAS, so you have to change nginx ports

 

Either way, the server is reachable by 8096 from internet, he needs to close it, but leave it opened locally.

Edited July 10, 2021 by rodainas

[vdatanet 1549]

Take a look at this, the problem is in your NAS configuration:

https://www.wundertech.net/nginx-proxy-manager-synology-nas-setup-instructions/

[crusher11 851]

3 minutes ago, vdatanet said:

Nginx is listening the same ports that your NAS, so you have to change nginx ports

 

Not sure what you mean by this.

 

 

3 minutes ago, rodainas said:

Post screenshots of those port sections of firewall to help people to help you. 

In the router config? There's nothing about a firewall. There's a "security" section, but that only seems to allow MAC/IP filtering.

[rodainas 188]

If you dont want access from internet to 8096 you need to close it, but leave it open locally. If not closed, you will always be reachable from 8096 from outside your network.

[vdatanet 1549]

I don't believe in magic, well if with Santa Claus yes, if port 8096 shows Emby and Emby doesn't listen that port somewhere there's a port forwading, and I think that's the NAS configuration.

Something like local port to container port.

Edited July 10, 2021 by vdatanet

[rodainas 188]

Emby has 8096 set as local port on the network config. But the port is not closed to the internet, so is reachable from outside, even if it is set as local on emby.

I had the same situation on my remote server, until I closed that port.

Edited July 10, 2021 by rodainas

[crusher11 851]

3 minutes ago, rodainas said:

If you dont want access from internet to 8096 you need to close it, but leave it open locally. If not closed, you will always be reachable from 8096 from outside your network.

But I have no idea how to close it....

[Carlo 4330]

Show us your current port forwarding from your router. I know you posted this before but let's see what it currently shows.

[vdatanet 1549]

6 minutes ago, rodainas said:

Emby has 8096 set as local port on the network config. But the port is not closed to the internet, so is reachable from outside, even if it is set as local on emby.

I had the same situation on my remote server, until I closed that port.

Oh, I haven't seen the local port settings. If we can access it remotely somewhere there is a port forwading.

Then this was correct:

 

proxy_pass http://192.168.0.2:8096;

@crusher11 can you post your container network settings:

https://kb.synology.com/en-uk/DSM/help/Docker/docker_container?version=6

Are you sure Nginx was working using your old router?

[crusher11 851]

5 minutes ago, cayars said:

Show us your current port forwarding from your router. I know you posted this before but let's see what it currently shows.

 

2 minutes ago, vdatanet said:

Oh, I haven't seen the local port settings. If we can access it remotely somewhere there is a port forwading.

Then this was correct:

 

proxy_pass http://192.168.0.2:8096;

@crusher11 can you post your container network settings:

https://kb.synology.com/en-uk/DSM/help/Docker/docker_container?version=6

Are you sure Nginx was working using your old router?

 

[rodainas 188]

4 minutes ago, vdatanet said:

Oh, I haven't seen the local port settings. If we can access it remotely somewhere there is a port forwading.

Then this was correct:

 

proxy_pass http://192.168.0.2:8096;

@crusher11 can you post your container network settings:

https://kb.synology.com/en-uk/DSM/help/Docker/docker_container?version=6

Are you sure Nginx was working using your old router?

Is correct, yes.