Bug Ftp system

Discussion in 'General' started by ivomendonca, Oct 27, 2010.

  1. ivomendonca

    ivomendonca Banned

    Ftp jumps to next user account.

    Example :
    User : A
    site - www.AAA /var/web5/
    site - www.BBB /var/web6/

    disabling www.AAA, ispconfig uses the AAA ftp account with BBB path.

    Missing verification of "domain" part.
    Imagine if i delete the site AAA and my copy was on BBB.:confused:

    This is not a bug is a trap :D
  2. till

    till Super Moderator

    FTP usernames have to be unique for the whole server as the FTP protocol never verifies by domain, thats independant if you use ispconfig or not. To ensure unique usernames, every username has a prefix. Make sure that you did not remove or modified the prefix.
  3. ivomendonca

    ivomendonca Banned

    Did you read what i wrote ?

    If you cant understand what i write i can write in other words.

    Disable Vhosts have active ftp accounts for those that want to leave to other host, or simple disable the ftp account, but changing path with no "common sense", is not a normal beavior.
    Last edited: Oct 27, 2010
  4. till

    till Super Moderator

    Thats not reproducable on my systems with ispconfig 3.0.3

    1) I created new website test1.tld
    2) I created new website test2.tld
    3) I created FTP user test1 for website test1.tld
    4) I created FTP User test2 for website test2.tld
    5) I disabled user test1, the path of user test2 does not change.

    I guess you did some manual modifications e.g. in the FTP path or so.
  5. ivomendonca

    ivomendonca Banned

    Yes, but disabled by traffic, thats what i wrote.

    And is all the same version (stable) i dont change code in stable versions.

    And you have to use the ftp account, not look for ispconfig "paths".

    I dont lose time reporting bugs to others software, if i did not try 10 times.
    Last edited: Oct 27, 2010
  6. till

    till Super Moderator

    Read your own post and tell me where you find the word traffic here....

    By the way, the traffic quota system does not disable FTP accounts. It disables the website.

    If you like to report a bug, then please do this in the bugtracker. as bugs posted in the forums does not get reviewed by the devlopers.


    The ispconfig genetral forum is for general questions about ispconfig.
  7. till

    till Super Moderator

    So, up to the next test:

    1) Changed the paths on both ftp users to a custom path.
    2) Disabled the website and enabled it again. Result: Path of ftp users has not changed.
    3) Disabled ftp user, enabled ftp user again. result: path does not change.

    So the only conlusion that I can ind is that you do not use ispconfig 3.0.3 or that you have changed some code.
  8. ivomendonca

    ivomendonca Banned

    ok, ok so i did think i wrote traffic :) sorry.

    I thinked disabled by traffic or by hand will do the same.

    ->So the only conlusion that I can ind is that you do not use ispconfig 3.0.3 or that you have changed some code.

    Yes, you are right. again!
    Thanks for the help.
    Last edited: Oct 27, 2010
  9. till

    till Super Moderator

    The path does not change on my systems with 3.0.3 installed. You should recheck this on your server. there is exactly one situation where the path is rewritten for FTP users and thats when a website is assigned to a new client, as this means that the path of the site has been changed and in that case, ispconfig has to remap the FTP user to the new path of this website.
  10. ivomendonca

    ivomendonca Banned

    Add a client.
    add 2 domains to that client
    add 1 ftp user for each domain.

    Open filezilla and configure the 2 accounts.

    Add a file to domain1.
    Disable domain 1

    refresh ftp account(filezilla) of domain1, and is connected to domain2.
  11. till

    till Super Moderator

    Tested this with fireftp and it is not reproducable. Site1 remains site1. Deactivating a site can not have a influence on FTP which you can see in the sources. Disabling FTP just removes the vhost file for apache.
  12. ivomendonca

    ivomendonca Banned

    Yes, you are right i cant reproduce like i say it will.

    But one thing is right, that bug really exists, you can bet on that.
    Maybe something related auto disable by cron when the site is over traffic.

    In my other "bug" is the traffic Limit(status) wont go away, now that "bug" is fixed (24 H later).

    My 2 bugs where active during that 24H time, now in not possible to reproduce, you can take your conclusions.

Share This Page