Sites not served after Precise - Trusty upgrade - new apache2 documentroot path
Bug #1308570 reported by
Ryan Beisner
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.
Changed in apache2 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
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.