Welcome to LinuxQuestions. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.How to Fix Forbidden and Permission Denied Error Messages on your Apache Setup
I have scoured the web trying to make sure things are configured correctly with no luck. It contains the configuration directives that give the server its instructions. 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. NOTE: Where filenames are specified, you must use forward slashes instead of backslashes e.
If a drive letter is omitted, the drive on which httpd. 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. Change this to Listen on specific IP addresses as shown below to prevent Apache from glomming onto all bound IP addresses. Listen It is usually good practice to create a dedicated user and group for running httpd, as with most system services. ServerAdmin: Your address, where problems with the server should be e-mailed.
It only takes a minute to sign up. I followed this tutorial Building an SQLite temperature logger. The python files work perfectly, no errors at all. However, I am not able to see the webpage, I get a - forbidden error. I've been banging my head for the last couple of days. I'm hoping that anyone here would be able to help me. This makes me think that the problem is related to webgui. The owner of this file is www-data.
Here is the contents of the cgi conf. Your public files are owned by root. Apache can't access it. Change the ownership so that it's owned by www-data. These will change the owner and group of the files in those directories to www-data. The files will once again get owned by root if you edit it as root usually by using sudo [editor] [file]. If that's the case, simply re-run the commands above. If this is accessible online or if you decide to publish it publicly, you may want to set the permissions to so random people can't hack modify your public files.
Ask Different is a question and answer site for power users of Apple hardware and software.
It only takes a minute to sign up. For references, I usually check:. This time I'm simply getting a Forbidden error every time I hit Here are the relevant Apache configs:. I have an alias specified in OSX server pointing to a user directory.
No idea why it wasn't working. Eventually, I just checked the "shared folder" checkbox in the Finder for that folder, and it workedon the specified domain, with php active, the way I wanted it to.
I generally fix this by setting the Apache user to myself in local environments and in machines where the only user who uses Apache is me. Own them:. After this, Apache and PHP et al. In fact, you should prevent this regardless of the scripts you run or even if you don't set Apache user to yourself since you probably don't want random outsiders to be able to see the contents of your localhost.
I just solved my issue by setting permissions not only to the DocumentRoot directory, but also to all its parent directories. This is how I did it. Error 13 indicates a filesystem permissions problem. That is, Apache was denied access to a file or directory due to incorrect permissions.
Subscribe to RSS
It does not, in general, imply a problem in the Apache configuration files. In order to serve files, Apache must have the proper permission granted by the operating system to access those files. In particular, the User or Group specified in httpd. Typical permissions on a unix-like system for resources not owned by the User or Group specified in httpd. You may also need to check extended permissions such as SELinux permissions on operating systems that support them.
On some systems, the utility namei can be used to help find permissions problems by listing the permissions along each component of the path:.The Forbidden error is an HTTP status code that means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason. Different web servers report Forbidden errors in different ways, the majority of which we've listed below. Occasionally a website owner will customize the site's HTTP Forbidden error, but that's not too common.
The Forbidden error displays inside the browser window, just as web pages do. The IE title bar should say Forbidden or something similar. Cannot download the information you requested inside the MS Office program.
The error is essentially saying "Go away and don't come back here. You can see a complete list at Microsoft. Check for URL errors and make sure you're specifying an actual web page file name and extensionnot just a directory.
Most websites are configured to disallow directory browsing, so a Forbidden message when trying to display a folder instead of a specific page, is normal and expected. This is, by far, the most common reason for a website to return the Forbidden error. Be sure you fully explore this possibility before investing time in the troubleshooting below. If you operate the website in question, and you want to prevent errors in these cases, enable directory browsing in your web server software.
Clear your browser's cache. Issues with a cached version of the page you're viewing could be causing Forbidden issues. Log in to the website, assuming it's possible and appropriate to do so. A Forbidden message could mean that you need additional access before you can view the page. Typically, a website produces a Unauthorized error when special permission is required, but sometimes a Forbidden is used instead.
Clear your browser's cookiesespecially if you typically log in to this website and logging in again the last step didn't work. While we're talking about cookiesbe sure you have them enabled in your browseror at least for this website if you do actually log in to access this page. The Forbidden error, in particular, indicates that cookies might be involved in obtaining proper access.
Contact the website directly. It's possible that the Forbidden error is a mistake, everyone else is seeing it, too, and the website isn't yet aware of the problem. Most sites have support-based accounts on social networking sitesmaking it really easy to get a hold of them. Some even have support email addresses and telephone numbers. Twitter is usually abuzz with talk when a site goes down completely, especially if it's a popular one.
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up. But when I access Apache web server using Where test-site is the second "localhost". The filename is default. You have to edit it you can rename it, if you want, or make some other. Of course, you need to have some index. Ii is good idea to spend some time to improve your server's security.
These manuals are about the security configuration: 1st and 2nd. Here you can get free SSL certificate. These sites will help you to check your progress: 1st and 2nd. Choice the Office profile. Something like this. I am supposed to link you to this answer where solved my problem. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered.
I had a SELinux issue. I don't know if the first command was necessary or only the second. That second definition is somehow setting DocumentRoot to the system's root directory. Apache is right to deny that. Learn more. Asked 8 years, 3 months ago.
Nevertheless none of the answers solved it directly in my case or were based upon false or outdated information. Many of those rightly accepted answers tell to change permissions or ownership of the configured DocumentRoot directory and the contained files and directories recursively to www-data.
But this is likely not needed anymore when talking about a local installation of latest Debian or Ubuntu e. As the error page itself contains just a very generic message we need to have a look at the error log to get more information on it:. The tail command will output the last 10 lines of a file and using the -f option ensures that the output is updated while the log grows. This one is easy.
As explained at Apache: client denied by server configuration we just need to update our configuration with Require all granted setting - so it looks like:. This one is a bit more complicated as it can have several reasons. To find out what the actual reason is a good start is to update our configuration to not use a destination containing a symlink but instead point to the destination directly.
If you see another message here and may already have a working solution it would be great when you comment and link the respective discussion here so other people might find the right information as well. As the message tells the path is not fully accessible for Apache as one or more components of it can not be traversed.
To see which component may cause it we can do:. The namei command separates and prints the path components and with -m option shows the mode bits of each component in the style like ls -l command would do. As it seems the johndoe directory is causing the trouble here.
So before we just modify the permissions with chmod let's better have a closer look:.
The ls command with -d option will print the information for the directory and not its contents in list -l style. This finally pointed me into the right direction as I was sure that I have not setup any ACL on my own. Even more because I have not even set up the media mount points on my own but instead I used Nautilus to encrypt and mount my drive. Keep in mind that you need to encrypt and mount your drive after every boot.
There is plenty of information available on it here at Stack Exchange but I can recommend:. Sign up to join this community. The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered.
How to Fix a 403 Forbidden Error
Asked 4 years, 10 months ago. Active 3 years, 8 months ago. Viewed 14k times. Active Oldest Votes.