iansavell
November 26th, 2015, 05:09 PM
Last night I decided to upgrade my Ubuntu 12 LTS test server, evidently to Ubuntu 14.04.3 LTS. Throughout the update I selected the default of keeping the existing configuration files when asked. I don't recall being asked about any Apache files, and those appear to be new. Apache2 is now version 2.4.7.
After the upgrade none of the websites on that test server, which were all name virtual hosts, worked. Even the "default" website didn't (doesn't) work. All attempts to access the web server land in /var/www and show a directory listing of /var/www (which obviously it claims is /) including an html folder, which is where the default Apache2 page is now (it was in /var/www before the upgrade). sites-enabled/000-default.conf says the default document root should be /var/www/html but that clearly isn't happening. I've now stripped out all my virtual hosts except for 000-default to narrow the options. I did earlier note the requirement that virtual host configuration files now have to have a .conf extension but making that change (the new 000-default file was already .conf) had no noticeable effect.
I must have made some really obvious mistake and need to understand it rather than just starting again from scratch, the whole purpose of upgrading was to see what would happen if I upgraded my production server. I've been running this for several years and never broken the server with previous upgrades, clearly I've been getting cocky!
Ideas?
After the upgrade none of the websites on that test server, which were all name virtual hosts, worked. Even the "default" website didn't (doesn't) work. All attempts to access the web server land in /var/www and show a directory listing of /var/www (which obviously it claims is /) including an html folder, which is where the default Apache2 page is now (it was in /var/www before the upgrade). sites-enabled/000-default.conf says the default document root should be /var/www/html but that clearly isn't happening. I've now stripped out all my virtual hosts except for 000-default to narrow the options. I did earlier note the requirement that virtual host configuration files now have to have a .conf extension but making that change (the new 000-default file was already .conf) had no noticeable effect.
I must have made some really obvious mistake and need to understand it rather than just starting again from scratch, the whole purpose of upgrading was to see what would happen if I upgraded my production server. I've been running this for several years and never broken the server with previous upgrades, clearly I've been getting cocky!
Ideas?