WampDeveloper is set up by default to answer any requests that reach it (it does not block access to any websites), but those requests have to get to it first…
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 “@” part – “@” means base-domain).
Note that WampDeveloper’s “Local DNS” feature is purely for local use, and will not 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 Firewall port 80 and 443.
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 that up (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 “Apache HTTP Server” Inbound Rules that you see. These are automatically created by the Firewall when a new version of Apache is started.
Router Port Forward Port 80 and 443
Port-forward port 80 and 443 in Router (if using one).
If you are behind a Router (such as a typical wifi router/modem), make sure that you’ve logged into it (ex: http://192.168.1.1, username or password: admin), and have created 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 like “192.168.1.100″.
Otherwise, none of this will work as the router 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) to another LAN device/system unless you configure it to keep assigning the same LAN IP to the same server device/system.
Check ISP Blocking of Incomming Port 80 Requests
Make sure your ISP (internet provider) does not block incoming port 80 and 443.
Some ISP might be blocking incoming ports due to abuse, hacking, and spam issues on their networks. Sometimes you can call in and get them to open that up for you (for a fee, or tech level-up).
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…
http://anonymouse.org/anonwww.html
It’s a free anonymous browsing service that will proxy the request using different servers throughout the world.
It’s a bit slow, but if you get “Error – Timeout” eventually, the request was not able to reach your server.