To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed
WordPress can’t write directly to its files (ownership differs from the PHP user), so it falls back to asking for FTP details.
Please enter your FTP credentials to proceedWordPress needs to access your web serverConnection Information Meaning
WordPress uses the “direct” method only if files are owned by the PHP process user. On self-managed servers fix ownership; FS_METHOD direct forces it but still needs write permission.
Common causes
- WordPress files owned by a different user than PHP-FPM/Apache
- Mixed ownership after manual uploads
- Shared hosting setups requiring FTP
⚡ Quick fix
- chown the WordPress directory to the PHP user
- Optionally define('FS_METHOD', 'direct') once permissions are right
Detailed fix by platform
WordPress
- php
// wp-config.php (after fixing ownership) define('FS_METHOD', 'direct');
Linux
- bash
ps -o user= -C php-fpm8.3 | head -1 # PHP user sudo chown -R www-data:www-data /var/www/html
How to diagnose
- PHP user — Process owner
- Files — ls -l wp-content
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Call to undefined function (WordPress) WordPress: Fatal error: Uncaught Error: Call to undefined function wp_get_current_user() / add_action() / get_header()
- Call to undefined function create_function() WordPress on PHP 8: Fatal error: Uncaught Error: Call to undefined function create_function() / each()
- Critical error WordPress: There Has Been a Critical Error on This Website
Most viewed in WordPress
- There was an error trying to send your message Contact Form 7: There was an error trying to send your message. Please try again later.
- Download failed WordPress: Download failed. A valid URL was not provided / cURL error 60 / Could not resolve host: downloads.wordpress.org
- The REST API encountered an error Site Health: The REST API encountered an error / Your site could not complete a loopback request (cURL error 28)
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 12 Oct 2026