el proftpd lleva un fichero de configuración proftpd.conf dónde está todo explicado.
Si, debes añadir un usuario en el sistema para que pueda acceder al ftp. No hace falta lo del alias.
Te recomiendo las directivas:
RequireValidShell off
<Limit LOGIN>
Order allow,deny
AllowUser usuario
Deny all
</Limit>
DefaultRoot /home/usuario/public_html usuario
La primera para que el usuario del ftp aunque no tenga acceso shell pueda logearse al ftp (por seguridad), la segunda para que sólo puedan acceder los usuarios que tu digas al ftp, aunque tengan cuenta y la tercera para que vean los ficheros del directorio dónde está el wordpress (mira la ruta (path))
Gracias, con eso me funcionó correctamente el FTP.
Añado una cosa para los que hayan encontrado este post buscando porqué Wordpress les pide datos de Acceso FTP si están en localhost. Es un fragmento de la web :
http://www.chrisabernethy.com/why-wordpress-asks-connection-info/In order to fix this issue, you will need to make sure that the scripts which need to write to the filesystem are owned by the same user that apache is running as.
Many hosting companies will run your apache instance using your user account, and all of your files will be owned by the same account. In those cases, you will probably not have the issue described here.
If your hosting company is running apache as a system user, and your files are owned by your own account, your only option may be to enter your FTP credentials here and allow WordPress to use FTP.
If you are running on a hosting company that gives you root access, or you have installed WordPress on your own development machine at home or at work, you should be able to modify the filesystem permissions to allow WordPress to directly access the filesystem.
The easiest way to do this is to find out what user apache is running as and change ownership of the entire WordPress directory to that user. For example, if apache is running as 'httpd', you could use the following commands on your WordPress installation directory:
# chown -R httpd: wordpress
Note that not all versions of chown are equal. If that command does not work, see your local chown man page for usage information.
Tip: In order to find out what user your instance of apache is running as, create a test script with the following content:
<?php echo(exec("whoami")); ?>
En mi caso se arregló escribiendo: chown -R www-data: www
Saludos
Mostrar Mensajes
Bueno, ¿ya lo dice el dicho, no?
creo que no es problema de configuracion de apache sino del dominio 