Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 25/04/2016, à 11:38

Hugo33

[Résolu] 403 sur Apache Ubuntu 16.04

Bonjour,

J'aimerai déplacer le dossier de travail de wamp sur ma nouvelle installation 16.04.
J'ai suivit ce tuto: https://elwan7.wordpress.com/2014/10/22 … ur-debian/

Seulement j'obtient une 403 quand j'essaie d'accéder a 127.0.0.1.

Voici mon /etc/apache2/sites-availible/000-default.conf:

<VirtualHost *: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 /home/hugo/sites

	# 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

	# 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

mon /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

#
# 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 denied
</Directory>

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

<Directory /home/hugo/sites/>
	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

le dossier en question se trouve a l'adresse: /home/hugo/sites

www-data est le propriétaire de ce dossier et les permissions sont en 775.

C'est bien une erreur de permissions:

[Mon Apr 25 12:26:11.933058 2016] [core:error] [pid 27856] (13)Permission denied: [client 127.0.0.1:58334] AH00035: access to / denied (filesystem path '/home/hugo/sites') because search permissions are missing on a component of the path

Quelqu'un a t'il une idée ?

Merci d'avance de vos réponses

Dernière modification par Hugo33 (Le 25/04/2016, à 13:23)

Hors ligne

#2 Le 25/04/2016, à 12:47

αjet

Re : [Résolu] 403 sur Apache Ubuntu 16.04

En faisant une petite recherche, je suis tombé sur ce cas similaire :
https://askubuntu.com/questions/451922/ … re-missing

Je pense que le compte apache (www-data) ne peux pas traverser ton dossier home.
Verifies les droits de ton dossier home:

ls -l /home | grep hugo

Ca devrait te retourner une ligne similaire a celle ci
drwxr-xr-x 18 hugo hugo 4096 Apr 25 13:39 hugo
Regarde les 3 derniers flags de controle d'acces, si le x est manquant (tu aurais r--), comme conseillé dans la réponse dans le lien ci dessus, tu devrais appliquer la commande ci dessous :

chmod +x /home/hugo

pour pouvoir traverser ce dossier.

Note que ça veut dire que n'importe quel utilisateur peut lister le contenu de ton dossier home ce qui peut causer un problème de sécurité/confidentialité s'il s'agit d'un pc partagé.

Dernière modification par αjet (Le 25/04/2016, à 12:49)


αjet: ça se prononce alfajet, bordel ! | GMT+1 | Viens poueter avec moi, bordel ! | Mes photos | Shaarli | Fluidbuntu-fr

Hors ligne

#3 Le 25/04/2016, à 13:17

abelthorne

Re : [Résolu] 403 sur Apache Ubuntu 16.04

Personnellement, plutôt que d'indiquer un dossier du genre /home/machin/site dans le virtualhost, je déclare /var/www/site et j'en fais un lien symbolique vers /home/machin/site. Je ne sais pas si c'est la bonne méthode mais ça fonctionne sans avoir besoin de régler des permissions particulières.

Hors ligne

#4 Le 25/04/2016, à 13:20

pires57

Re : [Résolu] 403 sur Apache Ubuntu 16.04

je déclare /var/www/site et j'en fais un lien symbolique vers /home/machin/site.

... moche


Utilisateur d'Archlinux, Ubuntu et Kali Linux
Administrateur système et réseau spécialisé Linux.
LinkedIn

Hors ligne

#5 Le 25/04/2016, à 13:23

Hugo33

Re : [Résolu] 403 sur Apache Ubuntu 16.04

αjet a écrit :

En faisant une petite recherche, je suis tombé sur ce cas similaire :
https://askubuntu.com/questions/451922/ … re-missing

Je pense que le compte apache (www-data) ne peux pas traverser ton dossier home.
Verifies les droits de ton dossier home:

ls -l /home | grep hugo

Ca devrait te retourner une ligne similaire a celle ci
drwxr-xr-x 18 hugo hugo 4096 Apr 25 13:39 hugo
Regarde les 3 derniers flags de controle d'acces, si le x est manquant (tu aurais r--), comme conseillé dans la réponse dans le lien ci dessus, tu devrais appliquer la commande ci dessous :

chmod +x /home/hugo

pour pouvoir traverser ce dossier.

Note que ça veut dire que n'importe quel utilisateur peut lister le contenu de ton dossier home ce qui peut causer un problème de sécurité/confidentialité s'il s'agit d'un pc partagé.

C'est parfait merci !

Hors ligne

#6 Le 25/04/2016, à 13:27

αjet

Re : [Résolu] 403 sur Apache Ubuntu 16.04

Cool smile


αjet: ça se prononce alfajet, bordel ! | GMT+1 | Viens poueter avec moi, bordel ! | Mes photos | Shaarli | Fluidbuntu-fr

Hors ligne