Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1013
  • Last Modified:

Using WAMP, accessing website from Internet I get a WAMP configuration page??

I am trying to help a client with a website setup by an employee who no longer works there. The site is on an internal "server" running WAMP. They used a free dns redirect to point a domain name to the company's public static IP. It's been working like a champ for years. (The free dns service was everydns.net, which was acquired by dyndns.org. They sent notices by email that no-one saw b/c employee was gone. Now Dyndns controls the dns for the domain and we can't contact them in any way because we don't have a paid account)

SO... I used another domain name and created "intranet.newdomain.com" and had the hosting company point web requests to the public IP. (the router is properly set up to forward port 80)

-The site (a front end for a database) is accessible from the LAN side using "domain-intranet.com" because we have manually entered that name into host files on the local PCs.
-"domain-intranet.com" points to 192.168.2.2 in the hosts file.
-but if I enter "192.168.2.2" or "http://192.168.2.2" in a web browser on a local PC I get this WAMP configuration type of page. (I'll attach a picture)
-I also get that "WAMP page" when I use the new "intranet.newdomain.com"  OR when I use the public IP address. (I've tried to add port 80 ":80" to the end of the ip address also.

So, to sum up, I know the site is running because it's accessible from the LAN side using the hosts file and old domain name. But if I use the new domain from the WAN side, or WAN IP from outside or LAN IP from inside, it doesn't work.
0
RickNCN
Asked:
RickNCN
  • 2
  • 2
1 Solution
 
RickNCNAuthor Commented:
WAMP config page comes up instead of our website
0
 
xtermCommented:
I'm not familiar with WAMP, but being a LAMP guy, I think I know what is happening.  Apache needs to know for any given site (if its not the "default" site on that machine) what names it will be accessed by.

So you will need to open httpd.conf (or whatever the WAMP equivalent is) on the server side, and find the VirtualHost for this site and add "ServerAlias intranet.newdomain.com" to that host and restart Apache.

This is pretty much the reason it doesn't work by IP either - if you're doing name-based virtual hosting, you have to access each site by its name.  The exception is that (this is true in the Unix environment, anyway) generally the FIRST listed host, or the standard DocumentRoot will be what gets displayed when accessing the system by IP.  If the system DocumentRoot doesn't contain any content (like an index.html) then you will see the generic Apache screen, which is what I believe you're seeing the WAMP equivalent of.


0
 
RickNCNAuthor Commented:
Bingo! That did it. Simple as can be. I knew I was missing a little part. Not being familiar with it I probably wouldn't have found it. Thanks
0
 
xtermCommented:
You're most welcome, and for what its worth, that is not obvious - a lot of people stumble on it.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now