I'll assume you have to assign web-site in all cases. buy no worries Just tested to create new ftpuser with options Directory as "/var/www/clients/" instead of proposed /var/www/clients/client2/web1/ and dadaa: Code: Command: USER ftptest Status: TLS/SSL connection established. Response: 331 User ftptest OK. Password required Command: PASS ******** Response: 230-User ftptest has group access to: client2 sshusers Response: 230 OK. Current restricted directory is / Command: SYST Response: 215 UNIX Type: L8 Command: FEAT Response: 211-Extensions supported: Response: EPRT Response: IDLE Response: MDTM Response: SIZE Response: REST STREAM Response: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*; Response: MLSD Response: AUTH TLS Response: PBSZ Response: PROT Response: UTF8 Response: ESTA Response: PASV Response: EPSV Response: SPSV Response: ESTP Response: 211 End. Command: OPTS UTF8 ON Response: 200 OK, UTF-8 enabled Command: PBSZ 0 Response: 200 PBSZ=0 Command: PROT P Response: 200 Data protection level set to "private" Status: Connected Status: Retrieving directory listing... Command: PWD Response: 257 "/" is your current location Command: TYPE I Response: 200 TYPE is now 8-bit binary Command: PASV Response: 227 Entering Passive Mode (192,168,xxx,yyy,zzz,yyy) Command: MLSD Response: 150 Accepted data connection Response: 226-Options: -a -l Response: 226 5 matches total Status: Directory listing successful Listing all clients and their sub folders (client2, 3 and 4) .
Unclear! How can I create a new FTP client if I must specify a domain name to do so? I simply do not understand what I am looking at, here.
@edi00A FTP user is always associated to a website. So you can not access all sites of a client with one FTP user as every website has its own website (shell) user and the FTP user is bound to that shell user @eko_taas But you area aware that you can do this only as admin and not as client. As admin you can set off course paths that are outside of the client directory. But nevrtehless, setting such a path is useless as this FTP user still belongs to one website, so files uploaded by this user to a different website belong to a wrong user.
I would not mind if the FTP user would belong to one website. I just want to open separate directory "new" above the website /var/www/clients/client1 /new /web1 /web2 and FTP to "new"
FTP users belong to a website, so a path should be always withis a site. Create anwe directory: /var/www/clients/client1/web1/new and then set the path of the FTp user to that directory.
That is what I have now. The problem is that if I am doing backup of all webs via WinSCP I do not want new directory in there. I do not understand why I can't FTP to root if I can do that with WinSCP I was always able to FTP to root as Admin on all my prior servers. I think you should create a provision to do so. Or how can I create web without use of domain
Might be cheap-and-dirty, but Based on Till's notes, this will be only useful for back-ups (you can always trust NewB ) Even if cheap-and-dirty, I tested with mentioned ftptest-user (account created as admin) and "back-up" all 3 clients to ftp-client working w/o issue (filezilla).... You can select any domain (or create new one just to be able to create ftp-user.... w/o (fake) domain I'll assume no chance.
way to cheap-and-dirty This is how I did test (for you). Note! As I have understood/considered structure (as NewB to NewB): - admin is not a client - Client can be created by Admin (or distributer) - domain is under one client (which can be created by admin/distr. for him) - ftp-account is always under one domain (which can be created by admin/distr. for him) 1. login as ISPC3 admin 2. create new user (or use existing one with reasonable quota) 3. create new web-site (useless.example.com or use existing one with existing user) (If you can use existing, you can avoid extra files as one domain less) 4. create new ftp-account with Options / Directory as "/var/www/clients/" (as Till said possible only as Admin) 5. try to back up your data (download) (I have tried with Filezilla w/o problem) Few issues I have not checked / tough thru: - how quota is working (was not an issue for me as used existing me-as-client with big quota) - I did not try to recover (i.e. upload), that should be done with site dedicated ftp-account to keep attributes correct as till mentioned earlier (I am using site dedicated ftp-accounts only (like till recommends), and also more limited ones for special purposes only to sub-folders /var/www/clients/client2/web1/subftp1/ ).
Quota works on a per user basis, so the files uploaded with this FTP user account to the quota volume of the website were the user belongs to, independantly to which directory the files were uploaded.
It looks it works very well. The key part was Options / Directory as "/var/www/clients/client1/" in my case. It appears that I can set User/Group separately in my case I have set them to www-data both rather than root. it works a OK Thanks!
