can't access i-mscp admin pannel from remote machine over the internet

Hi All, I am not sure this is the right place, but I hope it is.

I just installed I-mscp on my debian 8 system. this system is running on a cloud instance on codero.com. Somehwere I read that this might be in issue running I-mscp on a virtualized system. my problem is the following.

So, after the setup process was complete, It said to open my browser, and go to https://adminhost.mydomain.com:4443. I went to this url from my computer at home via firefox, and I got a can't access this page error, 404.

I then opened a lynx session on themachine itself that I am running I-mscp, and went to the same url, the https://adminhost.mydomain.com:4443 and successfully loaded the login page for the imscp control panel.

I know it isn't an issue of dns since I can access that machine via the same address minus the port :4443. when I just goto http://adminhost.mydomain.com it opens the default server page for debian apache installations.

If anyone has any ideas on what I can check I would really appreciate it.

Thank you.

Hi,

the url I specified in my I-mscp setup was mercury.hostulator.com. The address that I have been trying to go is https://mercury.hostulator.com:4443.

So one thing I found is that since my instance I a virtual machine, it is on a private lan as well.

when I do a ifconfig, I get eth0 and eth1 devices.

eth0 inet addr = 10.244.0.210
eth1 inet addr = 10.144.11.38

my public ip is 68.168.99.252

from with the machine's shell prompt, if I do a ping mercury.hostulator.com I get back the ip addr from eth1.

if I ping the mercury.hostulator.com from my home Linux box, I get 68.168.99.252

so does this mean its behind a NAT wall?

How can I then get it so I can access what I need, and also make sure I-mscp related services work with this kind of setup?

Please let me know if there is any other information anyone needs.

Thank you in advance.