Apache2 : impossible d'accéder au localhost

Bonjour,

je viens d’installer apache2 sur une machine propre avec donc un debian neuf et à jour, et je rencontre un souci.
Il m’est impossible d’accéder à l’adresse localhost/, pourtant apache fonctionne bien il est bien lancé:

> service apache2 status Apache2 is running (pid 20175)
Le contenu de mon fichier /etc/hosts:

[code]127.0.0.1 localhost debian-ben
127.0.1.1 debian-ben
127.0.1.2 cakephp

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters[/code]

Pas de problème de port, comme indiqué ci dessous:

root@debian-ben:~# netstat -antp Connexions Internet actives (serveurs et établies) Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name tcp 0 0 192.168.0.21:41557 74.125.230.218:80 TIME_WAIT - tcp 0 0 192.168.0.21:39257 74.125.132.105:80 TIME_WAIT - tcp 0 0 192.168.0.21:56361 74.125.230.90:80 TIME_WAIT - tcp6 0 0 :::80 :::* LISTEN 3077/apache2

Mon fichier /etc/apache2/ports.conf :

[code]NameVirtualHost *:80
Listen 80

# If you add NameVirtualHost *:443 here, you will also have to change # the VirtualHost statement in /etc/apache2/sites-available/default-ssl # to # Server Name Indication for SSL named virtual hosts is currently not # supported by MSIE on Windows XP. Listen 443 Listen 443 [/code]

Mon fichier /etc/apache2/apache2.conf :

[code]#

Based upon the NCSA server configuration files originally by Rob McCool.

This is the main Apache server configuration file. It contains the

configuration directives that give the server its instructions.

See http://httpd.apache.org/docs/2.2/ for detailed information about

the directives.

Do NOT simply read the instructions in here without understanding

what they do. They’re here only as hints or reminders. If you are unsure

consult the online docs. You have been warned.

The configuration directives are grouped into three basic sections:

1. Directives that control the operation of the Apache server process as a

whole (the ‘global environment’).

2. Directives that define the parameters of the ‘main’ or ‘default’ server,

which responds to requests that aren’t handled by a virtual host.

These directives also provide default values for the settings

of all virtual hosts.

3. Settings for virtual hosts, which allow Web requests to be sent to

different IP addresses or hostnames and have them handled by the

same Apache server process.

Configuration and logfile names: If the filenames you specify for many

of the server’s control files begin with “/” (or “drive:/” for Win32), the

server will use that explicit path. If the filenames do not begin

with “/”, the value of ServerRoot is prepended – so “foo.log”

with ServerRoot set to “/etc/apache2” will be interpreted by the

server as “/etc/apache2/foo.log”.

Section 1: Global Environment

The directives in this section affect the overall operation of Apache,

such as the number of concurrent requests it can handle or where it

can find its configuration files.

ServerRoot: The top of the directory tree under which the server’s

configuration, error, and log files are kept.

NOTE! If you intend to place this on an NFS (or otherwise network)

mounted filesystem then please read the LockFile documentation (available

at URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile);

you will save yourself a lot of trouble.

Do NOT add a slash at the end of the directory path.

#ServerRoot “/etc/apache2”

The accept serialization lock file MUST BE STORED ON A LOCAL DISK.

LockFile ${APACHE_LOCK_DIR}/accept.lock

PidFile: The file in which the server should record its process

identification number when it starts.

This needs to be set in /etc/apache2/envvars

PidFile ${APACHE_PID_FILE}

Timeout: The number of seconds before receives and sends time out.

Timeout 300

KeepAlive: Whether or not to allow persistent connections (more than

one request per connection). Set to “Off” to deactivate.

KeepAlive On

MaxKeepAliveRequests: The maximum number of requests to allow

during a persistent connection. Set to 0 to allow an unlimited amount.

We recommend you leave this number high, for maximum performance.

MaxKeepAliveRequests 100

KeepAliveTimeout: Number of seconds to wait for the next request from the

same client on the same connection.

KeepAliveTimeout 15

Server-Pool Size Regulation (MPM specific)

prefork MPM

StartServers: number of server processes to start

MinSpareServers: minimum number of server processes which are kept spare

MaxSpareServers: maximum number of server processes which are kept spare

MaxClients: maximum number of server processes allowed to start

MaxRequestsPerChild: maximum number of requests a server process serves

StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0

worker MPM

StartServers: initial number of server processes to start

MaxClients: maximum number of simultaneous client connections

MinSpareThreads: minimum number of worker threads which are kept spare

MaxSpareThreads: maximum number of worker threads which are kept spare

ThreadLimit: ThreadsPerChild can be changed to this maximum value during a

graceful restart. ThreadLimit can only be changed by stopping

and starting Apache.

ThreadsPerChild: constant number of worker threads in each server process

MaxRequestsPerChild: maximum number of requests a server process serves

StartServers 2 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxClients 150 MaxRequestsPerChild 0

event MPM

StartServers: initial number of server processes to start

MaxClients: maximum number of simultaneous client connections

MinSpareThreads: minimum number of worker threads which are kept spare

MaxSpareThreads: maximum number of worker threads which are kept spare

ThreadsPerChild: constant number of worker threads in each server process

MaxRequestsPerChild: maximum number of requests a server process serves

StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxRequestsPerChild 0

These need to be set in /etc/apache2/envvars

User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

AccessFileName: The name of the file to look for in each directory

for additional configuration directives. See also the AllowOverride

directive.

AccessFileName .htaccess

The following lines prevent .htaccess and .htpasswd files from being

viewed by Web clients.

<Files ~ “^.ht”>
Order allow,deny
Deny from all
Satisfy all

DefaultType is the default MIME type the server will use for a document

if it cannot otherwise determine one, such as from filename extensions.

If your server contains mostly text or HTML documents, “text/plain” is

a good value. If most of your content is binary, such as applications

or images, you may want to use “application/octet-stream” instead to

keep browsers from trying to display binary files as though they are

text.

DefaultType text/plain

HostnameLookups: Log the names of clients or just their IP addresses

e.g., www.apache.org (on) or 204.62.129.132 (off).

The default is off because it’d be overall better for the net if people

had to knowingly turn this feature on, since enabling it means that

each client request will result in AT LEAST one lookup request to the

nameserver.

HostnameLookups Off

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a

container, error messages relating to that virtual host will be

logged here. If you do define an error logfile for a

container, that host’s errors will be logged there and not here.

ErrorLog ${APACHE_LOG_DIR}/error.log

LogLevel: Control the number of messages logged to the error_log.

Possible values include: debug, info, notice, warn, error, crit,

alert, emerg.

LogLevel warn

Include module configuration:

Include mods-enabled/.load
Include mods-enabled/
.conf

Include all the user configurations:

Include httpd.conf

Include ports listing

Include ports.conf

The following directives define some format nicknames for use with

a CustomLog directive (see below).

If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i

LogFormat “%v:%p %h %l %u %t “%r” %>s %O “%{Referer}i” “%{User-Agent}i”” vhost_combined
LogFormat “%h %l %u %t “%r” %>s %O “%{Referer}i” “%{User-Agent}i”” combined
LogFormat “%h %l %u %t “%r” %>s %O” common
LogFormat “%{Referer}i -> %U” referer
LogFormat “%{User-agent}i” agent

Include of directories ignores editors’ and dpkg’s backup files,

see README.Debian for details.

Include generic snippets of statements

Include conf.d/

Include the virtual host configurations:

Include sites-enabled/[/code]

Il n’y a rien dans le fichier httpd.conf.

En revanche j’ai essayé d’accéder à mon serveur depuis un autre PC en wifi, en me connectant à l’adresse du réseau local 192.168.0.21 de mon serveur sur lequel est installé apache, et là ça fonctionne bien, la page de test avec le “It works” s’affiche correctement et tout à l’air de fonctionner.
Alors pourquoi depuis mon ordi où est installé apache je n’arrive pas à obtenir ce même résultat? Je ne vais pas à la bonne adresse ? Ou bien y a t’il quelque chose de mal configuré quelque part?

Merci par avance!

Bonjour,

et si tu tapes 127.0.0.1

tu obtiens quel message ?

Exactement la même chose que quand je tape localhost/, c’est à dire rien :confused:

au lieu de

essaye avec

Vérifier également que l’interface lo soit bien activée

Ouais, et qu’elle a la bonne adresses 127.0.0.1 (et accessoirement ::1).
Et tant qu’on y est, que l’éventuel jeu de règles iptables ne bloque pas le trafic depuis et vers celle-ci.

Effectivement ton /etc/hosts je sais pas si ca se fait comme tu l’a fait.
Essayes ce que la personne précédente t’as proposé. ex:

127.0.0.1 localhost 127.0.1.1 gab1.chezgab.net gab1

Sinon, petite question:
pour l’utilisation de netstat, l’option -l ( = listenning = écouter ) n’est-elle pas utile lorsque justement tu veux voir si un programme (ex: apache dans ce cas ) écoute sur un port ?

Et donc , que donne

?

Quel est le message exact dans ton navigateur pour la page “localhost” ?

[quote=“Poutchoukou”]root@debian-ben:~# netstat -antp Connexions Internet actives (serveurs et établies) Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name tcp 0 0 192.168.0.21:41557 74.125.230.218:80 TIME_WAIT - tcp 0 0 192.168.0.21:39257 74.125.132.105:80 TIME_WAIT - tcp 0 0 192.168.0.21:56361 74.125.230.90:80 TIME_WAIT - tcp6 0 0 :::80 :::* LISTEN 3077/apache2[/quote]
Je sais pas si ça a un rapport avec ton problème, mais je crois pas que ça soit normal qu’apache n’écoute qu’en IPv6 pas en IPv4…
Du coup j’ai un peu de mal à comprendre comment 192.168.0.21 peut fonctionner à partir d’une autre machine puisque ça utilise IPv4. :017

Par défaut, une socket IPv6 TCP ou UDP en écoute sur l’adresse indéfinie (::slight_smile: accepte aussi les communications en IPv4. Ce comportement peut être désactivé au niveau des options de la socket par le programme qui l’a ouverte, ou globalement au niveau du système avec le sysctl net.ipv6.bindv6only.

Ah oui maintenant que tu le dis… J’aurais dû m’en rappeler de cette histoire pourtant vu que j’active systématiquement net.ipv6.bindv6only (rapport à un bug lié à Java dont je ne me rappelle plus les détails). :blush:
Au temps pour moi.

http://fr.wiktionary.org/wiki/autant_pour_moi :stuck_out_tongue:

Extrait de ton lien :

:teasing-neener:

Discussion close en ce qui me concerne, pas la peine de faire dérailler le sujet pour si peu. On peut continuer en MP si tu veux mais je ne vois pas ce qu’il y a à dire de plus de toutes façons. :wink: