Allowing Customers To Access there Control Panel

5 posts / 0 new
Topic locked
Last post
#1 Thu, 12/23/2010 - 19:47
wilsonsworldlimited

Allowing Customers To Access there Control Panel

I have set up webmin and virtual min PRO on my server but for some reason i can get the control panel to work properly so that my customers can access from there computers

i have a dynamic ip address so i set up a host with NO-IP and they seem to be working fine

wilsonsmedia.zapto.org and wilsonsmedia2.zapto.org

i have also set up my site which is working perfect

the only way i can access my control panel from another computer in the office is by using the server address 192.168.1.104 which is unreachable for customers

How is it possible for me to change this so that customers can access there control panel and ftp ect were ever they are

Please Help Me

Regards

Thu, 12/23/2010 - 20:01
Locutus

Does the Vmin host have a public (e.g. Internet routable) IP address, or only a private one?

In the latter case, you need to create port forwardings in your router for the ports Vmin uses, that'd be 10000 (default) for the control interface, 21 for FTP, 25 for SMTP, 110 for POP3 etc. (Be aware that FTP through a router is more complicated than just forwarding port 21.)

Thu, 12/23/2010 - 20:10
wilsonsworldlimited

Hello thanks for your reply the Vmin is showing a mixture of private and public ip addresses, like wilsonhosting.com in the virtual server is showing a private ip (192.168.1.104) however because the ns records are set to the external ip it is showing up on internet perfact but when i was testing services on laptop i could put in wilsonsmedia.zapto.org:10000 and it would work fine, however since i have put the software on the server is comes up with nothing the only way i can access the control panel is threw https://192.168.1.104:10000

Thu, 12/23/2010 - 20:18
wilsonsworldlimited

ok i open port 10000 and it brings up a bad request and a link to https://ibm-7ffa209f07c.home:10000/

this link is not usable for my customers

Fri, 12/24/2010 - 04:32
Locutus

I suppose this ".home" hostname is something that your local nameserver generates for the RDNS lookup of the internal IP address.

You can safely ignore this link and message, and tell your customers to browse to "https://your-external-ip-or-hostname:10000". If the port forwarding is active, that will work regardless of http or https.

Topic locked