FW: Re: FW: Help with Virtual Hosting on Linux 3.2 / Ubuntu 12.04.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks, that worked.

 

I had multiple listen directives. I cleared httpd.conf ( tried some code and left it there accidentally ) and removed "listen 80" from sites-available/example.com VHost settings

 

Another thread advised the use of "restart" instead of "reload" in "service apache2 restart", which seemed to work.

 

There are obviously several ways to do vhosts. Are there advantages/disadvantages to this method? If it is relevant, I need to have multiple sites on this server, each with their own config, and some with their own SSL.

 

Thanks again,

 

Roy

 



-----Original Message-----
From: "Eric Covener" <covener@xxxxxxxxx>
Sent: Friday, April 25, 2014 10:29am
To: users@xxxxxxxxxxxxxxxx
Subject: Re: FW: Help with Virtual Hosting on Linux 3.2 / Ubuntu 12.04.4

On Fri, Apr 25, 2014 at 1:20 PM, Roy Hinkelman - Technical Services
<roy@xxxxxxxxxxxxxxxxxxx> wrote:
> This site, for 2.4, https://httpd.apache.org/docs/2.4/vhosts/name-based.html
> , says to "simply" put the VirtualHost info into httpd.conf. FireFox says
> "Unable to Connect"

Missing a Listen directive, or a firewall problem. Not related to
VirtualHost directive.

If your packaging of httpd uses a sites-available/sites-enabled
layout, use it. If not, put it in httpd.conf. The server doesn't
really care what ultimately gets included.


--
Eric Covener
covener@xxxxxxxxx

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux