Apache impossible de m'identifier avec .htaccess ?
Bonjour,
Mon serveur à grillé, j'ai du le changer, j'ai pris un Raspberry PI 3.
Je pas donc de Debian Wheezy à Debian Stretck et de PHP5 a PHP7 pour mon site internet local.
J'ai installé Lamp et configuré un accès .htaccess. (Apache 2.4.25 / PHP 7.0.30)
Suite à cette installation, je rencontre un problème de configuration avec apache :
Concernant l'accès protégé impossible de m'identifier quand le fenêtre d'identification s'affiche et me demande le login et le mot de passe quand je me connecte à ma page avec le navigateur du répertoire protégé.
Pour créer les mots de passes, j'ai utilisé pour le premier :
puis pour les suivant s:
ensuite j'ai fait un chown
Dans le dossier à protéger, j'ai placé les deux fichiers .htaccess et .htpasswd .
Fichier .htaccess
Fichier .htpasswd
Ma version de apache et de PHP
Mon fichier apache.conf
Mon fichier httpd.conf
Pouvez vous m'aider ?
Merci.
Mon serveur à grillé, j'ai du le changer, j'ai pris un Raspberry PI 3.
Je pas donc de Debian Wheezy à Debian Stretck et de PHP5 a PHP7 pour mon site internet local.
J'ai installé Lamp et configuré un accès .htaccess. (Apache 2.4.25 / PHP 7.0.30)
Suite à cette installation, je rencontre un problème de configuration avec apache :
Concernant l'accès protégé impossible de m'identifier quand le fenêtre d'identification s'affiche et me demande le login et le mot de passe quand je me connecte à ma page avec le navigateur du répertoire protégé.
Pour créer les mots de passes, j'ai utilisé pour le premier :
htpasswd -c -p /var/www/html/maison/N4/.htpasswd laurent
puis pour les suivant s:
htpasswd -p /var/www/html/maison/N4/.htpasswd test
ensuite j'ai fait un chown
sudo chown serveur:www-data /var/www/html/maison/N4/.htpasswd
Dans le dossier à protéger, j'ai placé les deux fichiers .htaccess et .htpasswd .
serveur@raspberrypi:~ $ ls -alh /var/www/html/maison/N4/
total 232K
drwxr-xr-x 15 serveur www-data 4,0K ao�t 22 21:56 .
drwxr-xr-x 12 serveur www-data 4,0K ao�t 22 08:19 ..
-rwxr----- 1 serveur www-data 4 juin 22 2014 compteur-n4.txt
drwxr-xr-x 2 serveur www-data 4,0K ao�t 22 08:19 construction
-rwxr-x--- 1 serveur www-data 77 juin 22 2014 div-admin.php
-rw-r--r-- 1 serveur www-data 14K juin 22 2014 div-contenu-accueil.php
-rwxr-x--- 1 serveur www-data 827 juin 22 2014 div-entete.php
-rwxr-x--- 1 serveur www-data 9,1K juin 22 2014 div-menu-deroulant.php
-rw-r--r-- 1 serveur www-data 949 juin 22 2014 div-pied.php
drwxr-xr-x 15 serveur www-data 4,0K ao�t 22 08:15 habitation
-rw-r--r-- 1 serveur www-data 167 ao�t 22 21:49 .htaccess
-rw-r----- 1 serveur www-data 17 ao�t 23 07:18 .htpasswd
-rwxr-x--- 1 serveur www-data 22K juin 22 2014 index.php
-rwxr-x--- 1 serveur www-data 1,1K juin 22 2014 style-page.css
-rwxr-x--- 1 serveur www-data 1,5K juin 22 2014 style-site.css
serveur@raspberrypi:~ $
Fichier .htaccess
serveur@raspberrypi:~ $ cat /var/www/html/maison/N4/.htaccess
AuthName "Accès Réservé"
AuthType Basic
AuthUserFile "/var/www/html/maison/N4/.htpasswd"
Require valid-user
serveur@raspberrypi:~ $
Fichier .htpasswd
serveur@raspberrypi:~ $ cat /var/www/html/maison/N4/.htpasswd
laurent:mlkjhg
test:qsdfgh
serveur@raspberrypi:~ $
Ma version de apache et de PHP
serveur@raspberrypi:~ $ apache2 -v
Server version: Apache/2.4.25 (Raspbian)
Server built: 2018-06-02T08:01:13
serveur@raspberrypi:~ $
serveur@raspberrypi:~ $ php -v
PHP 7.0.30-0+deb9u1 (cli) (built: Jun 14 2018 13:50:25) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.0.30-0+deb9u1, Copyright (c) 1999-2017, by Zend Technologies
serveur@raspberrypi:~ $
Mon fichier apache.conf
serveur@raspberrypi:~ $ cat /etc/apache2/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
#
# The directory where shm and other runtime files will be stored.
#
DefaultRuntimeDir ${APACHE_RUN_DIR}
#
# 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 all the user configurations:
Include /etc/apache2/httpd.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 denied
</Directory>
<Directory /usr/share>
AllowOverride None
Require all granted
</Directory>
<Directory /var/www/>
Options Indexes FollowSymLinks
AllowOverride None
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
Mon fichier httpd.conf
serveur@raspberrypi:~ $ cat /etc/apache2/httpd.conf
DirectoryIndex index.html index.htm index.xhtml index.php
ServerName debian.domain.tld
#ServerName localhost
#*************** .htaccess ************************
#mise en place d'un accès protégé htaccess dans le répertoire Fichiers
<Directory /var/www/html/Fichiers>
AllowOverride all
</Directory>
#mise en place d'un accès protégé htaccess dans le répertoire N4
<Directory /var/www/html/maison/N4>
AllowOverride All
</Directory>
#*************** Accès au disque ************************
# ----------------------------------------------------
# Alias pour les Documents
Alias /Documents "/home/serveur/Documents/"
<Directory "/home/serveur/Documents">
Options Indexes FollowSymLinks
AllowOverride all
Require all granted
</Directory>
# http://192.168.1.xx/Documents/
# ----------------------------------------------------
# Alias pour les vidéos
Alias /Videos /home/serveur/Vidéos/
<Directory "/home/serveur/Vidéos">
Options Indexes FollowSymLinks
AllowOverride all
Require all granted
</Directory>
# http://192.168.1.xx/Videos/
# ----------------------------------------------------
Pouvez vous m'aider ?
Merci.
A voir également:
- Apache impossible de m'identifier avec .htaccess ?
- Identifier appareil avec adresse mac - Guide
- Apache open office gratuit - Télécharger - Suite bureautique
- Identifiant et mot de passe - Guide
- Call identifier 2.08 - Télécharger - Téléphonie & Visio
- Identifier un tableau à partir d'une photo - Forum Loisirs / Divertissements
1 réponse
Bonjour,
Merci pour ce message détaillé, voici la procédure que j'adopte pour sécuriser un dossier (dans cet exemple,
Bonne chance
Merci pour ce message détaillé, voici la procédure que j'adopte pour sécuriser un dossier (dans cet exemple,
/usr/share/phpmyadmin). Je te laisse le soin de contrôler que ce que tu as fait est conforme.
Bonne chance