Ftp uploaded files - errors 403 and 404


Evening all,

I have a problem accessing files I’ve uploaded through ftp. I’m new to using any kind of an internet server really so I’m not sure whether I’m doing something wrong, or whether there is a logical explanation for this, so please bear with me :slight_smile: A browse on the wiki and a forum search haven’t turned up anything.

I’ve created an ftp-only account for a friend to use and assigned him his own domain (or is it a subdomain?) - http://ziroc.dreamhosters.com

It looks like the DNS changes have now propogated through, since travelling to the above link displays an index of files inside. I can access through ftp either directly to his domain, or through the host machine with no problems. I can upload and download files fine, and they are reflected in the index of files in the directory.

For example, going to the above URL, you should be able to see a ‘test.txt’ file.

Yet when I try to visit the file directly, I get the following error:

You don’t have permission to access /test.txt on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.[/quote]
If anyone could shed some light on what’s happening it would be much appreciated!



View the properties of that folder and see if all users is readable.(chmod is another term for what I mean).


Thanks for the reply silkrooster - it’s definitely a permissions issue, so thanks for pointing me in that direction.

However, I’m still a bit confused - for some reason, read access isn’t sufficient for this. After a bit of trial and error, it appears that I can only get error free access when permissions on the directory are set to 777! This seems a tad…erm…excessive!

For example, currently the situation is this:

and I have no access to the files over my browser. The ftp programme can access the folder, but only after I’d enabled writing for group users (for some reason, 764 is not enough).

Chmod 777 however makes the files readable as you would expect.

So in a sense, it’s fixed, but I would love to know why the permissions have to be so extensive, when you would think a web browser only needs read access to a file/folder to display it…any ideas?

Thanks again :slight_smile:


Great links! I hadn’t realised that execute permission is needed to read the contents of a directory - it’s all working fine now.

Thank-you both for your help :slight_smile: