Cpanel Fcgi 403 Error
Contents |
Guide cPanel WebHost Manager (WHM) Plesk SSL Certificates Specialized Help Offers & Bonuses Website Design Affiliates Helpful Resources Account Addons Billing System HostGator Blog HostGator Forums Video Tutorials Contact Us Interact and Engage Put two cpanel fcgi timeout or more words in quotes to search for a phrase: "name servers" Prepend cpanel fcgi config a plus sign to a word or phrase to require its presence in an article: +cpanel Prepend a minus sign cpanel fastcgi to a word or phrase to require its absence in an article: -windows Words of less than three characters are ignored. All searches are case-insensitive. Search [?] Support Portal Home » Specialized Help cpanel fastcgi configuration » 403 Forbidden or No Permission to Access 403 Forbidden or No Permission to Access A 403 Forbidden error means that you do not have permission to view the requested file or resource. While sometimes this is intentional, other times it is due to misconfigured permissions. The top reasons for this error are permissions or .htaccess error. Permissions The 403 Forbidden error means that your
403 Forbidden Error Fix
file has bad permissions. Directories and folders must be 755. Executable scripts within the cgi-bin folder must be 755. Images, media, and text files like HTML should be 755 or 644. See our article on How to change permissions (chmod) of a file for information on how to change file permissions. If your permissions were changed to 000, please contact us via phone or Live Chat and an Administrator will help resolve this. Only one of our Linux Administrators can correct these permissions. Hidden Files (Dot Files) If you see "client denied by server configuration" in your Error Logs, then this usually means bad file permissions, but could also mean that the visitor is trying to look at a hidden file, like the .htaccess file. You cannot look at that file in your browser, or any file name that starts with a dot. e.g. http://domain.com/.htaccess will always result in a 403 error. Other Possibilities The account may have IP Deny rules. Check in cPanel and make sure you are not blocking your own connecting IP. You may have changed the Index Manager to No Indexing. This will cause a 403 error if their is
Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by yasmagic, Dec 11, 2008. Page 1 of 2 1 2 Next > yasmagic Kilo Poster Messages: 12 Hello, I recently upgraded
What Does 403 Forbidden Mean On Website
to Plesk 9.0. I have set PHP as Fastcgi option for one of my 403 forbidden error wordpress website, and when I tried to access the site it provides the following error: "Forbidden You don't have permission to access /index.php 403 forbidden cpanel on this server." When I disable .htaccess file, the site works or if I comment out "RewriteEngine On" in the .htaccess file then it works. But, I need "RewriteEngine On" to be set for the full http://support.hostgator.com/articles/403-forbidden-or-no-permission-to-access functionality of my website. I see the following error in the Apache error log: Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden: /var/www/vhosts/
eCommerce App & Web Developers WordPress & Bloggers Agencies & Designers Enterprise Government Blog About Us Who We Are Philosophy of Web Hosting Our Data Centers Leadership Press Room Careers Email sign up Contact Server Security A Script for Fixing File Permissions January 27, 2012 https://www.servint.net/university/article/the-tech-bench-a-script-for-fixing-file-permissions/ suPHP and FastCGI require files and folders to have a specific set of permissions/ownership different from other handlers. Without these permissions set correctly you will see a lot of errors such as: “403 Forbidden”, “500 Internal Server Error”, https://www.deanspot.org/~alex/php5fcgi/ or simply generic errors that commonly have the word ‘permission’ in them. It can be very time consuming to track down and check file permissions across a whole server. Luckily, fixing permissions and ownership on a server running 403 forbidden cPanel can be scripted. One of the members of our MST, Colin Roche-Dutch, created a simple script for ServInt called ‘fixperms' that you can wget to any cPanel server. Simply run the fixperms script, specifying the user (or all users), and the errors disappear. It is a good generic fix if you cannot find your permission problem, or if you have just switched your handler and need a quick way to change every user account on 403 forbidden error the server. ***WARNING!!!*** The following script is intended for suPHP or FastCGI ONLY! If you are not running either of these two handlers, do not run fixperms. The script will cause problems if you are running another handler such as DSO. Furthermore, it is highly recommended that you run a full backup of your server before running fixperms or any other script that makes changes to multiple files. The fixperms script is intended for cPanel servers only. It is dependent on cPanel’s internal scripts and file structure. If you’re on anything else (such as Plesk), it will simply fail to run. It won’t be able to do anything. Steps to run fixperms on your VPS 1. wget fixperms and run for a single user To use the fixperms script, simply log into your server as root, wget the file from our server, then run it. Type in the cPanel username and it will run only for that particular account. It does not matter which directory you are in when you run fixperms. You can be in the user’s home directory, the server root, etc. The script will not affect anything outside of the particular user’s folder. wget http://img.servint.net/fixperms.sh.gz gunzip fixperms.sh.gz sh fixperms.sh -a USER-NAME 2. Running fixperms for all of the users If you would like to fix the permissions for every user on your
server using FastCGI. PHP normally runs as an Apache module. Apache + mod_php4 + mod_php5 = sefaulting badness PHP can also run as a CGI program. This is generally slower than the module approach, but the key here is flexibility rather than performance. FastCGI is much faster than normal CGI. My very incomplete benchmarks showed PHP5 as FastCGI to have about 80% of the performance of mod_php5. (Measuring requests/second via ab, Apache Benchmark.) Setup This is the testing setup I put together : Linux (This setup works on Windows, but all my examples are on Linux.) Apache 2.0.59 PHP 4.4.4, compiled as an Apache module PHP 5.1.5, compiled as a FastCGI binary mod_fastcgi 2.4.2 A note on binaries There are binary packages available for all the software used in this presentation. These notes show how to compile everything from source, but that's not necessary if you don't want to. It's also fine to mix and match binary packages with packages you build yourself. If you get binaries, you'll still need to do the configuration to tie it all together. Install Apache 2.0.59 shell> cd /usr/local/src/apache-2.0.59 # Nothing too special. Enable shared-object support and # use the prefork module recommended by php.net shell> ./configure --prefix=/usr/local/apache-2.0.59 --enable-so --with-mpm=prefork shell> make shell> make install http://httpd.apache.org/docs/2.0/install.html Install PHP 4.4.4 shell> ./configure --prefix=/usr/local/php-4.4.4 --with-apxs2=/usr/local/apache-2.0.59/bin/apxs --enable-memory-limit --with-mysql shell> make shell> make install You might want other options. This is just a minimal set. I've already got a version of PHP running with my main web server, so I put this one in a different directory in /usr/lib/. http://www.php.net/manual/en/install.unix.apache2.php Configure Apache to server PHP4 content. shell> vi /usr/local/apache-2.0.59/conf/httpd.conf # Load the PHP4 module. LoadModule php4_module modules/libphp4.so # Associate the three listed extensions with a PHP mime-type. AddType application/x-httpd-php .php .phtml .php3 # Turn up the error reporting in Apache since we're going to be # screwing around. Change this back to a higher level once # everything is working OK. LogLevel debug http://httpd.apache.org/docs/2.0/mod/directives.html Test the setup so far Looks like everything is OK so far. Install mod_fastcgi 2.4.2 shell> cd /usr/local/src/mod_fastcgi-2.4.2 Use the apxs program to compile *.c into a shared object called 'mod_fastcgi.so'. shell> /usr/local/apache-2.0.59/bin/apxs -o mod_fastcgi.so -c *.c Change to the directory where the .so ends up. shell> cd .libs Install the module. shell> /u