Well long time no post. Latest problem that I found was that I didn’t see the dot file on ftp client.
The ftp server was vsftdp.
The fix is
force_dot_files=YES
Of course you have to restart the vsftdp server after adding this line to conf.
April 23, 2014
vsftpd dot file .htaccess is not visible
July 18, 2012
How to install wordpress plugin without ftp user/password
Hello
Well I try today to install a plugin on a wordpress. But when I try to install it it request me the ftp user password host, for my hosting account.
Well, i try to chmod 777 the wp-content, still the same, so I force the wordpress to not require ftp by adding some code into wp-config.php
So to fix this chmod 777 wp-content
and add
define('FS_METHOD', 'direct');
to wp-config.php
March 2, 2012
proftpd passive port not working
Well, we have to check a proftpd why was not working in some case.
Here are some error output:
227 Entering Passive Mode (10,108,211,224,191,201).
ftp: connect: Connection timed out
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is the current directory
Command: TYPE I
Response: 200 Command okay.
Command: PASV
Response: 227 Entering Passive Mode (172,30,255,230,229,148)
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD
Error: Connection timed out
Error: Failed to retrieve directory listing
Well from here look like passive mod not working ok.
I know that I open the port from firewall , for passive range. However this still was not working.
So it appear that when you are using passive mod, you have to use also and the masqueradeaddress section on proftpd.
So basically you should have something like this:
ServerName "your server name"
PassivePorts 49000 50000
MasqueradeAddress name.ofserver.com
Or you may use your routable ip on masqueradeaddress .
And not forget to open 49000:50000 range port in firewall.
February 29, 2012
Standalone vs inetd
What to use ?
Inetd or standlone server ?
Well I personally chose standalone, however if you have a server with low resources, and a service that you want to run from time to time, then you should go with inetd.
Inetd only spawns the process when it is needed, so the process does not consume resources when no one is using it. However, there is an overhead on each connection as inetd spawns a new process to handle it.
So if you have a heavy used service go with standalone.
