This video demonstrates how to set up virtual hosting with Apache web server on Windows. Virtual Hosting makes it so Apache will respond to domain name reque…
Video Rating: 5 / 5
Virtual Web Hosting with Apache on Windows Part 2
Virtual Server Hosting Site
Virtual Servers, Technology and More
I’m getting “this website is temporatily unavailable” error. Please help.
Apache 2.4
Hi thanks for the nice video, i ran into the problem, both of my website
are going to site A how can i change where each of them goes to there
corresponding index page.. thanks
WTF indeed. Not sure what happened there. Windows Firewall? How did you
install it?
By default, Apache will use the first virtualhost defined if you visit the
server via IP address. The whole point is to use 1 public IP address and
host multiple websites using the domain name rather than the IP address. If
you have multiple public IPs, want to use them, but only have 1 server,
then that’s a different type of virtual hosting.
CincinnatiBell, my ISP, said it didn’t block port 80. I set 3 domain names
pointing to the same internal IP in the hosts file of the host PC including
the public domain. I also set the public domain pointing to the external IP
of my router in A Record. I can access the 3 sites on the host PC not from
any other PC. I don’t know how to port scan. Could you help me? Any help
appreciated. Thanks for quick reply.
Look in to a program called nMap, there’s a Windows version floating around
out there somewhere. Make sure that you disabled all profiles of the
Windows Firewall as well.
Good eye. A couple things to note that I probably should’ve mentioned. When
working with Windows, you will almost always be using but with Linux and
Mac, it’s /. Windows is also case INSENSITIVE while Linux and Mac are case
SENSITIVE. As seen at 1:20, you’ll notice that I’m using / despite the fact
that I’m on Windows. To be honest, I’m not sure why that even works, but I
must slap myself on the hand for that. Best practice is to use the
conventions for the appropriate operating system.
I’ve had issues with setting up virtual hosts, and my issue was that I was
also copying the directory path from the folder address bar, and windows
uses “backslash” in the path, but in Apache’s conf file, you can’t have
that. You have to have “forward slash.” It was fixed once I changed it. I
noticed you also had the issue in the beginning, but you didn’t mention
anything about it. In your video at 1:20 it can be seen that you have
changed to “forward slashes”
I got it to work but does siteb have an assigned IP Address? All my local
host IPs are assigned to site a not site b
Works Great for me, awesome tutorial! However i think a cool next step
would be to know how to connect to my website running off Apache from other
computers in the same network?
In Windows 7/8, and possibly Vista, there is a Home, Work, and Public
profile for the firewall. This is so you can have multiple different
“pre-sets” for the firewall depending on the location you pick. A public
network will be super paranoid, while a home network is more laxed, and the
work I believe is somewhere in between. Disabling all of these will disable
the firewall no matter where you are. Are you sure you forwarded the ports
correctly?
I used nmap and open-pot. Both showed port 80 is closed on my external IP.
I double checked with my ISP and was told no advise to close any port. Most
likely it is still my Firewall blocking port 80. I did turned off the
Firewall on my laptop though. what do u mean to disable all profiles of the
Windows Firewall as well? Do u mean disable all inbound rules? By the way,
I used wireless network.
Cincinnati Bell said it doesn’t block port 80. I set up 3 web domain point
to the same internal ip in hosts file of the host PC including a public
domain name . I don’t know how to do port scan. Could you please help me?
Any help appreciated.
I used nmap and open-pot. Both showed port 80 is closed on my external IP.
I double checked with my ISP and was told no advise to close any port. Most
likely it is still my Firewall blocking port 80. I did turned off the
Firewall on my laptop though. what do u mean to disable all profiles of the
Windows Firewall as well? Do u mean disable all inbound rules? By the way,
I used wireless network.
WTF??? 1:27:31 PM [Apache] Error: Apache shutdown unexpectedly. 1:27:31 PM
[Apache] This may be due to a blocked port, missing dependencies, 1:27:31
PM [Apache] improper privileges, a crash, or a shutdown by another method.
1:27:31 PM [Apache] Check the “/xampp/apache/logs/error.log” file 1:27:31
PM [Apache] and the Windows Event Viewer for more clues
With Virtual Hosting, the sites are referenced by domain over IP. If you
visit the site via IP address, you will always be taken to the first
virtual host defined in your conf file. If you want each site to have its
own IP address, you would need subinterfaces on the card, but you’re
defeating the purpose of virtual hosting really at that point.
Thank you!!, i was looking for information many hours and i couldnt resolve
the same problem u had, these videos were helpful!
Who is your ISP? Do you have a business account? One thing to note, and I
think I mentioned this on the video, is that a lot of ISPs will block
conventional server ports, such as 80, 443, 21, 110, 25, etc. in an effort
to get you to spend more money on their business plans. You could do a port
scan on your public IP address from outside your network to see if that may
be the culprit. From within your network, change the host file on a
computer with the domain and internal IP and test it.
I setup virtual web host in the way introduced in this video. It works but
only on the host computer. I can’t access the webpage from any other
computers either inside my network nor outsite computer. I registered a
public domain, pointed the public domain to the public IP address of my
router, then port forwarding to the host PC, I also turned off the window
fire wall on the PC. I still can’t access the website from any other
computers. Any advice to solve my problem?
I was getting the same error. In my case, I was able to trace it to the
Directory block in my VirtualHost definitions. Commenting out the directory
blocks allowed me to restart Apache. I don’t know what the fundamental
cause of the error was, and not sure how to include these
directory-specific directives for each virtual host.