0

I am wondering what might have gone wrong and how to fix it.

I upgraded Ubuntu from 16 to 18 on September 20th, 2018. I ended up having to re-install PHP at the time to allow proper function, but everything worked and the server was preforming well up until November 13th, 2018 (2 days ago).

The server had a few updates for security to be installed, so I allowed them to install as I do every 3 or so days. At that point, Apache2 went down and I couldn't figure out why so I ran a purge of the app and then reinstalled it. Then the server ran into issues with my virtual hosts listed in the apache2.conf file in this format:

Include /etc/apache2/sites-enabled/

#Virtualhosts
<VirtualHost *:80>
DocumentRoot /var/www
</VirtualHost>

<VirtualHost 111.11.1.111:80>
DocumentRoot /var/www/html/www.domain.com/public_html
ServerName www.domain.com
ServerAlias www.domain.com domain.com
<Directory “/var/www/html/www.domain.com/public_html”>
allow from all
Options +Indexes
</Directory>
HostNameLookups double
IdentityCheck on
</VirtualHost>

When I removed the statements in the Apache2.conf then Apache started up just fine.

The only error I get when running the Apache2 Service Status is that my server does not have a qualified domain name. Everything else passes. I do not think this would cause the issues I am having. I never gave it one to begin with as this is just a test server to see if I want to run my sites off of Ubuntu or not.

I then tried the sites, and not all of them worked so I looked further and found that one of the 3 sites were up so I know the virtual hosts are not functioning correctly. I looked to see what else was broken and found that PHP wasn't functioning, so I repaired it. PHP is now up and fixed, but I still have no virtual hosts available.

I have 3 files that are pointing to my domain.com.conf files in the sites-enabled folder but I still can't get Apache2 to function with them. Every time I try to add a virtual host statement into the Apache2.conf file it comes back as failed when it is restarted. Does the new version of Apache2 not support this?

Any pointers as to what is happening would be great. The server is not a production server yet, as I am making sure I can handle a Ubuntu server to handle our websites before I go live with them.

Also, is it better to just build a new Ubutnu server when upgrading or do most people just do the in-place upgrade on the server like I did when they upgrade to the newest version? Seems going from 16 to 18 wasn't worth it to me. A lot of little issues have popped up since I did this. I never had issues with 16.04, it was only after the in-place upgrade that these things started.

Thanks for any help, Ross

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.