New emby server setup - cannot connect to server internally

[teiva 18]

Setup:

Ubuntu Server 16.04

Docker 1.12.2

Windows 10 client (Putty)

 

I'm a Linux/Docker newbie. I ping'd my server from Windows to get the internal server IP. 

 

http://[ubuntu server internal IP]:8096

http://[ubuntu server internal IP]:8920

 

Both requests resulted with 'refused to connect' by Chrome. Does my emby server have a different IP from the Ubuntu server since it lives within a docker container? Is there some firewall on the ubuntu server that I need to turn off? If so how? Do I need to complete emby setup via CLI on the server before I can hit it remotely? 

 

Thanks, 

Linh

[mastrmind11 717]

Setup:

Ubuntu Server 16.04

Docker 1.12.2

Windows 10 client (Putty)

 

I'm a Linux/Docker newbie. I ping'd my server from Windows to get the internal server IP. 

 

http://[ubuntu server internal IP]:8096

http://[ubuntu server internal IP]:8920

 

Both requests resulted with 'refused to connect' by Chrome. Does my emby server have a different IP from the Ubuntu server since it lives within a docker container? Is there some firewall on the ubuntu server that I need to turn off? If so how? Do I need to complete emby setup via CLI on the server before I can hit it remotely? 

 

Thanks, 

Linh

Generally the container will have it's own IP but docker will modify the iptables of the server to make that fact transparent (ie, it'll do all the bridging itself).  Did you make sure Emby was up?  What happens if you curl hostip:8096 on the box itself?

[teiva 18]

You're right. I totally spaced. Emby wasn't started.  Thank you!