[debian] Anonymous FTP

Discussion in 'Installation/Configuration' started by Mountainman, Jun 13, 2006.

  1. Mountainman

    Mountainman New Member

    Hi there on this sunny day :cool: !

    I have got a few questions on anonymous ftp.

    In ISPConfig you should turn 'ftp access' and 'anonymous ftp' on in order to use anonymous ftp. Should i do somethin else because at the moment this isn't working.

    I get a '530 - Incorrect login' in my ftp client. ( I didn't fill in any user/pass just the domain... )

    I hope you can help me on this one.

    grtz,
     
  2. falko

    falko Super Moderator Howtoforge Staff

    Do you use a regular FTP client?
    What's in /etc/proftpd_ispconfig.conf?
     
  3. Mountainman

    Mountainman New Member

    I use FileZilla as a ftp-client, don't think that's the problem. In Firefox and IE i'm prompted for a password.

    I first tried enabling anonymous ftp on a website that already had ftp enabled, however this didn't work ( the 503... ), then I created another site with only anonymous ftp enabled. This resulted in the same 503 error.

    My proftpd.conf:
    Code:
    ###################################
    #
    # ISPConfig proftpd Configuration File
    #         Version 1.0
    #
    ###################################
    <VirtualHost 192.168.1.101>
            DefaultRoot             ~
            AllowOverwrite          on
            Umask                   002
            <Anonymous /var/www/web1/ftp>
              User                          web1_anonftp
              Group                         web1_anonftp
              UserAlias                     anonymous web1_anonftp
              UserAlias                     guest web1_anonftp
              MaxClients                    10
              <Directory *>
                <Limit WRITE>
                  DenyAll
                </Limit>
              </Directory>
              <Directory /var/www/web1/ftp/incoming>
                Umask                       002
                <Limit STOR>
                  AllowAll
                </Limit>
                <Limit READ>
                  DenyAll
                </Limit>
              </Directory>
            </Anonymous>
    </VirtualHost>
    <VirtualHost 192.168.1.101>
            DefaultRoot             ~
            AllowOverwrite          on
            Umask                   002
            <Anonymous /var/www/web1/ftp>
              User                          web1_anonftp
              Group                         web1_anonftp
              UserAlias                     anonymous web1_anonftp
              UserAlias                     guest web1_anonftp
              MaxClients                    10
              <Directory *>
                <Limit WRITE>
                  DenyAll
                </Limit>
              </Directory>
              <Directory /var/www/web1/ftp/incoming>
                Umask                       002
                <Limit STOR>
                  AllowAll
                </Limit>
                <Limit READ>
                  DenyAll
                </Limit>
              </Directory>
            </Anonymous>
    </VirtualHost>
    
    web1 is the website in where I enabled ftp and anonymous ftp...
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    If you restart proftpd on the commandline:

    Did you get any errors?
     
  5. Mountainman

    Mountainman New Member

    hmmz, currently I get the following error:

    Code:
    Restarting ProFTPD ftp daemon.proftpd.
    .. - warning: "ProFTPD" address/port (192.168.1.101:21) already in use by "Debian"
     - warning: "ProFTPD" address/port (192.168.1.101:21) already in use by "Debian"
    proftpd.
     done.
    
     
  6. falko

    falko Super Moderator Howtoforge Staff

    Do you know why you have the <VirtualHost 192.168.1.101> section twice in /etc/proftpd_ispconfig.conf?
     
  7. Mountainman

    Mountainman New Member

    Yes I noticed this, is it safe to delete 1 section?

    grz
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    I guess you have entered the IP 192.168.1.101 twice in ISPConfig under management > server > settings. If the IP 192.168.1.101 is in the IP field for the server IP, it shall not be entered again in the IP list field below.
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    It si safe, but will not solve your problem, as ISPConfig will override it when you change any website in the ISPConfig interface.
     

Share This Page