How can I stop WordPress from prompting me to enter FTP information when doing updates?

How can I stop WordPress from prompting me to enter FTP information when doing updates?

Solutions Collecting From Web of "How can I stop WordPress from prompting me to enter FTP information when doing updates?"

If you edit your wp-config.php file you can preload these FTP settings as constants read by WordPress. Keep in mind, on a shared host, you should be mindful of possible security implications.
See Editing wp-config.php for more information.

Your settings will vary, but these work for me and my hosting setup. I’ve included some of the unused constants, prefixed:

define('FS_METHOD', 'direct');
define('FTP_BASE', '/usr/home/username/public_html/');
define('FTP_CONTENT_DIR', '/usr/home/username/public_html/');
define('FTP_PLUGIN_DIR ', '/usr/home/username/public_html/');
// define('FTP_PUBKEY', '/home/username/.ssh/');
// define('FTP_PRIKEY', '/home/username/.ssh/id_rsa');
define('FTP_USER', 'my-ftp-username');
define('FTP_PASS', 'my-ftp-password');
define('FTP_HOST', '');
// define('FTP_SSL', false);

Check your file ownership. When the user that apache runs as can write to the wordpress directories, then the integrated upgrade process all just works without ftp. The FTP credentials are for if the web server doesn’t have the right priviledges on your files, then wordpress prompts you for your FTP details, and attempts to use those to FTP back to the same server it is on to be able to write the files it needs.

It seems that not only does WordPress check if the directories are writable, but it checks if the Apache user OWNS the directories (or at least, if the Apache user owns the temporary file it creates). Observe these lines of code at /wp-admin/includes/file.php: get_filesystem_method():

if ( $temp_handle ) {
    if ( getmyuid() == @fileowner($temp_file_name) )
        $method = 'direct';

So, a quick solution will be to issue this command and give ownership of the whole WordPress installation to Apache:

sudo chown -R www-data wordpress/

Where www-data is the Apache user, and of course wordpress is your WordPress installation folder.

I have further documented my solution here:

When fine tuning Apache 2.4 through EasyApache4 for improving website load speed in a Centos 7 PHP 7 server, I had enabled mod_pagespeed. On enabling it, it will automatically disable mod_ruid2 and mod_cgi (and enable other two modules). When disabling mod_pagespeed, it will not re-enable mod_ruid2 automatically – it will re-enable only mod_cgi. Without mod_ruid2 WordPress will request the FTP credentials.

There is no need to hard code wp-config.php or set file permissions (dangerously) to 777. Just enable mod_ruid2 manually, restart Apache and the FTP/file permission issue is solved. WordPress and plugins now can be updated as usual and media uploaded to the WordPress gallery. It works right away.

I just checked that when changing from MPM Prefork into Worker, it will disable mod_ruid2. When reverting from Worker to Prefork it will not enable mod_ruid2, causing the issue described in this post.

In both cases, the key is to check and enable mod_ruid2.

Hope to have helped.

1) I couldn’t agree with the answer above because of it being too generic

1a) I just dont want to go change ownership of all my files recursively(as in using a shotgun to kill a musquito). Especially as this work perfectly before.

1b) WordPress having the “sneaky” feature of all of a sudden ask you for credentials for ftp

2) So I started digging deeper using Ardee Aram’s his lead.
I went checking in the file.php file and checked its ownership. Seems like the file.php is dependent on it’s own ownership (which was incorrectly set as root).

Fix : chown www file.php

NOTE: Replace www with whatever your distro or settings are (you could use ps aux | egrep “php|http” and see what its ownership is in the first column.

I hope this helps someone else from getting frustrated about this.
I don’t even get why wordpress doesn’t “complain” in the first place and then proposes to use the FTP alternative. Now it’s like a “feature” that all of a sudden gets introduced.