On Mon, Jun 10, 2013 at 5:52 PM, David Galligani <[email protected]> wrote:
> > Hi > > > >> What if you try to navigate to localhost:80/bloodhound while running >> Bloodhound on port 8080? Do you still see the directory listing? >> > Yes I can I have to assume then, that somewhere in `/etc/apache2` there is a site configuration for serving /var/www on port 80. Your output from scanning the ports backs that up. If it is not in /etc/apache2/sites-enabled, then maybe it is in /etc/apache2/apache.conf or /etc/apache2/httpd.conf? Do you have a /etc/apache2/sites-common directory? Garry suggested to me that you run: grep -r "/var/www" /etc/apache2/ and post the output here. > We could check that Apache is actually the webserver running on Port 80, >> either by stopping Apache and checking if the default page can still be >> seen at http://localhost or `$ sudo netstat -tulpn | grep 80`. >> Though, >> you'd probably see an error when starting Apache if there was another >> server running on that port. >> > I got this > tcp6 0 0 :::8000 :::* LISTEN > 20278/apache2 > tcp6 0 0 :::80 :::* LISTEN > 20278/apache2 > > > >> If you want to jump on the IRC channel, we might be able to sort this out >> more quickly, >> > Yes , thanks :) but maybe this way all those info could be useful to > someone else in the future ... > In the IRC would be more quick , but It would help just me > ( and maybe noone else in the future will bug you with the same question > anymore , lol ! ) > What do you think ? > Either way is fine. If we switch to IRC, we can always summarize our findings here.
