Plesk 403 Forbidden Error
Contents |
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base Documentation Downloads Plesk University Release notes Blog Become a Partner Russian German French Spanish Chinese Japanese plesk 403 - forbidden access is denied Italian Language English Russian German French Spanish Chinese Japanese Italian any Search I plesk 403 forbidden nginx get the "Forbidden error" when trying to access a site Article ID: 800, created on Oct 6, 2008, last review
403 Forbidden Error Fix
on Dec 26, 2014 Applies to: Plesk 11.5 for Linux Symptoms I get the "Forbidden" error when trying to access a site Resolution In general, this error means that the Apache process cannot access
You Don T Have Permission To Access On This Server Plesk
some file/directory because the system the user's Apache server is running under (usually httpd or www) has no read/search permissions or access is forbidden by Apache settings. The reason may be one of the following: There is no index file in this directory, or the index file is not listed in the DirectoryIndex directive in the Apache configuration file. There are Inhibitory settings in the .htaccess file in the plesk error logs folder Find out what user Apache is run under. For example, with the 'ps -axu | grep httpd' command, the user name can be found in httpd.conf in the User directive. Check if this user has the read permission for the needed file and the execute/search permission for every folder in a path to the file. If you see the error below in the Apache error_log... pcfg_openfile: unable to check htaccess file, ensure it is readable. ... then make sure that the Apache user is included in the psaserv group: # grep psaserv /etc/group psaserv:x:2523:apache,psaftp,psaadm Search Words none pcfg_openfile: unable to check htaccess file, ensure it is readable Domains giving 403 error for all a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f Email subscription for changes to this article RSS subscription for changes to this article Save as PDF Was this article helpful? Tell us how we may improve it. No Yes University Training & Certification Product Expert Program Partners Become a Partner Company About Us Leadership Team Press Room Contact Us Keep in touch © 2016 Parallels IP Holdings GmbH. All rights reserved. Plesk and the Plesk logo are trademarks of Parallels IP Holdings GmbH. Terms and Conditions Privacy Policy Impressum Sitemap
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base Documentation
Plesk Preview 403 Forbidden
Downloads Plesk University Release notes Blog Become a Partner Russian you do not have permission to access this document. plesk German French Spanish Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any 500 internal server error Search "403 Forbidden" error received when trying to access a site Article ID: 112884, created on Nov 25, 2011, last review on Aug 12, 2014 Applies to: https://kb.plesk.com/en/800 Plesk for Linux/Unix Symptoms When you try to access your website, you receive the "403 Forbidden" error. You see the following in the Apache error_log: pcfg_openfile: unable to check htaccess file, ensure it is readable. Resolution 1. Check http://kb.sp.parallels.com/en/800. 2. If the KB article above does not help, then you will https://kb.plesk.com/en/112884 need to understand exactly where the incorrect permissions for the Apache user are set: su - apache -s /bin/bash
-bash-3.2$ cd /var/www/vhosts/
-bash-3.2$ cd /var/www/vhosts/
-bash: cd: /var/www/vhosts/hammasll.fi/httpdocs/
-bash-3.2$ cd /var/www/vhosts/
-bash-3.2$ cd /var/www/vhosts/
-bash: cd: /var/www/vhosts/hammasll.fi/httpdocs/
am I seeing a 403 Forbidden error message? Browse by products and services DV and VPS Hosting Grid Shared Hosting Legacy DV Hosting Applies to: Grid Difficulty: Medium Time Needed: 20 Tools Required: FTP client, plain text editor Applies to: All DV https://mediatemple.net/community/products/dv/204644980/why-am-i-seeing-a-403-forbidden-error-message Difficulty: Easy Time Needed: 10 Tools Required: FTP client, plain text editor Overview The 403 Forbidden error is an HTTP status code which means that accessing the page or resource you were trying to reach is absolutely http://www.miva.com/forums/forum/online-merchants/miva-merchant-5-5/113631-403-forbidden-when-using-toolkit-s-callurl-on-new-plesk-11-5-server-configuration forbidden for some reason. This article contains basic troubleshooting instructions for 403 Forbidden errors. Symptom You get the following error when you try to visit a web page: Figure 1. Causes and Solutions There are three 403 forbidden common causes for this error. Here they are listed from most likely to least likely. Empty html directory Empty httpdocs directory Make sure that your website content has been uploaded to the correct directory on your server. Remember to replace example.com with your own domain name. Grid: /domains/example.com/html/ This is the path you will use for FTP. However, the full path to your website content is /home/00000/domains/example.com/html/. The 00000 is your site plesk 403 forbidden number. See this article for details. DV server: /var/www/vhosts/dv-example.com/httpdocs/ When you connect with your FTP user, you just need to navigate into the httpdocs directory. If this folder does not exist, feel free to create it. No index page The home page for your website must be called index.php or index.html. To resolve this error, upload an index page to your htmlhttpdocs directory. If you already have a home page called something else - home.html for example - you have a couple of options: Rename your home page to index.html or index.php. Set up a redirect on the index page to your real home page. See How do I redirect my site using a .htaccess file? for details. Set a different default home page in your .htaccess.htaccess file. Javascript Kit has a good example. If you don't want a single page to display, but instead want to show a list of files in that directory, see Making directories browsable, solving 403 errorsMaking directories browsable, solving 403 errors. Permissions and ownership errors A 403 Forbidden error can also be caused by incorrect ownership or permissions on your web content files and folders. Permissions Rule of thumb for correct permissions: Folders: 755 Static Content: 644 Dynamic Content: 700 Please see File Permissions for a complete discussion of permiss
visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Announcement Collapse No announcement yet. 403 forbidden when using toolkit's callurl on new Plesk 11.5 server configuration Collapse X Collapse Posts Latest Activity Search Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only Filtered by: Clear All new posts skepticwebguy Mivite Join Date: Dec 2007 Posts: 367 #1 403 forbidden when using toolkit's callurl on new Plesk 11.5 server configuration 09-05-13, 06:13 PM I recently upgraded from Plesk 10.4.4 to Plesk 11.5. When my server was running Plesk 10.4.4, I used toolkit's "callurl" function on subdomain.domain.com to load an html file from domain.com. Something has changed on the new server configuration that no longer allows me to use toolkit's callurl function to fetch files from domain.com from subdomain.domain.com. It causes 403 Forbidden errors (i.e. "You don't have permission to access filename on this server") and "client denied by server configuration" errors in my server error log file related to the file on domain.com that callurl won't load. I use alias settings in my vhost.conf file on subdomain.domain.com which point subdomain.domain.com/filename to domain.com/filename. I know these aliases are working because the file I am trying to call via callurl can easily be accessed directly usign the subdomain.domain.com alias. For instance, if in the callurl code I try to fetch http://subdomain.domain.com/file.html, I get the 403 Forbidden error when viewing my store page that contains the callurl function. However, if I simply load http://subdomain.domain.com/file.html into a browser I can see the file just fine. That file actually only exists at http://domain.com/file.html. So, I know vhost.conf server path alias is working correctly. Any ideas what server