Virtual host files (one without .conf, all others with)
> agifforyou.com.conf -> ../sites-available/agifforyou.com.conf
benmillett.us -> ../sites-available/benmillett.us
benmillett.us.conf -> ../sites-available/benmillett.us.conf
blog.benmillett.us.conf -> ../sites-available/blog.benmillett.us
catlincurry.com.conf -> ../sites-available/catlincurry.com.conf
If I use a2dissite for benmillett.us, it leaves benmillett.us enabled and disables benmillett.us.conf.
If I change the name of sites-available/benmillett.us to sites-available/bm.us, then sites-enabled/benmillett.us shows up in red text and black highlighting and reload fails with "Job for apache2.service failed because the control process exited with error code."
I've updated benmillett.us to have the exact same text as benmillett.us.conf just to make sure that my site is serving up correctly.
Questions:
Should I care about benmillett.us and benmillett.us.conf both existing?
Do I really need benmillett.us.conf if I have benmillett.us?
Can I get rid of benmillett.us somehow and just rely on benmillett.us.conf?
5 Replies
If I were using sites-enabled I'd do like the following article suggests and keep them in a separate location and sym link them into sites-enabled/sites-available as appropriate:
I'd also try to make sure to not have redundant configurations.
@jebblue I had been following this guide that suggests creating files in the sites-available folder:
For now, I've disabled the benmillett.us.conf file so that only benmillett.us is still there.
@jeremye77 I tried making that change, with no luck. Thanks though. That was good to learn about.
@jebblue:
I can't tell from the chain, if the site(s) is/are still failing, check the Apache logs, see what's in there.