imscp fresh install: proftpd login doesn't work

  • Hi together,
    i have installed a fresh ubuntu 14 installation without any other packages. After linux installation i directly installed imscp branch version 1.3.x.
    everything works fine, but ftp login doesen't work so far.


    Code
    1. 220 ProFTPD 1.3.5rc3 Server (myserver)Name (xxx:root): boesi331 Password required for boesiPassword:530 Login incorrect.Login failed.Remote system type is UNIX.Using binary mode to transfer files.ftp> 221 Goodbye.


    i found older post (FTP) but i can't solv my problem.


    My auth.log says:

    Code
    1. proftpd[9550]: xxx (xxx) - USER boesi: no such user found from xxx [xxx] to ::xxx:21



    some other messages:

    Code
    1. Sep 29 11:25:35 myServer postfix/smtpd[9552]: sql_select option missingSep 29 11:25:35 myServer postfix/smtpd[9552]: auxpropfunc error no mechanism availableSep 29 11:25:35 myServer postfix/smtpd[9552]: _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin: sqlSep 29 11:25:35 myServer saslauthd[6987]: pam_mysql - SELECT returned no result.Sep 29 11:25:35 myServer saslauthd[6987]: pam_mysql - SELECT returned no result.Sep 29 11:25:35 myServer saslauthd[6987]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication moduleSep 29 11:25:35 blimustec saslauthd[6987]: do_auth : auth failure: [user=owner] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error]

    i did check the proftpd.conf (user sql settings):

    Code
    1. # i-MSCP SQL Managment<IfModule mod_sql.c> SQLBackend mysql SQLAuthTypes Crypt SQLAuthenticate on SQLConnectInfo imscp@localhost "vftp_user" "secretpasswordstring" SQLUserInfo ftp_users userid passwd uid gid homedir shell SQLGroupInfo ftp_group groupname gid members SQLMinUserUID 1001 SQLMinUserGID 1001</IfModule>

    They seems to be ok. I tried to login on phpmyadmin & console with this credentials (vftp_user + pass) and check if the fields exists in database. It seems to be ok, too:
    mysql -u vftp_user -psecretpasswordstring imscp


    Code
    1. mysql> show tables;
    2. +-----------------+
    3. | Tables_in_imscp |
    4. +-----------------+
    5. | ftp_group |
    6. | ftp_users |
    7. | quotalimits |
    8. | quotatallies |
    9. +-----------------+


    ftp User exists in tables.



    I tried to reinstall several times the same version again (1.3.x) with
    perl imscp-autoinstall -d


    Then i tried to install the stable version 1.2.9, but this doesent work (i a downgrade possible?)


    Because there are more erros in auth log (see above this post), i think perhaps there are some problems with sql conenction between services (proftp) and the database? I don't know iff this could be a imscp insatllation bug or any other problems from me.


    I checked the "Service Ports" in control panel, too: FTP | 0.0.0.0, i-MSCP-Daemon,< 127.0.0.1


    Any idea how can a solve my problem?

    Edited once, last by boesi666 ().

  • Hello ;


    Downgrade from 1.3.x branch to 1.2.9 is not really possible because some db update were mades...
    The "some other messages:" your have posted are not related to proftpd.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • i found out my mistake


    i logged on with boesi on the domain. But the username which imscp create ist always "username@domain"


    so i forgot to type in the long username.


    is it possible to use short usernames without the domain in the string? For a project i move from one root server to another (imscp).


    On old server the ftp accounts wasn't with the "@domain" in the usernamestring

    Edited once, last by boesi666 ().

  • No it's not possible by default and also makes no sense in shared-hosting..

  • ok. thanks for official answer. for future it ist ok.


    My actual problem i could solve:
    i copied the records in imscp database table ftp_users into a new record. Then i edited the username from myusername@mydomain to "myusername"


    after thet i found in imscp controlpanel both ftp users and logon with both names is possible. This is only a work around for my project.


    For new accounts in future theese usernames with @domain ok for me, too.


    solved.