Fix “FTP Connection Information” Error on WordPress Updates (2026)

Seeing the WordPress FTP connection information screen? Does WordPress ask for “Connection Information” with FTP host, username and password every time you update a plugin? We had this exact problem on QuickOnlineTips years ago: every plugin install or WordPress update demanded FTP details, and often timed out even with the right password, so we had to update by hand. The cause was file permissions on our server. Here is how to fix the FTP connection information error in WordPress in 2026.

Quick answer: WordPress asks for FTP details when the web server user cannot write to your WordPress files. The proper fix is to make the files owned by the same user PHP runs as (ask your host, or run chown on a VPS). If ownership is already correct, add define( 'FS_METHOD', 'direct' ); to wp-config.php. As a last resort, save your FTP details in wp-config.php so WordPress stops asking.

Why WordPress asks for FTP connection information

Before updating, WordPress tests whether it can create files in your site folders. If PHP runs as a different user from the one that owns the files (for example, files owned by your account but PHP running as www-data or nobody), WordPress cannot write directly. It falls back to asking for FTP or SSH login details to make the changes.

Fix 1: Correct file ownership (best)

On shared hosting, contact support and ask them to make PHP run as your account user (most modern hosts use PHP-FPM or suPHP-style setups that do this). That is what fixed it for us: our host switched the server to run PHP as our account, and one-click updates worked again with no downtime.

On your own VPS, set the owner to the PHP user, for example:

sudo chown -R www-data:www-data /var/www/example.com
sudo find /var/www/example.com -type d -exec chmod 755 {} \;
sudo find /var/www/example.com -type f -exec chmod 644 {} \;

Replace www-data with your PHP-FPM pool user and the path with your site folder.

Fix 2: Set FS_METHOD to direct

If ownership is correct but WordPress still asks, open wp-config.php and add this line above “That’s all, stop editing!”:

define( 'FS_METHOD', 'direct' );

Only use this when PHP really can write to the files, otherwise updates will fail with permission errors.

Fix 3: Save FTP details in wp-config.php

If you cannot change ownership, store the details so WordPress uses them automatically:

define( 'FS_METHOD', 'ftpext' );
define( 'FTP_HOST', 'localhost' );
define( 'FTP_USER', 'your-ftp-user' );
define( 'FTP_PASS', 'your-ftp-password' );

Plain FTP sends passwords unencrypted, so prefer SFTP or the ownership fix where possible, and keep wp-config.php permissions tight (600 or 640).

After the fix

• Try updating a small plugin to confirm it works.
• Turn on safe automatic updates for plugins and themes.
• If an update gets stuck, see how to fix the “Briefly unavailable for scheduled maintenance” error.
• Need to change a theme file quickly? Here is how to edit WordPress theme files without FTP.

FAQ

Is FS_METHOD direct safe?

Yes, when files are owned by the PHP user on a server only you use. On shared servers with poor isolation, it can be riskier.

Why does the FTP login time out even with the right password?

Many hosts block plain FTP or require FTPS/SFTP. Fixing ownership avoids FTP completely.

What permissions should WordPress files have?

Usually 755 for folders and 644 for files, with wp-config.php at 600 or 640.

Did this fix your WordPress update problem? Tell us in the comments.