Apache出现 You don't have permission to access /phpmya
在 CentOS5.3 MySQL 5.0.45 Apache2.2.3 PHP5.1.6(都是系统自带的)中运行PHP程序出错。 装好 apachephpmysql 后,拷贝(tar / mv )一份 phpmyadmin 过后运行出错: You don’t have permission to access / on this server 有人说把selinux关掉就好了, 的确是
在 CentOS5.3 + MySQL 5.0.45 + Apache2.2.3 + PHP5.1.6(都是系统自带的)中运行PHP程序出错。
装好 apache+php+mysql 后,拷贝(tar / mv )一份 phpmyadmin 过后运行出错:
You don’t have permission to access / on this server
有人说把selinux关掉就好了, 的确是这样。原因是因为网站执行的权限,一般要 Read from all httpd scripts and the daemon这个权限。
1. Apache – Document root must be a directory 问题。
是SELinux的新特性搞的鬼。我把目录或文件设成了user_home_t类型,因此apache的进程没有权限,无法访问。针对 Apache的进程所使用的SELinux target policy规定了apache的进程只能访问httpd_sys_content_t类型的目录或文件。
解决办法:
很简单,把目录或文件的策略类型改成 httpd_sys_content_t 就可以了
使用root用户
$ chcon -R -t httpd_sys_content_t 目录名或文件名
然后可以用命令
$ ls -laZ
drwxr-xr-x root root system_u:object_r:httpd_sys_content_t .
drwxr-xr-x root root system_u:object_r:httpd_sys_content_t ..
drwxr-xr-x root root root:object_r:httpd_sys_content_t admin
-rw-r--r-- root root root:object_r:httpd_sys_content_t adminer.php
drwxr-xr-x root root root:object_r:httpd_sys_content_t phpmyadmin
-rw-r--r-- root root root:object_r:httpd_sys_content_t test.php
$ ll -aZ
$ ll -Z
查看文件目录的策略类型。
注: 只查看目录
$ ls */
$ ll */
$ ll /var/www/html/*/

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











To set up a CGI directory in Apache, you need to perform the following steps: Create a CGI directory such as "cgi-bin", and grant Apache write permissions. Add the "ScriptAlias" directive block in the Apache configuration file to map the CGI directory to the "/cgi-bin" URL. Restart Apache.

There are 3 ways to view the version on the Apache server: via the command line (apachectl -v or apache2ctl -v), check the server status page (http://<server IP or domain name>/server-status), or view the Apache configuration file (ServerVersion: Apache/<version number>).

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

When the Apache 80 port is occupied, the solution is as follows: find out the process that occupies the port and close it. Check the firewall settings to make sure Apache is not blocked. If the above method does not work, please reconfigure Apache to use a different port. Restart the Apache service.

How to view the Apache version? Start the Apache server: Use sudo service apache2 start to start the server. View version number: Use one of the following methods to view version: Command line: Run the apache2 -v command. Server Status Page: Access the default port of the Apache server (usually 80) in a web browser, and the version information is displayed at the bottom of the page.

How to configure Zend in Apache? The steps to configure Zend Framework in an Apache Web Server are as follows: Install Zend Framework and extract it into the Web Server directory. Create a .htaccess file. Create the Zend application directory and add the index.php file. Configure the Zend application (application.ini). Restart the Apache Web server.

Apache cannot start because the following reasons may be: Configuration file syntax error. Conflict with other application ports. Permissions issue. Out of memory. Process deadlock. Daemon failure. SELinux permissions issues. Firewall problem. Software conflict.

To delete an extra ServerName directive from Apache, you can take the following steps: Identify and delete the extra ServerName directive. Restart Apache to make the changes take effect. Check the configuration file to verify changes. Test the server to make sure the problem is resolved.
