Sites not served after Precise - Trusty upgrade - new apache2 documentroot path

Bug #1308570 reported by Ryan Beisner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Expired
Low
Unassigned

Bug Description

An existing site is no longer online following a Precise to Trusty upgrade when the site is in the default DocumentRoot. This is because DocumentRoot on Trusty is now /var/www/html whereas it was /var/www for Precise.

There is a simple work-around for simple deployments: move the contents of /var/www to /var/www/html. More complex scenarios may require additional reconfiguration, such as anything else referencing these as absolute paths.

Tags: trusty
Changed in apache2 (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Joshua Powers (powersj) wrote :

I don't see this a bug, the default configuration changed (and yes it was annoying as heck). /var/www/html has been the default since Trusty now, I'm not sure there is any bug to solve here.

Changed in apache2 (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.]

Changed in apache2 (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Ryan Beisner (1chb1n) wrote :

@powersj - agree. At the time I raised this, Trusty was about to release, and the LTS-to-LTS upgrade story was about to be affected going into Trusty.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.