Proftpd issue

massive

Verified User
Joined
Feb 16, 2006
Messages
299
Everything started when i updated to Apache 2.
I am creating a ftp account and i am trying to login
but it says login incorrect.
I am trying to login as anonymous and i am getting :
530-Unable to set anonymous privileges.

Can anybody help me?
 
There's nothing you can do installing apache that should make any changes to proftpd.conf or prfotpd.passwd.

Nevertheless, those are the two files where I'd start to look.

Jeff
 
After installing apache i reinstalled direct admin
to revert the system in its previous state.

Is this a reason to cause proftpd not to work
even if i can see the user that i just created in direct admin? In proftd.passwd the user has also a record.
I can't login even with the admin user name and pass

My proftpd.conf :

# This is a basic ProFTPD configuration file (rename it to
# 'proftpd.conf' for actual use. It establishes a single server
# and a single anonymous login. It assumes that you have a user/group
# "nobody" and "ftp" for normal operation and anon.

ServerName "ProFTPD Default Installation"
ServerType standalone
DefaultServer on

# Port 21 is the standard FTP port.
Port 21

# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
Umask 022

# To prevent DoS attacks, set the maximum number of child processes
# to 30. If you need to allow more than 30 concurrent connections
# at once, simply increase this value. Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd).
MaxInstances 30

# Set the user and group under which the server will run.
User ftp
Group ftp

# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
#DefaultRoot ~

# Normally, we want files to be overwriteable.
AllowOverwrite on

# Bar use of SITE CHMOD by default
<Limit SITE_CHMOD>
DenyAll
</Limit>

# A basic anonymous configuration, no upload directories. If you do not
# want anonymous users, simply delete this entire <Anonymous> section.
#<Anonymous ~ftp>
# User ftp
# Group ftp

# We want clients to be able to login with "anonymous" as well as "ftp"
UserAlias anonymous ftp

# Limit the maximum number of anonymous logins
MaxClients 10

# We want 'welcome.msg' displayed at login, and '.message' displayed
# in each newly chdired directory.
DisplayLogin welcome.msg
DisplayFirstChdir .message

# Limit WRITE everywhere in the anonymous chroot
<Limit WRITE>
DenyAll
</Limit>
</Anonymous>
 
Reinstalling DirectAdmin on a working server is guaranteed to break things.

Two of the things you've broken are probably the proftpd.conf and proftpd.passwd files.

Jeff
 
can you please answer me because i have big
problem with my server?

I woulike to know what users are using the files
proftpd.conf and proftpd.passwd
 
I don't suggest, but you may find copies of more recent ones somewhere:

Try:
Code:
# ls -al /etc/proftpd.conf*
# ls -al /etc/proftpd.passwd*
To see if you've got any files with anthing after them; possibly something like:

/etc/proftpd.conf~

or

/etc/proftpd.conf-

and

/etc/proftpd.passwd~

or

/etc/proftpd.passwd-

If so, they may contain more copies of the file, needing less changes to make work.

I don't know what other problem may be caused by reinstalling DA; you might want to contact DA support.

Jeff
 
Back
Top