Port bug with dedicated server IP?

[EliteCube 6]

Hey guys,

im new with emby.

I installed emby on my dedicated server with static public IP.

So my local IP is a public is
88.88.88.88

Emby write on the admin page:
Local:
88.88.88.88:8096
Public
88.88.88.88:8096

Good, I test it and i change the local port to 8097 and https to 8021 (public unchanged 8096/8020)

 

I restart and check public connection:
88.88.88.88:8096

Browser write:
ERR_CONNECTION_REFUSED

Firewall and all are disabled. I change nothing... Okay i test the local port...
88.99.148.20:8097
it works... ??

Why i cant connect to the remote port only on the local port on a remote server?
I test a vLAN with IP 10.0.0.10 (i chang it also in emby admin) and it does not work. Only connect to the local port

Is this Secure? Its a Bug?

It seems to me uncertain.

How is your setup on a dedicated server and security?

My plan is to use a domain with proxy. this work good, but the same only to the local port nothing with public
crazy...

 

My system:
Ubuntu Server 16.04 (Original minimal image and new install)
No Firewall no closed ports. (for testing)
1 dedicated public IP and 1 IPv6
No local IPs

Any ideas or answers?
I do not know if this is so right. It does not seem right to me

thank you guys

Edited April 29, 2017 by Seimann

[Luke 38874]

You may need to set up port forwarding in your router.

[EliteCube 6]

You may need to set up port forwarding in your router.

What for a router? its a dedicated server IP (and the forwarding ist open to the public port 8096)

 

i test to create a virtual LAN IP with

 

dont work. i bind lokal port 8097 to 10.0.0.1 and public port 8096 to 88.99.xx.xx

dont work. no matter what I do, only connection to the local port

 

the server is in a other country, i dont have LAN access. Its wrong

do you see a "router" here?   

now you say also its a bug?

Edited April 29, 2017 by Seimann

[pir8radio 1302]

I think the issue is your local and public IP are the same IP so how do you expect emby to tell the difference between local and public?  

 

If you are using a proxy, bind emby to 127.0.0.1 and enter the domain name or public IP into the "External Domain" field have your proxy point to 127.0.0.1 and you should see this in emby:   That is how I run emby at a hosted site.

[pir8radio 1302]

plus "local" access port is no less secure than "public" port.  You can use the local port as your public port.   If you are hosting your server you will need to setup the firewall no matter what, you dont want the box hanging right on the internet backbone...  so when you setup the firewall just block everything but your emby port so DLNA and what not are not trying to be sent out to the internet.    

[EliteCube 6]

plus "local" access port is no less secure than "public" port.  You can use the local port as your public port.   If you are hosting your server you will need to setup the firewall no matter what, you dont want the box hanging right on the internet backbone...  so when you setup the firewall just block everything but your emby port so DLNA and what not are not trying to be sent out to the internet.    

Thank you very much. i see the problem...

127.0.0.1 works with public ip and server domain

 

im plex user long years a go, now i see emby and i love it

I do not know emby yet. The only connect to the local port has made me a little afraid. I do not know if it is certain that the embry maybe sends public information or anything is visible from the outside

yes i disable DNLA on dedicated

Thank you pir8radio to help me 

Edited April 29, 2017 by Seimann

[Luke 38874]

If you don't have a router then the public port setting does nothing other than display on the front page of the server dashboard. So in that situation, it would be up to you to tell us why one port is working and the other isn't'.

[EliteCube 6]

Ok i have tested now. (Local IP 127.0.0.1 | Public IP 88.99.XX.XX)
If local port and public port are the same it works

If public port is different, it does not work ...

Example:
Local: 8080
Public: 80

I cant connect to emby with 80

Works only:
Public and Local Port 8080
Proxy 80 to 8080 forwarding and it works
(Or Public + Local 80 without proxy)

That was what frightened me. The local port is only accessible and the actual important port remote has no function
My idea was, for locally take any port and lock this in the firewall 2. open only the public. From the logical ..

Thanks guys

Edited April 29, 2017 by Seimann