You need to configure port forwarding in your router to the server IP, for all relevant ports (80, 25, 53 UDP, 110, 443, 995 and so on).
But there’s more to getting hosting behind a NAT router to work than forwarding ports. Setting up DNS properly is the biggest challenge. I think there’s a page with instructions about this somewhere on this website, Eric surely knows the link which I don’t.
Unfortunately, we won’t be able to help with your router configuration since each router is different. The key there is that you would need to configure the port forwarding for all the ports Locutus mentioned… your router should have documentation on how to do that.
After performing all the port forwarding, if things still aren’t working, what problem are you having exactly?
Note though that since you’re using NAT, you’d need to go into System Settings -> Virtualmin Config -> Network Settings, and in there, set “Default IP address for DNS records” to “Same as virtual server IP”.
That’s only a small piece of the puzzle though – if things aren’t working for you, you’ll have to give us lots of details about what isn’t working, what symptoms you’re seeing, any errors you’re getting, and what you’ve tried so far in order to resolve it.
My problem is i dont know how configure virtualmin for see the web in internet. If you can talk me about few ticks of how configure the virtualmin i apreciate this.
After i will see how configure the router. but i need configure first the virtualmin perfectly.
Did you perform the step I described above, going into System Settings -> Virtualmin Config -> Network Settings, and in there, set “Default IP address for DNS records” to “Same as virtual server IP”?
That’s the only step you should have to perform in Virtualmin.
If you’ve performed that step – can you describe what problem you’re having specifically?
Typically, a new server has Internet access… under most circumstances, you shouldn’t have to perform any steps to get Virtualmin to see the Internet.
Please describe what symptoms you’re seeing though, including any errors you’re receiving – that’ll enable us to provide the best help.
@mamb: In addition to what Eric said (we need more detailed problem descriptions!), what exactly do you mean with “see the web in internet”? Do you mean accessing the server from the outside, or providing internet access for the server? In both cases, please describe precisely what you tried and what did not work.
The hostname resolves correctly, but connect to port 80 on the IP 190.39.32.137 is not working.
In your first post you said Virtualmin detected the IP 10.0.2.10, but in your most recent one you said you forwarded to IP 192.168.1.100 in your router. You might want to make sure there’s no discrepany (i.e. Virtualmin is configured properly and what is the correct IP for your server).
Then double-check if the port forwarding to your server is correct. Also make sure Apache is running and listening on port 80 using netstat -tpln | grep :80
No, the 2495 is the process ID, not a port number.
Still, connect from the outside to your port 80 is not successful. So either the port forwarding in your router is not configured correctly, or some external or internal firewall is blocking access.
The latter you can check with iptables -L on your server. The former you need to check in your router’s config web interface, or with your internet service provider. The hosts that appear in the route to your IP (notably COMPANIA-ANONIMA-NACIONAL.POS6-0-0.ar1.MIA2.gblx.net followed by four hosts that don’t reply to traceroute), would suggest that some anonymizer or similar service is involved, which might block external access to your system.