403 forbidden 您无权访问此服务器上的/。部署 Laravel 项目后
403 forbidden You don't have permission to access / on this server. after deploying Laravel project
我在 AWS 上的 EC2 实例上的 apache 服务器有些奇怪。
好吧，我在本地计算机上使用 Laravel 框架开发了网站，然后我通过 SSH 使用我最喜欢的 IDE ( PHP storm ) 部署了网站。
一开始一切都很好，但后来每次更新项目时，我都开始收到“您无权访问此服务器上的/。403 禁止访问”。
我注意到当我执行此命令“sudo chmod 777 /var/www/html/public”时，该网站再次运行，但需要大约 2 分钟。
但是这个问题很烦人，因为每次我更改服务器上的其中一个文件时都会出现此错误。特别是我有影响产品环境的开发环境。
我假设我的 apache 有问题 Server.so 这就是我的 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.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/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 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.
#
# 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 specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"
#
# 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 80
#
# 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
#
Include conf.modules.d/*.conf
#
# 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 webapp
Group webapp
# '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 root@localhost
#
# 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.example.com:80
#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
AllowOverride none
Require all denied
</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.
#
#
# 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 "/var/www/html/public"
#
# Relax access to content within /var/www.
#
<Directory "/var/www">
AllowOverride All
# Allow open access:
Require all granted
</Directory>
# Further relax access to the default document root:
<Directory "/var/www/html">
#
# 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.4/mod/core.html#options
# for more information.
#
Options 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 All
#
# Controls who can get stuff from this server.
#
Require all granted
</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.php index.html
</IfModule>
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
Require all denied
</Files>
#
# 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.example.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/ "/var/www/cgi-bin/"
</IfModule>
#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
AllowOverride All
Options None
Require all granted
</Directory>
<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig /etc/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
</IfModule>
#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8
<IfModule mime_magic_module>
#
# 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
</IfModule>
#
# 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.example.com/subscription_info.html
#
#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be 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.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on
# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf
#### Virtual Host Settings ####
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public"
ServerName mydomain.me
ErrorLog "logs/mydomain.me-error_log"
CustomLog "logs/test.mydomain.me-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/"
ServerName mydomain.net
ErrorLog "logs/mydomain.net-error_log"
CustomLog "logs/mydomain.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/dashboard"
ServerName dashboard.mydomain.net
ErrorLog "logs/dashboard.mydomain.net-error_log"
CustomLog "logs/dashboard.mydomain.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/dashboard"
ServerName dashboard.mydomain.me
ErrorLog "logs/dashboard.mydomain.me-error_log"
CustomLog "logs/dashboard.mydomain.me-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/dev"
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/html/public/dev/>
Options +Indexes +FollowSymLinks +MultiViews
AllowOverride All
Require all granted
</Directory>
ServerName dev.mydomain.me
ErrorLog "logs/dev.mydomain.me-error_log"
CustomLog "logs/dev.mydomain.me-access_log" common
</VirtualHost>
#### End of Virtual Host Settings ####
#### AWS Settings ####
# Disable ETag headers
FileETag none
# Hide Apache and PHP info
Header unset Server
Header unset X-Powered-By
# Don't expose server versions
ServerSignature Off
ServerTokens Prod
# Enable server-status for internal IP
<Location /server-status>
SetHandler server-status
Order Deny,Allow
Deny from all
Allow from 127.0.0.1
</Location>
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# Configure /var/www/html
<Directory "/var/www/html">
Options FollowSymLinks
AllowOverride All
DirectoryIndex index.html index.php
Order allow,deny
Allow from all
</Directory>
# Add remote IP to log
LogFormat "%h (%{X-Forwarded-For}i) %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
#### End of AWS Settings ####
我注意到另一件事，所有通过我的 IDE 上传的文件，用户从 webapp 更改为 ec2-user，这是有道理的，因为我使用 ec2-user 而不是 webapp sshing 服务器，所以这是是什么导致了问题？？
无论如何，我将非常感谢您的回答。
我还在开发环境的配置文件中进行了不同的设置，根据堆栈溢出上发布的答案，但我仍然无法正常工作。
根据您的 httpd.conf，您已正确设置 /var/www 目录。此配置已设置，因此 Apache 是 运行 作为 "webapp" 用户和组。确保您的 /var/www/html 目录及其所有内容至少对 webapp 用户或组具有读取权限。
获取setfacl包（Debian/Ubuntu）：
apt-get install setfacl
设置群组：
chown -R :webapp /var/www/html
为组设置写入权限：
chmod -R g+w /var/www/html
为所有目录设置组粘性位，以便新内容将具有父组：
find /var/www/html -type d -exec chmod g+s {} \;
为所有新内容设置默认组权限：
setfacl -R -d -m g::rwx /var/www/html
所以现在，即使您在 /var/www/html 目录中修改或创建目录和文件，它们也始终拥有 Apache 的正确权限。
仅当这不是生产环境时此顺序才合适，因为您不希望 Apache 能够写入所有内容。对生产服务器执行以下操作：
获取setfacl包（Debian/Ubuntu）：
apt-get install setfacl
设置群组：
chown -R :webapp /var/www/html
为组设置读取权限：
chmod -R g+r /var/www/html
为所有目录设置组粘性位，以便新内容将具有父组：
find /var/www/html -type d -exec chmod g+s {} \;
为所有新内容设置默认组权限：
setfacl -R -d -m g::r /var/www/html
那么对于 Laravel，您确实希望将存储设置为可写：
find /var/www/html/storage -type d -exec chmod g+w {} \;
setfacl -R -d -m g::rwx /var/www/html/storage
我得到
的原因
You don't have permission to access / on this server.403 Forbidden "
这是因为 AWS 自动扩展。因为旧服务器的旧配置设置为我的 public 目录（index.php 所在的目录），而我的 Apache 配置指向相同的文件夹 var/www/html/public.
但是，新创建的实例具有指向 var/www/html 的不同 Apache 配置，因此这两个配置之间存在冲突。
我是怎么发现这个问题的。有时我得到 403，在重新加载页面几次后我可以访问该网站。
无论如何，您应该通过在默认 AMI 中设置配置来更新新创建的 instance.either 的默认配置，或者如果您使用的是 elasticbeanstlak，则在配置页面中进行配置。
我在 AWS 上的 EC2 实例上的 apache 服务器有些奇怪。
好吧，我在本地计算机上使用 Laravel 框架开发了网站，然后我通过 SSH 使用我最喜欢的 IDE ( PHP storm ) 部署了网站。
一开始一切都很好，但后来每次更新项目时，我都开始收到“您无权访问此服务器上的/。403 禁止访问”。
我注意到当我执行此命令“sudo chmod 777 /var/www/html/public”时，该网站再次运行，但需要大约 2 分钟。
但是这个问题很烦人，因为每次我更改服务器上的其中一个文件时都会出现此错误。特别是我有影响产品环境的开发环境。
我假设我的 apache 有问题 Server.so 这就是我的 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.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/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 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.
#
# 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 specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"
#
# 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 80
#
# 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
#
Include conf.modules.d/*.conf
#
# 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 webapp
Group webapp
# '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 root@localhost
#
# 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.example.com:80
#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
AllowOverride none
Require all denied
</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.
#
#
# 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 "/var/www/html/public"
#
# Relax access to content within /var/www.
#
<Directory "/var/www">
AllowOverride All
# Allow open access:
Require all granted
</Directory>
# Further relax access to the default document root:
<Directory "/var/www/html">
#
# 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.4/mod/core.html#options
# for more information.
#
Options 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 All
#
# Controls who can get stuff from this server.
#
Require all granted
</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.php index.html
</IfModule>
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
Require all denied
</Files>
#
# 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.example.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/ "/var/www/cgi-bin/"
</IfModule>
#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
AllowOverride All
Options None
Require all granted
</Directory>
<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig /etc/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
</IfModule>
#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8
<IfModule mime_magic_module>
#
# 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
</IfModule>
#
# 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.example.com/subscription_info.html
#
#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be 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.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on
# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf
#### Virtual Host Settings ####
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public"
ServerName mydomain.me
ErrorLog "logs/mydomain.me-error_log"
CustomLog "logs/test.mydomain.me-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/"
ServerName mydomain.net
ErrorLog "logs/mydomain.net-error_log"
CustomLog "logs/mydomain.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/dashboard"
ServerName dashboard.mydomain.net
ErrorLog "logs/dashboard.mydomain.net-error_log"
CustomLog "logs/dashboard.mydomain.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/dashboard"
ServerName dashboard.mydomain.me
ErrorLog "logs/dashboard.mydomain.me-error_log"
CustomLog "logs/dashboard.mydomain.me-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin noreply@mydomain.net
DocumentRoot "/var/www/html/public/dev"
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/html/public/dev/>
Options +Indexes +FollowSymLinks +MultiViews
AllowOverride All
Require all granted
</Directory>
ServerName dev.mydomain.me
ErrorLog "logs/dev.mydomain.me-error_log"
CustomLog "logs/dev.mydomain.me-access_log" common
</VirtualHost>
#### End of Virtual Host Settings ####
#### AWS Settings ####
# Disable ETag headers
FileETag none
# Hide Apache and PHP info
Header unset Server
Header unset X-Powered-By
# Don't expose server versions
ServerSignature Off
ServerTokens Prod
# Enable server-status for internal IP
<Location /server-status>
SetHandler server-status
Order Deny,Allow
Deny from all
Allow from 127.0.0.1
</Location>
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# Configure /var/www/html
<Directory "/var/www/html">
Options FollowSymLinks
AllowOverride All
DirectoryIndex index.html index.php
Order allow,deny
Allow from all
</Directory>
# Add remote IP to log
LogFormat "%h (%{X-Forwarded-For}i) %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
#### End of AWS Settings ####
我注意到另一件事，所有通过我的 IDE 上传的文件，用户从 webapp 更改为 ec2-user，这是有道理的，因为我使用 ec2-user 而不是 webapp sshing 服务器，所以这是是什么导致了问题？？
无论如何，我将非常感谢您的回答。
我还在开发环境的配置文件中进行了不同的设置，根据堆栈溢出上发布的答案，但我仍然无法正常工作。
根据您的 httpd.conf，您已正确设置 /var/www 目录。此配置已设置，因此 Apache 是 运行 作为 "webapp" 用户和组。确保您的 /var/www/html 目录及其所有内容至少对 webapp 用户或组具有读取权限。
获取setfacl包（Debian/Ubuntu）：
apt-get install setfacl
设置群组：
chown -R :webapp /var/www/html
为组设置写入权限：
chmod -R g+w /var/www/html
为所有目录设置组粘性位，以便新内容将具有父组：
find /var/www/html -type d -exec chmod g+s {} \;
为所有新内容设置默认组权限：
setfacl -R -d -m g::rwx /var/www/html
所以现在，即使您在 /var/www/html 目录中修改或创建目录和文件，它们也始终拥有 Apache 的正确权限。
仅当这不是生产环境时此顺序才合适，因为您不希望 Apache 能够写入所有内容。对生产服务器执行以下操作：
获取setfacl包（Debian/Ubuntu）：
apt-get install setfacl
设置群组：
chown -R :webapp /var/www/html
为组设置读取权限：
chmod -R g+r /var/www/html
为所有目录设置组粘性位，以便新内容将具有父组：
find /var/www/html -type d -exec chmod g+s {} \;
为所有新内容设置默认组权限：
setfacl -R -d -m g::r /var/www/html
那么对于 Laravel，您确实希望将存储设置为可写：
find /var/www/html/storage -type d -exec chmod g+w {} \;
setfacl -R -d -m g::rwx /var/www/html/storage
我得到
的原因You don't have permission to access / on this server.403 Forbidden "
这是因为 AWS 自动扩展。因为旧服务器的旧配置设置为我的 public 目录（index.php 所在的目录），而我的 Apache 配置指向相同的文件夹 var/www/html/public.
但是，新创建的实例具有指向 var/www/html 的不同 Apache 配置，因此这两个配置之间存在冲突。
我是怎么发现这个问题的。有时我得到 403，在重新加载页面几次后我可以访问该网站。
无论如何，您应该通过在默认 AMI 中设置配置来更新新创建的 instance.either 的默认配置，或者如果您使用的是 elasticbeanstlak，则在配置页面中进行配置。