Enabling Online and Internet Access of Websites For WAMP Server

Apache under most WAMP servers does not block internet access to any websites by default, and does not require additional configurations to enable outside and external access of websites.

If your websites are not reachable from the internet, and the request times out in your Browser (e.g., you get a blank screen), then those requests were not able to reach Apache…

Update DNS Records

Make sure your domain name resolves to your Public IP address. You can get this IP address from multiple websites (google: whats my IP), and it will also be displayed in your Router’s settings.

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).

Be aware that DNS changes can take 30 minutes to be implemented by the Registrar’s system, and then another 30 minutes to fully propagate to the ISP level, but usually the changes are in effect after 5-30 minutes.

* If using WampDeveloper Pro, click the Public IP address button in System Tab to display your Public IP address. Also note that WampDeveloper’s “Local DNS” feature is purely for local use, and will not enable or affect outside DNS.

Assign Domain Name or IP Address to Website

Make sure this Apache hosted website has a DNS-resolved domain-name (ex: www.example.com) set as its Primary Domain Name:
VirtualHost: ServerName www.example.com

And if accessing this website directly via the IP address, the IP address set as one of its Domain Aliases:
VirtualHost: ServerAlias example.com 192.168.1.101 and.public.ip.address.here

Also, if you are accessing this website via a Domain Alias such as the IP address, make sure that all ‘redirects’ from Domain Aliases back to Primary Domain Name are turned Off, or you’ll get redirected back to the Primary Domain Name which might not even be registered/real, nor have the needed DNS records set up for it. Check the website’s HTTP and HTTPS (SSL) VirtualHost files and the .htaccess file for any relevant Redirect lines or RewriteRule lines.

* If using WampDeveloper Pro, to disable redirects, select your website in Website’s Tab, and de-select: Forward To Primary – All Aliases.

Open Windows Firewall for Ports 80 and 443

Your Windows Firewall (native, comes with the OS) will block all incoming port 80 (HTTP) and 443 (HTTPS) requests by default.

You’ll need to open ports 80 and 443, for both TCP and UDP packets.

Open the Windows Firewall (with full interface) by running WF.msc, 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 rules are automatically created by the Firewall when a new version of Apache is started for the first time.

* If using WampDeveloper Pro, click the “Firewall” button in System Tab to open the Windows Firewall in full mode.

Port Forward Ports 80 and 443 in Router

Port-forward ports 80 (HTTP) and 443 (HTTPS) in Router (if you’re using one).

If your WAMP server is 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 port 443 to the LAN IP of the server.

To find the system’s LAN IP, open the command-line by running cmd.exe, and execute command: ipconfig

Wireless LAN adapter Wireless Network Connection:
   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::xxx
   IPv4 Address. . . . . . . . . . . : 192.168.1.17
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

The LAN IP is the “IPv4 Address” of the “Connection”, and 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).

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).

Without the “port-forward” rules, the requests coming in on those ports will never reach Apache because the Router is 1) assigned by the ISP the Public IP address (since it’s the first device on the network), and 2) will not know what to do with those incoming requests – to which LAN IP to forward them to.

* If using WampDeveloper Pro, the LAN IP is displayed in System Tab.

Check ISP Blocking of Incoming Port 80 Requests

Make sure your ISP (Internet Service 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…

http://anonymouse.org/anonwww.html

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.

Other Issues

When accessing your WAMP server from outside, if you receive a 404 / “Not Found”, a 403 / “Forbidden”, or some other error code / message, then the request did reach Apache. And the issue is not with online access, but with something else that has to do with Apache’s configuration for this website.