Dear all,

I am trying to install Drupal 6.10. In our domain I have been assigned a user name called mdcd. I upload all the contents of the Drupal package to the home directory called wwwhome. Therefore, the path containing the contents of the Drupal files is as follows:

/homewww/wwwmdcd/wwwhome/

I have also done the necessary write permissions and created a database.

Now, in order to start the installation I point the web address with my browser. But I get the following error:

Forbidden
You don't have permission to access / on this server.

I have done a quick search in this forum but no success. Any ideas how to resolve this.

Thanks in advance...

Comments

cog.rusty’s picture

Do you see anything when you browse to http://example.com/CHANGELOG.txt?

Did any other subdirectories exist under "wwwhome" before you uploaded Drupal?

matgas’s picture

Hi,

The wwwhome directory was empty before I move the contents of the Drupal package there.

After this move the first thing I do is point out the Internet address by the browser and I get the error:

Forbidden
You don't have permission to access / on this server.

When I point to http://www.example.com/CHANGELOG.txt I get the same error:

Forbidden
You don't have permission to access /CHANGELOG.txt on this server.

cog.rusty’s picture

Using FTP, do you see Drupal's CHANGELOG.txt file and index.php file in the "wwwhome" directory?

Or are they in a subdirectory under that?

If you can see the files in "wwwhome" then you will need to ask your host's tech support to fix whatever is wrong. If they are in a subdirectory you need either to browse there or to move everything back.

rbthakuri’s picture

I am facing the same problem.

My hosting account is with godaddy.com and I did an online drupal install in the home directoy under the /drupal folder. However pointing the browser to www.example.com/drupal is generating the following:

=======================================================================
Forbidden
You don't have permission to access /drupal on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
--------------------------------------------------------------------------------
Apache/1.3.33 Server at AppStuff Port 80
=======================================================================

I tried an manual install which also resulted in the same 403 Forbidden Error.

Can anyone help me figure out-
-if its a drupal issue?
-or an issue with my godaddy account;
- or some permission issue due to something i may have done wrong.

HELP..

Dhaval’s picture

if u find any solutions then plz ping me

mattgilbert’s picture

I get this error when uploading a multisite setup. The error doesn't appear in a subdomain pointed at the root of the drupal folder, where index.php is, but a different subdomain pointed at one of the site folders does return this 403 error. Anyone know why? I suspect .htaccess is involved, but I'm not sure how.

cog.rusty’s picture

It is natural Apache behavior that if you browse to a directory which doesn't contain an index file specified in the DirectoryIndex line, then you will get either an "403 Permission denied" (if you have and Options -Indexes line) or a file listing (if you have an Options +Indexes line).

If I misunderstood, explain what you mean by "one of the site folders", what you uploaded there and what you expected to see.

mattgilbert’s picture

oh i get it now. i pointed the subdomain to the folder with index.php and renamed the site folder to match that subdomain, now it works.

sorry, just learning..

robyedlin’s picture

I just tried to migrate my site (on ServInt server w/cPanel) to another subdomain for development purposes, without using a module to do it.

I dumped the db and compressed the public_html directory, and migrated both to a new account. Then I imported the db and I extracted the Drupal files in the new account under the public_html directory.

When I tried to access the new account in my browser, I got 403 Permission denied errors on every page.

There was nothing different about the files on the dev site, including the .htaccess file.

When I extracted the files in the new account, I forgot to ssh in and do a chown on the public_html directory to yourusername:nobody. You will know if you have to do this if the public_html permissions are seemingly random numbers. To find out, ssh in and run ls -l in your /home/myaccount directory.

Changing it to myusername:nobody fixed it for me.

TribalMan’s picture

Thank you. Solved it for me. I was doing this http://drupal.org/creating-drupal-test-sites (pretty much hat you did)

The second part is the important part: nobody

ram4nd’s picture

chown: invalid group: āra:nobodyā

billyverde’s picture

Tried it, and received: chown: changing ownership of `html': Operation not permitted

ram4nd’s picture

use sudo or root user

anacronaut’s picture

I recently ran into this issue on a Godaddy hosting account because I was pointing to the wrong IP Address in the DNS A record. If none of the above suggestions work, make sure you're A record is pointing to the Dedicated IP Address found on your Hosting Dashboard under the Server settings section. You'll still use the IP Address for FTP and SSH access.

vikassaxena’s picture

Hello All,

Without doing any changes to my website, I started getting an error that my website is offline. The error that it was showing then was following.

"The mysql error was: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' "

Then after getting in hold of my host admin, I got the issue resolved, this error came as the server was down.

But after getting this one resolved, I could see the main domain, but the sub domain that I was working on, starting receiving the following error

"Forbidden You don't have permission to access / on this server"

Then upon suggestion from my host admin, I checked the .htaccess file and there it was, it had nothing but the following data left

"order deny,allow
deny from all"

I immediately restored my .htaccess file and the issue got resolved for me. You could also trying renaming the file .htaccess to some other name .htaccess1, in case you dont have a backup.

I was so relieved, that I thought of sharing it with you.

Thanks!!
http://mainframewizard.com

bmango’s picture

I too had the same problem. It was because I had the wrong folder permissions set for the root folder (of drupal). They should have been 755. This solved the problem.

TribalMan’s picture

Anonymous’s picture

I ran into the issue after re-installing my laptop with Ubuntu.
Choosing the encrypted home dir option I only got 403's on my existing projects which I was running out of /home/USER/workspace/projectname searching through some sites it seems that encrypting caused my problem.

I moved my projects to /var/www/projectname and symlinked the workspace, all worked as expected.

Tiliann’s picture

Looking through all of the documentation and all of these issues, I noticed that the host system created the subdomain files under public_html (where the index.php file is) while the instructions told me to put the subdomain files under /sites. I moved the subdomain files to /sites to match the instructions. With the subdomain files under /sites the system was being directed to a directory that did not have an index file.

Make sure your subdomain directories are in the same directory as your index.php file (move them if necessary, this doesn't seem to mess anything up).
Make sure your system is being directed to look at that directory (document root)

On a side (but related) note, my host allowed me to create *.(mydomain).com so I don't have to set up each subdomain on that end separately.

EddPy’s picture

During a fresh install and minimal knowledge, I solved the, seemingly, same problem by disabling SELinux on my CentOS6 setup. I got the same error but the cause was different.

Temporarily (doesn't survive reboot) disable SELinux by executing
echo 0 >/selinux/enforce
Permanently disable SELinux by editing
/etc/selinux/config
and changing the line
SELINUX=enforcing
to
SELINUX=disabled
You'll need root permissions for both operations.

Please note that this is highly insecure and should be used for testing only.
You can read further about it here:
http://www.crypt.gen.nz/selinux/disable_selinux.html

Sorry about exhuming this post but I haven't found relevant information about Drupal paired with this error elsewhere.
Hopefully, this will help others.