1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

skeleton files and symlinks for FTP

Discussion in 'Plesk for Linux - 8.x and Older' started by crops, Jul 17, 2005.

  1. crops

    crops Guest

    Hi there,

    i was browsing through the forums but did not find a complete answer to my problem.
    I created a new client with a new domain and all ok. With the original FTP details that i setup i did an ftp and i was able to see all directories under that client, which i guess is not what we want( i mean end user should see only on the httpdocs and httpsdocs and cgi-bin).

    i believe this has somthing to do with the skeleton definition?can i create a vhost.conf file and put in my skeleton with the symlinks that i want?
    Basically my question is :

    How do i create symlinks to the above 3 directories so as end user will be able to see only these directories, how do i inlcude to the direcotry name the domain name e.g. have something like domain.com-docs,domain.com-docss and how do i automate this to apply for any newly created domain?
  2. jamesyeeoc

    jamesyeeoc Guest

    Skeleton files have nothing to do with this. Symlinks are not involved either.

    When you create a domain ftpuser and set the login shell to /bin/bash (chrooted), it will allow them to login and only see that domain's root.

    The domain root includes httpdocs, httpsdocs, anon-ftp, subdomains, etc.

    The given chrooted domain ftpuser should not be able to see the folders of another domain, even if the domain is also owned by the same Client.

    Check the login shell settings for this ftpuser and make sure it is set for the chrooted option.

    Or is it the Web Users feature you are trying to implement???
  3. crops

    crops Guest

    Hi there,

    thanks for your quick reply,

    maybe i wasnt understood. the FTP user does see his domain root and not somebody else's domain. What I was trying to say was that the end user is able to see and have access to directories such as bin,conf etc,lib,statistics,usr, var, web_users etc which he has access on and he shouldnt since all these fodlers have nothing to do with the FTP user who wants to just upload files for publishing on the web...or is this normal for PLESK and i'm just being stupid here?

    The purpose of the skeleton structure isnt to predefine a structure that will be propagated to all newly created domains and thats the structure that the end FTP user will see?
  4. jamesyeeoc

    jamesyeeoc Guest

    The skeleton file allows you to define your own (limited) structure and files (custom error docs, custom index, etc). Other directories will be created by Plesk such as the anon-ftp, etc, var and others as are required for doing the chroot environment and other directories which Plesk needs to be present.

    The FTP login is implemented in such a was as to allow the single ftp user to be able to access everything under the docroot of the domain. This is by their design.

    Since they do not allow creation of more than a single ftp user per domain, this is how they have implemented it.

    Others have been able to setup webusers and then do some custom stuff to get the files moved over to the proper docroot directories.

    If you go 'outside' of Plesk, there are other methods for creating additional ftpusers and make their home directory the httpdocs folder, but then what if they need to access the httpsdocs folder? You would need several ftpusers per domain.

    Since all the normally needed directories are directly under ~/domain.com/ that is where the single ftpuser is set for home directory.

    The purpose of the skeleton is not just for defining what the ftp user will see, but for defining a standardized directory structure and files for a new domain, not just for the ftp user, but for the entire domain in general.

    Hope that's not too confusing.