Second Hostname Not Loading on Apache Virtual Host

JaredBusch

@ajstringham said:

So I have my Ubuntu 14.04 server with two Apache virtual hosts. So far, I have been unable to get the second site to work. I have the virtual hosts file setup, Wordpress is extracted and the wp-config.php file is setup correctly. From what I can see, there is no difference, in terms of configuration, between ThanksAJ.com and the new site. Does anyone have any ideas as to what I could be missing? I can't for the life of me figure it out! When you try to go to the site, Chrome kicks out a "Server connection refused" error. Oh, and the virtual host is online. Thanks for the help!

A.J.

@ajstringham check my new post in the wordpress LEMP challenge. Not Ubuntu, but still may help.

scottalanmiller

Do you have the right details in the VirtualHost config?

thanksajdotcom

@scottalanmiller said:

Do you have the right details in the VirtualHost config?

Yes. Give me a sec and I'll post the two configs.

thanksajdotcom

Site 1:

*<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName www.example.com

    ServerAdmin webmaster@localhost
    ServerName thanksaj.com
    ServerAlias www.thanksaj.com
    DocumentRoot /var/www/thanksaj.com

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf

</VirtualHost>*

thanksajdotcom

Site 1 works btw.

thanksajdotcom

Site 2:

*<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName www.example.com

    ServerAdmin [email protected]
    DocumentRoot /var/www/builtbyart.com
    ServerName builtbyart.com
    ServerAlias www.builtbyart.com

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf

</VirtualHost>*

Site 2 does not work.

JaredBusch

If site 1 is also your default document root, that is why it is working, not because the virtual host is correct.

thanksajdotcom

That is the first line but the doing it in italics screwed it up.

thanksajdotcom

They each have a different document root. Each is in the appropriate website folder in /var/www

JaredBusch

@ajstringham said:

<VirtualHost *:80>

That is the first line but the doing it in italics screwed it up.

I use notepad++ to tab out an entire section i want to paste here then the nobebb detects it as code.

thanksajdotcom

@JaredBusch said:

@ajstringham said:

<VirtualHost *:80>

That is the first line but the doing it in italics screwed it up.

I use notepad++ to tab out an entire section i want to paste here then the nobebb detects it as code.

Yeah, I didn't realize it did that.

JaredBusch

@ajstringham my CentOS6.5 webserver has apache 2.2 ithink and when i setup this Centos7 server it is 2.4. I had to add the directory element to my existing virtual host info that i copy/pasted over to the new server.

		<Directory />
			Require all granted
			Options Indexes FollowSymLinks Includes ExecCGI
			AllowOverride All
			Order allow,deny
			Allow from all
		</Directory>

thanksajdotcom

@JaredBusch said:

@ajstringham my CentOS6.5 webserver has apache 2.2 ithink and when i setup this Centos7 server it is 2.4. I had to add the directory element to my existing virtual host info that i copy/pasted over to the new server.
  	<Directory />
  		Require all granted
  		Options Indexes FollowSymLinks Includes ExecCGI
  		AllowOverride All
  		Order allow,deny
  		Allow from all
  	</Directory>

It's all one server. Those settings are in a different Apache file than the virtual-hosts file.

thanksajdotcom

I have 3 files in my /etc/apache2/sites-enabled folder. 000-default.conf, builtbyart.com.conf, and thanksaj.com.conf. The default one has to be there. However, the actual virtual host is brought online when you run:

a2ensite builtbyart.com
a2ensite thanskaj.com

The site name must correspond to a .conf. So if I'm bringing thanksaj.com online, the file has to be thanksaj.com.conf.

thanksajdotcom

What I can't figure out is why ThanksAJ.com DOES work but BuiltByArt.com DOES NOT. They are configured exactly the same.

JaredBusch

Well I cannot help you as my webserver is a simple standard CentOS box with a clean apache install. All the settings are in /etc/httpd/conf/httpd.conf

thanksajdotcom

@JaredBusch said:

Well I cannot help you as my webserver is a simple standard CentOS box with a clean apache install. All the settings are in /etc/httpd/conf/httpd.conf

Yeah, the RPM-based system vs a Debian-based system.

JaredBusch

@ajstringham does not explain why apache config files are different. one would think that would work the same because it is apache not the OS.

thanksajdotcom

I have even tried redoing Wordpress.

EDIT: I just checked and had forgotten to redo Wordpress after deleting the old files...oops. Let's try that again..

thanksajdotcom

@JaredBusch said:

@ajstringham does not explain why apache config files are different. one would think that would work the same because it is apache not the OS.

True.