Vhost file not see on debian about breeder

[alessandro-fazzi]

Hmmm...sounds strange: I work and I've worked for years with debian servers, but I can't find where that line could be...

In all my /etc/apache2/apache2.conf the inclusion is at the EOF and looks like

# Include generic snippets of statements
Include conf.d/

# Include the virtual host configurations:
Include sites-enabled/

Overall no one of my vhosts has a .conf extension and the inclusion is never optional.

Could you tell me where have you found that config, what version of Debian are you running, if you have installed apache from the repositories or compiled or whatever, ecc. ecc.? I'll be glad to investigate a bit

[Mte90]

I'm using debian sid.
i have downlaoded the deb for check the apache2.conf http://packages.debian.org/sid/apache2
I don't know if the problem exist because i use apache 2.4.* instead of 2.2.* :-/
This is the content:

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf```

[alessandro-fazzi]

Could you paste the output of apt-cache policy apache2, please?

[Mte90]

no problem :-)

  Installato: 2.4.6-3
  Candidato:  2.4.6-3
  Tabella versione:
 *** 2.4.6-3 0
        500 http://mi.mirror.garr.it/mirrors/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

[alessandro-fazzi]

Ok, reading comments in apache2.conf from apache2.4:

#   /etc/apache2/
#   |-- apache2.conf
#   |   `--  ports.conf
#   |-- mods-enabled
#   |   |-- *.load
#   |   `-- *.conf
#   |-- conf-enabled
#   |   `-- *.conf
#   `-- sites-enabled
#       `-- *.conf

while it was

#   /etc/apache2/
#   |-- apache2.conf
#   |   `--  ports.conf
#   |-- mods-enabled
#   |   |-- *.load
#   |   `-- *.conf
#   |-- conf.d
#   |   `-- *
#   `-- sites-enabled
#       `-- *

So, yes: we should expect some changes...I think it shouldn't be a problem to adapt breeder to write .conf files, since they would be compatible with older apache2.2 installations. I'll mark this issue as "enhancement" and I'll push something; probably later this week.

[Mte90]

no problem :-)

[Mte90]

any news?

[Flimmer1970]

I had the same problem, caused by a wrong directive in 000-default.conf.
Check with systemctl status apache2.service -l

[Mte90]

this problem exist