错误消息“禁止您没有访问此服务器上的权限/” [关闭]


520

我已经自己配置了Apache,并尝试在虚拟主机上加载phpMyAdmin,但收到了以下信息:

403禁止访问您没有访问此服务器上的权限

我的httpd.conf

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# 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.  
#
# 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 "logs/foo.log"
# with ServerRoot set to "C:/Program Files (x86)/Apache Software Foundation/Apache2.2" will be interpreted by the
# server as "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which httpd.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/Program Files (x86)/Apache Software Foundation/Apache2.2"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 127.0.0.1:80

Include conf/vhosts.conf

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule php5_module "c:/Program Files/php/php5apache2_2.dll" 

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin webmaster@somenet.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.somenet.com:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# 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 "logs/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

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "logs/access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access.log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.somenet.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: 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

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml

    AddType application/x-httpd-php .php 
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.somenet.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

PHPIniDir "c:/Program Files/php" 

和vhosts.conf:

NameVirtualHost 127.0.0.1:80

<VirtualHost 127.0.0.1:80>
    DocumentRoot i:/projects/webserver/__tools/phpmyadmin/
    ServerName dbadmin.tools
</VirtualHost>

http文件夹有哪些权利,谁拥有它?
奥利弗(Oliver)

它在Windows 7下的本机上,您指的是什么文件夹?我:/ projects / webserver / __ tools / phpmyadmin /?
Dmytro Zarezenko 2012年

是的,apache作为用户守护程序运行。该用户是否有权读取文件?
奥利弗(Oliver)

是的,我在管理员下
Dmytro Zarezenko 2012年

4
检查您是否没有要.htaccess覆盖的文件以拒绝您尝试访问的文件(在目录中)
Ujjwal Singh

Answers:


662

2016年10月更新

4年前,由于该答案被许多人用作参考,并且这些年来我从安全性角度学到了很多东西,所以我觉得我有责任澄清一些重要说明,并相应地更新了我的答案。

原始答案是正确的,但对于某些生产环境而言并不安全,此外,我还要解释一些在设置环境时可能会遇到的问题。

如果您正在寻找一种快速的解决方案,而“安全性不重要”,即开发环境,请跳过并阅读原始答案

许多情况下可能导致403 Forbidden


A.目录索引(来自mod_autoindex.c

当你访问一个目录,有此目录中没有发现默认的文件 阿帕奇Options Indexes不在此目录已启用。

A.1。DirectoryIndex选项示例

DirectoryIndex index.html default.php welcome.php

A2。Options Indexes选项

如果设置,则apache将列出目录内容(如果未找到默认文件)(来自上述👆🏻选项)

如果以上条件都不满足

您将收到403 Forbidden

推荐建议

  • 除非确实需要,否则您不应允许目录列表。
  • 将默认索引限制DirectoryIndex为最小值。
  • 如果要修改,则仅将修改限制在所需的目录中,例如,使用.htaccess文件或将修改内容放入<Directory /my/directory>指令中

B. deny,allow指令(Apache 2.2)

@Radu在评论中提到了@Simon A. Eugster 您的请求被这些指令拒绝,列入黑名单或列入白名单。

我不会发表完整的解释,但是我认为一些示例可以帮助您理解,简而言之,请记住以下规则:

如果两者都被匹配,那么最后一个指令将是一个获胜者

Order allow,deny

如果两个指令都匹配,则拒绝将获胜(即使在conf中的allow指令之后编写了指令deny

Order deny,allow

如果两个指令都匹配,allow将获胜

例子1

Order allow,deny
Allow from localhost mydomain.com

只有localhost和* .mydomain.com可以访问此主机,所有其他主机均被拒绝

例子2

Order allow,deny
Deny from evil.com
Allow from safe.evil.com # <-- has no effect since this will be evaluated first

所有请求均被拒绝,最后一行可能会欺骗您,但请记住,如果同时符合最后一条获胜规则(此处,“拒绝”为最后一条),则与以下内容相同:

Order allow,deny
Allow from safe.evil.com
Deny from evil.com # <-- will override the previous one 

例子4

Order deny,allow
Allow from site.com
Deny from untrusted.site.com # <-- has no effect since this will be matched by the above `Allow` directive

接受所有主机的请求

示例4:典型的公共网站(除非已列入黑名单,否则允许)

Order allow,deny
Allow from all
Deny from hacker1.com
Deny from hacker2.com

示例5:典型的Intranet和安全站点(除非列入白名单,否则拒绝)

Order deny,allow
Deny from all
Allow from mypc.localdomain
Allow from managment.localdomain

C. Require指令(Apache 2.4)

Apache 2.4使用了一个名为 mod_authz_host

Require all granted =>允许所有请求

Require all denied =>拒绝所有请求

Require host safe.com =>仅允许来自safe.com


D.文件权限

大多数人做错的一件事是配置文件权限,

黄金法则是

无需许可即可开始,并根据需要添加

在Linux中:

  • 目录应获得Execute许可

  • 文件应具有Read权限

  • 是的,您是对的,请勿添加Execute文件权限

例如,我使用此脚本来设置文件夹权限

# setting permissions for /var/www/mysite.com

# read permission ONLY for the owner 
chmod -R /var/www/mysite.com 400 

# add execute for folders only
find /var/www/mysite.com -type d -exec chmod -R u+x {} \;

# allow file uploads 
chmod -R /var/www/mysite.com/public/uploads u+w

# allow log writing to this folder
chmod -R /var/www/mysite.com/logs/ 

我以此代码为例,在其他情况下设置可能会有所不同



原始答案

我遇到了同样的问题,但是我通过在httpd.conf的全局目录设置或httpd-vhosts.conf的特定目录块中设置options指令解决了该问题:

Options Indexes FollowSymLinks Includes ExecCGI

默认情况下,您的全局目录设置为(httpd.conf line ~188)

<Directory />
    Options FollowSymLinks
    AllowOverride All
    Order deny,allow
    Allow from all
</Directory>

将选项设置为: Options Indexes FollowSymLinks Includes ExecCGI

最后,它看起来应该像:

<Directory />
    #Options FollowSymLinks
    Options Indexes FollowSymLinks Includes ExecCGI
    AllowOverride All
    Order deny,allow
    Allow from all
</Directory>

也可以尝试改变Order deny,allow,并Allow from all通过线Require all granted

附录

目录索引源代码(为简洁起见,删除了一些代码)

if (allow_opts & OPT_INDEXES) {
     return index_directory(r, d);
} else {
        const char *index_names = apr_table_get(r->notes, "dir-index-names");

        ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r, APLOGNO(01276)
                      "Cannot serve directory %s: No matching DirectoryIndex (%s) found, and "
                      "server-generated directory index forbidden by "
                      "Options directive",
                       r->filename,
                       index_names ? index_names : "none");
        return HTTP_FORBIDDEN;
    }

41
另外,应该检查文件夹的权限,以便Apache进程的所有者有权读取/执行虚拟主机的指定路径。在Windows中,这可能很难得问题,但在Linux上它可以是403更频繁的原因
拉杜

76
我还不得不更改Order deny,allow, Allow from allRequire all grantedApache 2.4。参见此处:httpd.apache.org/docs/2.4/upgrading.html
Simon A. Eugster 2013年

52
只有在添加Require all granted它后才起作用
pylover 2013年

1
@pylover不和弄乱我的配置...(和这个家伙太一stackoverflow.com/questions/19263135/...
斯特凡帕凯

6
这个答案太差劲了!您切勿Allow from all在“ 多数民众赞成” <Directory />部分中设定httpd.conf仅仅是黑客的喜悦
RiggsFolly

187

我知道此问题已解决,但我碰巧自己解决了同一问题。

的原因

禁止您无权访问此服务器上的/

实际上是中的apache目录的默认配置httpd.conf

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory "/">
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all          # the cause of permission denied
</Directory>

只需更改Deny from all为即可Allow from all解决许可问题。

或者,更好的方法是在virtualhost配置上指定各个目录权限。

<VirtualHost *:80>
    ....

    # Set access permission
    <Directory "/path/to/docroot">
        Allow from all
    </Directory>

    ....
</VirtualHost>

Apache-2.4开始,访问控制是使用新模块完成的mod_authz_host从2.2升级到2.4)。因此,Require应使用新指令。

<VirtualHost *:80>
    ....

    # Set access permission
    <Directory "/path/to/docroot">
        Require all granted
    </Directory>

    ....
</VirtualHost>

OSX 10.6.8上的Apache / 2.2.24。1)这篇文章,以及2)此处的说明:thegeekstuff.com/2011/07/apache-virtual-host(您将收到一条警告,指出该行无效NameVirtualHost *:80,因此可以将其删除。您还必须创建目录日志文件。),以及
2011年

1
3)将行添加127.0.0.1 web_site_name.com到文件底部/ private / etc / hosts对我有用。如果您有Apache设置要监听8080端口,然后使用<VirtualHost *:8080>,就像必须使用url一样http://localhost:8080,则需要使用url http://web_site_name.com:8080。4)最后,我使用了@hmoyat的<Directory>配置(在其他答案之一中),因为它似乎更具体。
2014年

1
嗨@eagor 确保还启用MCrypt扩展(不仅安装它)。与Apache相比,该错误还与PHP更相关,因此您需要尝试stackoverflow.com/q/16830405/1349295或类似的线程。
沙皇皮诺2015年

3
请耐心等待授予您的根目录访问权限。这是不安全的。最好是授予对特定目录的访问权限(您想向公众展示)。
罗宾逊

1
对于那些使用过的用户<Directory />,建议的访问权限设置方法是按目录(即<Directory "/path/to/docroot">)。我的上一个示例使用<Directory />了显然允许远程主机访问整个文件系统的示例。我目前不知道破解者可以如何利用它,除了提供超出所需权限的权限是基本的安全措施。为了后代,我已经更新了答案。对于缺乏安全性的见解表示歉意。 httpd.apache.org/docs/current/misc/…–
沙皇皮诺

131

在默认的/ var / www /之外托管的目录的一个常见问题是,Apache用户不仅需要对托管站点的目录和子目录的权限。Apache要求对所有目录的权限一直到托管站点的文件系统的根目录为止。Apache在安装后会自动获得分配给/ var / www /的权限,因此,如果您的主机目录位于该目录的正下方,则该目录不适用于您。编辑:Daybreaker报告他的Apache已安装,没有对默认目录的正确访问权限。

例如,您有一台开发机,您的站点目录为:

/username/home/Dropbox/myamazingsite/

您可能认为您可以摆脱:

chgrp -R www-data /username/home/Dropbox/myamazingsite/
chmod -R 2750 /username/home/Dropbox/myamazingsite/

因为这赋予了Apache访问您网站目录的权限?嗯,这是正确的,但还不够。Apache一直在目录树中需要权限,因此您需要执行以下操作:

chgrp -R www-data /username/
chmod -R 2750 /username/

显然,我不建议您在不分析该目录结构中的内容的情况下,将访问生产服务器上的Apache的权限授予完整的目录结构。对于生产,最好保留默认目录或仅用于保存Web资产的其他目录结构。

Edit2:正如u / chimeraha指出的那样,如果不确定权限的用途,最好将站点目录移出主目录,以避免潜在地将自己锁定在主目录之外。


2
您的回答大有帮助。由于某种原因,我的/ var / www并未设置为由apache用户访问。谢谢!
2013年

1
@Craig那是进步。这意味着您已经解决了初始权限问题。开始查看您的Apache /应用程序日志文件,以确定是什么导致500错误。
吉尔斯·罗伯茨

5
多亏了这个答案,我才成功地将自己锁定在/ home目录树中……:)
seniorpreacher 2014年

1
这样做:chgrp -R apache / username /为我解决了这个问题!但是就像Edifice一样,现在我无法访问主目录树,除非我将用户chgrp返回。因此,现在我需要更改为原始用户才能通过git进行更改。然后改回apache重新部署我的服务器。这是唯一的方法吗?
anc1revv 2014年

1
chmod -R 2750-2号代表什么?7-所有者的rwe权限,5-重新组的权限,0-其他权限。但是2是多少?谢谢
Tebe

62

Apache 2.4中的某些配置参数已更改。设置Zend Framework 2应用程序时,我遇到了类似的问题。经过研究,以下是解决方案:

配置错误

<VirtualHost *:80>
    ServerName zf2-tutorial.localhost
    DocumentRoot /path/to/zf2-tutorial/public
    SetEnv APPLICATION_ENV "development"
    <Directory /path/to/zf2-tutorial/public>
        DirectoryIndex index.php
        AllowOverride All
        Order allow,deny #<-- 2.2 config
        Allow from all #<-- 2.2 config
    </Directory>
</VirtualHost>

正确配置

<VirtualHost *:80>
    ServerName zf2-tutorial.localhost
    DocumentRoot /path/to/zf2-tutorial/public
    SetEnv APPLICATION_ENV "development"
    <Directory /path/to/zf2-tutorial/public>
        DirectoryIndex index.php
        AllowOverride All
        Require all granted #<-- 2.4 New configuration
    </Directory>
</VirtualHost>

如果您打算从Apache 2.2迁移到2.4,请参考:http : //httpd.apache.org/docs/2.4/upgrading.html


谢谢!您的回答是正确的!
MladenIlić16年


24

在使用Apache 2.4的Ubuntu 14.04上,我执行了以下操作:

在文件apache2.conf中(在下方/etc/apache2)添加以下内容:

<Directory /home/rocky/code/documentroot/>
  Options Indexes FollowSymLinks
  AllowOverride None
  Require all granted
</Directory>

并重新加载服务器:

sudo service apache2 reload

编辑:这也可以在OS X Yosemite和Apache 2.4上使用。最重要的行是

要求所有授予


22

如果您使用的是WAMP服务器,请尝试以下操作:

  • 单击任务栏上的WAMP服务器图标

  • 选择在线选项

  • 您的服务器将自动重启

  • 然后尝试访问您的本地网站


19

如果将CentOS与SELinux一起使用,请尝试:

sudo restorecon -r /var/www/html

查看更多:https : //www.centos.org/forums/viewtopic.php?t=6834#p31548


4
请给这个人一个完整的互联网,他赚了。
UrielUVD 2015年

1
你救了我的命。我不知道为什么没有在其他地方指出这一点
埃里卡斯(Erikas)

1
先生,您救了我的一天,谢谢!
安东尼·富恩特斯·阿塔维亚

2
这是互联网上最重要的答案
弗拉基米尔·拉扎列夫斯基

17

我通过将用户添加到来解决了我的问题httpd.conf

# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
#User daemon
User my_username
Group daemon

2
答案没有道理。User被给了两次,最后UsermyuserUser deamon怎么了?另外,请确定您的答案的样式,其中不应该包含什么内容是非常不可读的httpd.conf。它也无法解释为什么这可以解决问题
dbf

2
我只是将“用户”和“组”更改为我的用户名,这也对我有用。
anc1revv 2014年

2
先生,你真是天赐之物 我无法解决这个问题,并且将我的用户和组都更新为我所在的用户非常有效。在复制生产VM并为开发VM设置新用户时发生。
理查德·奥尔特加

这个答案对我最有帮助
-mafonya

14

本文在Apache 2.2上创建虚拟主机可以帮助我(第9点)对顶级虚拟主机目录的访问权限。

我只需将以下行添加到我的vhosts.conf文件中:

<Directory I:/projects/webserver>
    Order Deny,Allow
    Allow from all
</Directory>

我遇到了问题,我将ubuntu 14.04中的文档根路径从/ var / www / html /更改为/ media / user / projects / php /:DocumentRoot / media / mithun / Projects / Sites / php <目录/ media / user / projects / php />选项索引FollowSymLinks AllowOverride无要求所有已授予</ Directory>无效。有帮助吗?
Mithun Shreevatsa 2015年

11

我遇到了同样的错误,并且很长一段时间都无法解决问题。如果您碰巧在包含SELinux之类的Linux发行版(例如CentOS)上,则需要确保已为文档根文件正确设置SELinux权限,否则会出现此错误。这是与标准文件系统权限完全不同的一组权限。

我碰巧使用了Apache和SELinux教程,但是一旦您知道要查找的内容之后,似乎就会发现有很多东西。


谢谢!SELinux引起了我的问题。我禁用了它,现在我可以访问默认/ var / www /目录之外的html文件了。现在,我将看一下本教程,以查看是否可以启用和配置它,以便仍然可以访问我的文件。
yellavon 2013年

您知道为什么restorecon /var/www/*命令会将所有内容都带回var_t而不是http_sys_content_tor tmp_t吗?类型var_t导致403 Forbidden错误。
errolflynn

6

如果您使用的是MAMP Pro,则可以通过选中- 选项卡Indexes下的复选框来解决此问题。 HostsExtended

在MAMP Pro v3.0.3中,外观如下: 在此处输入图片说明


谢谢它为我工作。
Ahmed_Ali '16

5

有另一种方法可以解决此问题。假设您要访问位于的目录“ subphp” /var/www/html/subphp,并且要使用进行访问127.0.0.1/subphp,则会收到如下错误:

您无权访问此服务器上的/ subphp /。

然后将目录权限从“无”更改为“访问文件”。命令行用户可以使用chmod命令来更改权限。


2
有半票赞成的选择吗?
Sahu V Kumar

3

我遇到了同样的问题,但是由于我将apache上的路径更改为var / www以外的文件夹,所以我开始遇到问题。

我通过在var / www / html> home / dev / project中创建一个符号链接来解决此问题,这似乎可以解决问题,而无需更改任何权限...


1
非常感谢,您知道这件事为我节省了太多工作!
oscar.fimbres

3

我使用Mac OS X,就我而言,我只是忘记在apache中启用php,我要做的就是取消注释以下一行/etc/apache2/httpd.conf

LoadModule php5_module libexec/apache2/libphp5.so

参考文章的细节。


2

(在Windows和Apache 2.2.x中)

“禁止”错误也是未定义虚拟主机的结果。

如Julien所述,如果您打算使用virtual hosts.conf,那么请转到httpd文件并取消注释以下行:

#Include conf/extra/httpd-vhosts.conf

然后在其中添加虚拟主机定义conf/extra/httpd-vhosts.conf并重新启动Apache。


你是对的!!!!!!
甘克

2

我遇到了这个问题,我的解决方案是使www-data不拥有适当的文件夹,而是将它设置为其中一个用户拥有。(我试图做一些幻想,但为了使ftp正常播放而进行了错误的欺骗。)

运行后:

chown -R www-data:www-data /var/www/html

机器再次开始提供数据。您可以通过以下方式查看谁当前拥有该文件夹

ls -l /var/www/html

2

此解决方案不允许所有人

我只想更改我的公共目录www,并从我的PC和通过Wifi连接的移动设备上访问它。我有Ubuntu 16.04。

  1. 因此,首先,我修改了/etc/apache2/sites-enabled/000-default.conf, 并更改了新的公共目录DocumentRoot“ / media / data / XAMPP / htdocs”的行DocumentRoot / var / www / html

  2. 然后,我修改了/etc/apache2/apache2.conf,并为本地主机和移动设备放了权限,这一次我使用了IP地址,我知道它不是完全安全的,但是对于我的目的来说还可以。

    <Directory/>
        Options FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Allow from localhost 10.42.0.11
    </Directory>
    

1

试试这个,不要添加任何东西Order allow,deny和其他:

AddHandler cgi-script .cgi .py 
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
<Directory "/usr/lib/cgi-bin">
    AllowOverride None
    Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
    Require all granted
    Allow from all
</Directory>

 

sudo a2enmod cgi
sudo service apache2 restart

1
    I changed 
    Order Deny,Allow
    Deny From All      in .htaccess to   " Require all denied "    and restarted apache but it did not help.

Ubuntu中apache2.conf的路径是/etc/apache2/apache.conf

然后我在apache2.conf中添加了以下几行,然后我的文件夹工作正常

    <Directory /path of required folder>
            Options Indexes FollowSymLinks
            AllowOverride All
            Require all granted
       </Directory>

   and run  " Sudo service apache2 restart " 

1

我知道这个问题已经有几个答案,但是我认为有一个非常微妙的方面,尽管已提到,但在先前的答案中并没有充分强调。

在检查Apache配置或文件的权限之前,让我们做一个简单的检查,以确保组成您要访问的文件(例如,文档根目录中的index.php文件)完整路径的每个目录不仅Web服务器用户可读且可执行

例如,假设您的文档根目录的路径为“ / var / www / html”。您必须确保Web服务器用户可以(读取和)执行所有“ var”,“ www”和“ html”目录。就我而言(Ubuntu 16.04),我错误地将“ x”标志从“ html”目录中移至“其他”组,因此权限如下所示:

drwxr-xr-- 15 root root 4096 Jun 11 16:40 html

如您所见,Web服务器用户(在这种情况下,向其应用“其他”权限的用户)没有对“ html”目录的执行访问权限,而这正是问题的根源。发出后:

chmod o+x html

命令,问题已解决!

在解决这种问题之前,我确实尝试了该线程中的所有其他建议,并且由于该建议被埋在了我几乎是偶然发现的评论中,因此我认为在此处强调和扩展它可能会有所帮助。


0

我只对特定的控制器有同样的问题-这真的很奇怪。我在CI文件夹的根目录中有一个文件夹,该文件夹的名称与我尝试访问的控制器的名称相同。因此,CI会将请求定向到此目录,而不是控制器本身。

删除此文件夹后(该文件夹有误),一切正常。

更清楚地说,这是它的样子:

/ci/controller/register.php

/ci/register/

我不得不删除/ci/register/


有时codeigniter使用.htaccess文件来停止直接访问。请查看ls -Al,以确保没有隐藏文件。
pgee70,2014年

0

确切检查文件放置位置,不要将它们嵌套在“文档”文件夹中。

例如,我犯了一个错误,因为我提到的将代码放在Documents文件夹中的方法是行不通的,因为Documents明确仅对您可用,而不对APACHE有效。尝试将其上移一个目录,您可能不会看到此问题。

将文件夹从:

/用户/您的用户名/文档/代码

到这里:/ Users / YOURUSERNAME /代码



0

您可以youralias.conf像以下代码那样更改文件:

Alias /Quiz/ "h:/MyServer/Quiz/" 
 <Directory "h:/MyServer/Quiz/">
   Options Indexes FollowSymLinks
   AllowOverride all
   <IfDefine APACHE24>
     Require local
   </IfDefine>
   <IfDefine !APACHE24>
    Order Deny,Allow
    Deny from all
    Allow from localhost ::1 127.0.0.1
   </IfDefine>
 </Directory>

0

请记住,在这种情况下要配置的正确文件不是phpMyAdmin别名中的httpd.conf,而是 bin/apache/your_version/conf/httpd.conf

查找以下行:

DocumentRoot "c:/wamp/www/"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Allow from all
</Directory>

确保将其设置为 Allow from all ...

如果没有,phpMyAdmin甚至可以工作,但是您的根目录和它下面的其他文件夹却不起作用。另外,请记住重新启动WAMP,然后将其联机...

这解决了我的头痛。


这个答案太差劲了!您切勿设置Allow from allRequire all granted在“ 多数民众赞成” <Directory />部分中httpd.conf仅让黑客高兴
RiggsFolly

0

在运行docker build之前,使用SSHFS从本地文件系统中的VirtualBox guest虚拟机中挂载文件时遇到了这个问题。最后,“修复”是将所有文件复制到VirtualBox实例,而不是从SSHFS装载内部进行构建,然后从那里运行构建。


0

工作方法(除非没有其他问题)

默认情况下,Apache不会限制从IPv4(公共外部IP地址)的访问

受限制的是“httpd.conf '中。

全部替换

<Directory />
    AllowOverride none
    Require all denied
</Directory>

<Directory />
    AllowOverride none
    # Require all denied
</Directory>

因此消除了对Apache的所有限制。

更换Require localRequire all granted/ WAMP / WWW /:C目录。

<Directory "c:/wamp/www/">
    Options Indexes FollowSymLinks
    AllowOverride all
    Require all granted
    # Require local
</Directory>

真的是“ <Directory />”(两个实例)吗?不应该是“ <目录>”吗?
Peter Mortensen

第一个接收目录路径<目录{/ path / to / your / dir}>
詹姆斯


0

这非常荒谬,但是当我尝试下载的文件不在文件系统上时,我收到了403 Forbidden。在这种情况下,apache错误不是很准确,在我将文件放置在原本应该的位置之后,整个工作就可以了。

By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.