WordPress asks for FTP details during plugin updates

You can be logged into WordPress as an administrator, able to edit pages, install content and change settings, then get stopped cold by an FTP credentials screen while updating a plugin. It feels like WordPress has forgotten who you are. Usually, it hasn’t.

Abstract server access paths beside plugin update symbols

There are two separate permissions involved. WordPress permission decides whether your user account may request the update. Server filesystem permission decides whether the PHP process running WordPress may write the new plugin files into the relevant directory. They are related only in the sense that both can ruin an otherwise ordinary afternoon.

For a service business in Dubai, the UAE or the UK, stalled updates tend to become a staff problem quickly. Someone tries random hosting passwords, somebody else changes permissions broadly, and a routine maintenance task becomes a riskier website repair job.

The FTP prompt is asking about transport, not your WordPress login

When WordPress cannot use direct filesystem access, it may ask for connection details so it can use another route to write files. The prompt is not evidence that your WordPress administrator login is incorrect.

WordPress selects a filesystem method from options including direct access, SSH2 and FTP. Its filesystem method selection logic checks write access and ownership when considering direct access, while configuration or filters can influence the method selected.

In plain terms: WordPress is trying to establish how the server should write the update files. Resolve the filesystem access model instead of guessing which password to enter.

Start by confirming it is a genuine update request

First, make sure the prompt appears from the normal WordPress update flow in the dashboard, for a known plugin or theme, and not from a plugin-branded screen with an unrelated message. Record the plugin name, the update action, the exact prompt wording and the time it appeared.

A redacted screenshot is useful. Remove usernames, hostnames, paths and credentials before sharing it. The point is to preserve the evidence, rather than asking a developer or host to work from somebody’s memory of a pop-up that appeared last Tuesday.

If the site has recently moved hosts, changed PHP versions, had a server rebuild or been handed over from another agency, note that too. These changes often alter the process running PHP or the ownership of files without preventing ordinary dashboard editing.

Why a migrated site can still edit pages but fail updates

Take a common illustrative case. A WordPress site is migrated to a new host. The owner can amend service pages, publish a news item and update a phone number. Then a plugin update requests FTP credentials.

Page editing mostly writes content to the database. A plugin update needs to download, unpack, replace and remove files on disk. If the web server’s PHP process does not own those directories, or cannot write through the intended method, WordPress may fall back to requesting another transport.

That is why administrator access inside WordPress does not prove that its PHP process can update files directly. They are different layers of the setup.

Ask the host to inspect the access model

This is usually a hosting or server administration question before it is a WordPress configuration question. Ask whoever manages the server to inspect the process identity used for the website, the ownership of the WordPress files and directories, the applicable write access, and the intended supported transport for updates.

Give them a specific question: can the PHP process for this site write safely to the WordPress content and plugin directories using the expected update method? That is far more useful than asking whether FTP credentials are available.

  • Confirm which user or process runs PHP for the affected site.
  • Check ownership on the WordPress installation and relevant content directories.
  • Confirm whether the hosting platform expects direct access, SSH2 or FTP-based transport.
  • Check whether a configuration setting or filter is deliberately overriding the normal method.
  • Confirm there is a current backup or recovery route before retrying the update.

Do not treat an FTP prompt as an invitation to try every password in the business. It can lead to a locked hosting account, a forgotten old credential being used against the wrong environment, or an update being attempted without any recovery plan.

Keep this separate from a directory creation error

An FTP credentials prompt and a message saying WordPress could not create a directory can sit near each other, but they are not the same diagnosis. The prompt concerns how WordPress intends to connect to the filesystem. A directory creation failure is where the selected process or transport has already failed to create a needed location.

If the update gets as far as a directory error, use the more focused WordPress directory ownership diagnostic to investigate that boundary. Do not skip straight there just because an FTP box appeared first.

Agree the supported route before changing configuration

A forced filesystem method can be an implementation choice, but it should be made by the administrator who understands the hosting setup, deployment process and recovery route. Hard-coding a method merely to make one update screen disappear can conflict with how the server is meant to operate.

The same applies to broader permission changes. They can mask the actual ownership or process issue and leave the next person maintaining the site with a mystery to unpick. No one wants that as a handover note.

Where plugin updates require paid renewals or account access, keep licence ownership separate from server write access. A valid plugin licence allows access to the update package. It does not grant the PHP process permission to install it. An audit of WordPress plugin licence ownership can help keep those responsibilities clear when several people or agencies have touched the site.

Verify one update with recovery available

Once the host or administrator has confirmed the intended transport, take a restore point and retry one known update during a sensible maintenance window. Check the plugin version afterwards, confirm the site still loads, and test one important journey such as a contact form submission or booking enquiry.

That final check matters. A green update notice only confirms that WordPress completed its task. It does not confirm that a key form, cache integration or third-party service still behaves as expected.

When the issue needs a wider repair review

If the FTP prompt arrived after a migration, hosting change, failed update or unexplained file ownership changes, it may sit within a wider maintenance handover or website repair issue. In that case, a scoped WordPress website repair review is a better route than repeatedly trying credentials from old emails and hosting portals.

FAQ

Why is forcing a filesystem method an administrator decision?

The correct method depends on how the hosting environment runs PHP, who owns the files, whether deployments are managed elsewhere and which transport the host supports. Forcing direct access, SSH2 or FTP without checking those conditions can conceal the underlying setup problem or conflict with the host’s intended access model.

Can I use my WordPress administrator password in the FTP prompt?

Usually no. A WordPress administrator password is for your CMS account. FTP or SSH credentials, where they are genuinely required, are server or hosting credentials. Only enter them after confirming the prompt is legitimate and the host has confirmed the correct supported connection route.

If a plugin update asks for FTP credentials and you are unsure what it expects, request an update-access review with the hosting setup and redacted prompt. It is a more sensible starting point than changing settings until the pop-up gives up.