FTP Invalid Path - But It's NOT!

Mitsurugi

Verified User
Joined
Jul 19, 2005
Messages
39
A simple problem, I'm trying to create this FTP account:

/home/admin/domains/mydomain.com/public_html/user/

I'm getting this:

That is not a valid path. Either it is not in your home directory, it contains symbolic links, or it contains invalid characters

I strongly disagree! It IS a valid path, it IS in my home directory, it does NOT contain a symbolic link or ANY invalid characters.

The directory "user" exists in "public_html". There are no weird permissions going on.

Any ideas? It will accept the link up to "public_html" but it won't even consider "user".
 
Any update on this issue?

I basically have the same problem as I want to allow FTP access to /home/username/domains/domain.com/public_html/userfolder - however, I get exactly the same error while trying to create that CUSTOM path.

Would be nice to see some replies here :)
 
Hello,

Testing this on our build system does not generate any problems.
1) Try entering the path without the trailing / character.
2) Is your /home directory a symbolic link to something like /usr/home ?
3) Make sure the path actually exists
4) Make sure you are using the latest version of DA (1.28.0)

John
 
Hello,

I guess it is a different problem since managed to find out where it fails.

My idea was to allow some people accessing a directory i created for them. So basically

domain.com/username

existed already with files inside.

If you try to create a custom ftp account and the folder already exists, then it fails to create the custom ftp.

However, if a user folder does not exist, then DA creates the custom FTP account to domain.com/folder.

Is this ment to be that way or would it be something you could maybe add in future?

I am basically launching a free hosting service which creates sub folders and would like to give access to that folders if a user needs ftp badly.

Thanks


Edit: I think I found the problem and will try to fix it. It had to do with chmod permissions. I will report back once confirmed by testing.


Update:
It seems like there is no issue with DA. The problem was the permissions on the existing folder which is why DA failed to accept it as ftp folder.

I tried to create a folder by FTP and was able to set the FTP to that folder. The issue was my script which set the chmod which caused the issue.

Thanks for your reply
 
Last edited:
U need to chown the folder to proper user

But i think DA shud solve this issue its really bad unable to create FTP with such silly mistake
 
Hello,

For simplicity, yes DA could, but we'd consider it a secuirty issue if DA went around changing directory ownerships that did not belong to the user. For example, if there is a directory owned by root, DA should not change that ownership, no matter where it lives. This is especially important because a symbolic link could in theory be used to point to somewhere the user shouldn't be going.. then if DA were to reset the permissions, that folder would then have full access by the user, which of course would be bad ;)

Also, a user shouldn't be able to create a folder without his permissions anyway... if a root user is creating things manually, just make sure they chowned correctly.

John
 
but you could ignore directories which have user=apache bcoz most of the php scripts create folders with user=apache

to those folders we arent able to create ftp ... this is very bad .. i almost removed DA after this but hmm chown worked .. but a manual job.

I have a script which autocreates a folder for every user to download like /home/admin/domains/mydomain.com/public_html/username/

and wanted to give him ftp to only that directory .. but couldn't and so lost all the customers and got all -ve feedbacks as i promised them FTP

DA dint allow .. not my dault .. DA should allow admin to create FTP to folders owned by usergroup apache ... at user's own risk.
 
Last edited:
Back
Top