Apache under most WAMP setups does not block internet access to any websites, and does not require additional configuration to enable internet access of websites.
If your websites are not reachable from the internet, and the request times out in your Browser (and you get a blank screen) – those requests were not able to reach Apache…
Update DNS Records
Make sure your domain name resolves to the IP address that you see when you click the Public IP address button in System Tab.
You’ll need to use your Registrar’s (GoDaddy, Namecheap, etc) DNS system and set up an “A” record to resolve your domain name to your public IP address for both the “www” and “@” parts (“@” means base-domain).
Note that WampDeveloper’s “Local DNS” feature is purely for local use, and will not enable or affect outside DNS.
Also note that DNS changes can take a few hours to propagate.
Assign Domain Name or IP to Website
Make sure this WampDeveloper hosted website has the above DNS-resolved domain-name (www.example.com) set as it’s Primary Domain Name, and (if accessing this website directly via the IP address) the IP address set as one of it’s Domain Aliases (in Websites Tab).
Also, if you are accessing this website via a Domain Alias such as the IP address, make sure to de-select: Forward To Primary – All Aliases, or you’ll just get redirected back to the Primary Domain Name (which might not even be registered/real, nor have proper DNS set up).
Open Windows Firewall
Open incoming port 80 and 443 in the Firewall.
Your Windows Firewall (native, comes with OS) will block all incoming port 80 (HTTP) and 443 (HTTPS) requests (both TCP and UDP packets). You need to open port 80 and 443, for both TCP and UDP packets.
Click the “Firewall” button in WampDeveloper’s System Tab. Select “Inbound Rules”, then “New Rule…”, Port, and fill in the proper info.
Also delete any blocking “Apache HTTP Server” Inbound Rules that you see. These are automatically created by the Firewall when a new version of Apache is started for the first time.
Port Forward Port 80 and 443 of Router
Port-forward port 80 and 443 in Router (if you’re using one).
If your WAMP setup is behind a Router (under a typical wifi router/modem home setup), you’ll need to login into the Router (ex: http://192.168.1.1, username or password: admin), and create a “port-forward” entry for port 80 and 443 to the LAN IP of the server.
The LAN IP is listed in WampDeveloper’s System Tab. It’s usually something similar to “192.168.1.100″ (but can also be of the form 172.16.x.x or 10.x.x.x).
Otherwise, none of this will work as the Router is 1) assigned (by the ISP) the Public IP address since it’s the first device on the network, and 2) must know what to do with incoming requests – to which LAN IP to forward them to.
Also, your Router might re-assign the local LAN IP (not to be confused with the Public IP) from time-to-time to another LAN device/system unless you configure it to keep assigning the same LAN IP to the same computer (by assigning the LAN IP only to the computer that has a specific MAC address).
Check ISP Blocking of Incoming Port 80 Requests
Make sure your ISP (internet provider) does not block incoming ports 80 and 443.
Some ISPs might block incoming ports due to abuse, hacking, and spam issues on their networks. Sometimes you can call in and get them to open those ports for your account (sometimes for a fee, sometimes via a tech level-up, and almost always if switched to a business account).
Though most of the time when they say they are not blocking incoming port 80, in reality they are.
You can check port 80 and your website externally by using this proxy…
It’s a free anonymous browsing service that will proxy the request using different external servers throughout the world.
It’s a bit slow, but if you get the message “Error – Timeout” eventually, the request was not able to reach your server.
If your ISP is blocking port 80, run the website on a different port.