Member Avatar for Inny

Im getting a 403 forbidden error on my server.

Server: MySQL 5.1
phpMyAdmin -

On my root directory I have a subfolder '/classifieds'
During work using filezilla, I somehow moved the folder into another subfolder.
I deleted it from that subfolder and reuploaded to the root directory.

Now I am able to access my classifieds admin panel

but not the installation itself.

the following gives the above error:

http://www.camosreptiles.com.au/classifieds/

root is /s101-2/home6/camosreptiles/classifieds

I dont know anything about servers, I just use filezilla to change files on the server.

can sombody please help me fiox this?
much appreciated.

  • 2 Contributors
  • 1 Reply
  • 281 Views
  • 19 Hours Discussion Span
  • Latest Post Latest Post by rch1231

Dani AI

Generated

Quick checklist for — is on the right track: a 403 after moving a folder almost always comes down to one of three things: filesystem ownership/permissions, a restrictive .htaccess or Apache config, or a missing/incorrect index file. Because your admin page loads, Apache can serve files from that tree, so start by checking the classifieds directory itself and its parents.

Run these checks (replace names/paths as needed and run as a user with the right privileges):

# show owner/permissions for the folder and its parent
ls -ld /s101-2/home6/camosreptiles /s101-2/home6/camosreptiles/classifieds

# if ownership is wrong, change to the site account (example)
chown -R camosreptiles:apache /s101-2/home6/camosreptiles/classifieds

# set safe permissions: dirs 755, files 644
find /s101-2/home6/camosreptiles/classifieds -type d -exec chmod 755 {} \;
find /s101-2/home6/camosreptiles/classifieds -type f -exec chmod 644 {} \;

Additional things to test if permissions look OK: confirm there is an index file (index.php or index.html) in /classifieds/; temporarily rename any .htaccess there to rule out a deny rule; check parent directories have the execute bit so Apache can traverse them. Look at the Apache error log for exact errors (permission denied or "client denied by server configuration") — that will point you to either a filesystem or config problem.

Cautions: never use 777 to "fix" this. On many shared hosts ownership and PHP handlers (suPHP, suEXEC) matter — if you lack shell access, use the host control panel file manager or open a support ticket and ask them to check ownership, error_log entries and SELinux/AppArmor if present.

Member Avatar for rch1231

In order for apache to access the files the directory and files must be readable by the apache user of group. Normally the owner is the domain login id and the group is apache. Your directory listing should look something like this:

ls -la /s101-2/home6/camosreptiles/

drwxr-xr-x camosreptiles apache 2048 18:44 classifieds
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.