Ubuntu-fr

joris.remandet

Site inaccessible depuis un poste en local Apache 2.4

Salut à tous,

Je viens de reprendre l'installation d'un serveur WEB LAMP (Apache / MySQL / PHP) sur un Ubuntu 16.10 avec l'utilisation de wordpress

Voici le souci que je rencontre :

J'ai placé les fichiers de Wordpress dans /var/www/html (logiquement qui est le directoryroot de apache)
Je peux accèder au site directement en tapant localhost sur la machine hôte, et j'arrive sur la page que j'ai crée avec Wordpress

Quand j'essaye d'accèder à mon serveur via un autre poste du réseau local, je fais comme ceci : http://10.39.250.254/ (pas besoin de cacher l'adresse IP ), et la on me dit que le localhost à refusé l'accès
Par contre, quand je fais http://10.39.250.254/index.php : la je peux accèder à ma page Web, mais le thème de Wordpress n'apparaît pas.

Pour être tranquille j'ai coupé UFW et même constat, avant je me rappelle qu'il fallait ajouter dans un fichier de config apache le fameux "allow from all", mais j'ai essayé ça ne fonctionne pas ..

D'après vous, cela vient de la configuration d'apache ? je connaissait bien apache 2.2 mais ils ont tout changer, et même dans la doc technique d'apache c'est pas expliqué (du moins pas correctement)

Merci de votre aide

---

Portable : Dell Inspiron 17 5748 , Intel Core i5 4510U, SSD Samsung 840 Pro 256 GB, 8 Go de RAM DDR3, Intel HD 4400 / NVIDIA GeForce 840M 2Go (avec Optimus)
Possession d'un Raspberry Type B pour un serveur FTP

bruno

Re : Site inaccessible depuis un poste en local Apache 2.4

Il faudrait voir ta configuration d'Apache, au moins l'hôte virtuel que tu utilises.
Mais a priori ce n'est pas un problème avec Apache mais avec Wordpress ou le fichier .htaccess (généré par Wordpress) à la racine du site. Pour quelle domaine (ou adresse IP si tu n'as pas de domaine) est configuré ton Wordpress ?

joris.remandet

Re : Site inaccessible depuis un poste en local Apache 2.4

Wordpress est configuré avec l'adresse IP de mon serveur, est-ce-que tu veux que je poste ma config d'apache et celle de Wordpress ?

Edit : fichier Apache2.conf :

# 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.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# 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 Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# 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.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# 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 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# 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 <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all granted
    Allow from all
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
	Allow from all
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Allow from all
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# 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.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
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
IncludeOptional conf-enabled/*.conf

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

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

Fichier 000-default :

<VirtualHost _default_:80>
        # The ServerName directive sets the request scheme, hostname and port that
        # the server uses to identify itself. This is used when creating
        # redirection URLs. In the context of virtual hosts, the ServerName
        # specifies what hostname must appear in the request's Host: header to
        # match this virtual host. For the default virtual host (this file) this
        # value is not decisive as it is used as a last resort host regardless.
        # However, you must set it for any further virtual host explicitly.
        #ServerName www.example.com

ServerAdmin webmaster@localhost
DocumentRoot /var/www/html

        # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
        # error, crit, alert, emerg.
        # It is also possible to configure the loglevel for particular
        # modules, e.g.
        #LogLevel info ssl:warn

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined
ServerName 10.39.250.254

        # For most configuration files from conf-available/, which are
        # enabled or disabled at a global level, it is possible to
        # include a line for only one particular virtual host. For example the
        # following line enables the CGI configuration for this host only
        # after it has been globally disabled with "a2disconf".
        #Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

Dernière modification par joris.remandet (Le 31/03/2017, à 11:24)

---

Portable : Dell Inspiron 17 5748 , Intel Core i5 4510U, SSD Samsung 840 Pro 256 GB, 8 Go de RAM DDR3, Intel HD 4400 / NVIDIA GeForce 840M 2Go (avec Optimus)
Possession d'un Raspberry Type B pour un serveur FTP

bruno

Re : Site inaccessible depuis un poste en local Apache 2.4

Dans 000-default.conf il faut ajouter :

…
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html

<Directory /var/www/html>
    Options -Indexes +FollowSymLinks +MultiViews
    AllowOverride all
    Require all granted
</Directory>
…

et recharger la configuration :

sudo service apache2 reload

joris.remandet

Re : Site inaccessible depuis un poste en local Apache 2.4

J'ai bien ajouté ceci dans le 000-default, mais j'ai malheureusement toujours le même soucis

Quand je saisis l'adresse IP de mon serveur sur un poste en local, il passe sur localhost, alors que normalement il devrait pas passer sur localhost, il devrait bien rester sur l'ip de mon serveur, j'ai l'impression que Apache refuse l'accès, et que du coup il indique que le serveur est sur le localhost qui demande l'accès..

Dernière modification par joris.remandet (Le 31/03/2017, à 12:16)

---

Portable : Dell Inspiron 17 5748 , Intel Core i5 4510U, SSD Samsung 840 Pro 256 GB, 8 Go de RAM DDR3, Intel HD 4400 / NVIDIA GeForce 840M 2Go (avec Optimus)
Possession d'un Raspberry Type B pour un serveur FTP

bruno

Re : Site inaccessible depuis un poste en local Apache 2.4

Est-ce que le comportement est le même sur tous les postes du réseau local ?
Normalement si tu saisis une adresse IP dans la barre d'adresse du navigateur (http://10.39.250.254) cela doit fonctionner sans qu'il n'y ait de changement dans la barre d'adresse.
Si la barre d'adresse se modifie automatiquement pour afficher http://ocalhost c'est que quelque chose sur ce poste redirige automatiquement 10.39.250.254 vers localhost.

joris.remandet

Re : Site inaccessible depuis un poste en local Apache 2.4

Aaaah attends, je viens de tester sur mon téléphone portable, et en saisissant l'adresse du serveur j'attéris bien sur la page WEB en question que j'ai fais avec Wordpress, donc j'ai l'impression que ça viens de mon poste en question (qui est sous Windows 10)

---

Portable : Dell Inspiron 17 5748 , Intel Core i5 4510U, SSD Samsung 840 Pro 256 GB, 8 Go de RAM DDR3, Intel HD 4400 / NVIDIA GeForce 840M 2Go (avec Optimus)
Possession d'un Raspberry Type B pour un serveur FTP