u2u2secured
Documentation menu
WordPress

Install the plugin

A standard WordPress plugin upload. Nothing on the server needs a shell.

Available in the WordPress plugin directory

The plugin is listed on WordPress.org as DollarMates U2 Secured Authenticator, so the quickest route is to search for it from inside your own site — WordPress then handles updates for you like any other plugin. The manual upload below is only needed if your site blocks installs from the directory.

View the plugin on WordPress.org · Download the latest ZIP

Install from the directory

  1. 1In WordPress, go to Plugins → Add Plugin and search for DollarMates U2 Secured Authenticator.
  2. 2Install Now, then Activate.
  3. 3A new Settings → U2 Secured screen appears. The rest of the setup happens there.

Or upload the ZIP by hand

Use this if your site cannot install from the directory — some managed hosts disable it, and some sites keep plugin installs behind a deploy process.

  1. 1Download the ZIP using the link above.
  2. 2Go to Plugins → Add Plugin → Upload Plugin and choose the file.
  3. 3Install Now, then Activate. Settings → U2 Secured appears as before.
  4. 4Updates will not arrive automatically on this route — WordPress only offers an update for a plugin it installed from the directory, so repeat this upload when a new version ships.

Requirements

  • PHP 7.4 is the floor. The plugin declares Requires PHP: 7.4, and WordPress refuses to activate it on anything older.
  • WordPress 6.0 or later.
  • PHP’s sodium extension is required for the TOTP fallback, together with U2AUTH_ENCRYPTION_KEY (see Connect). Without it, push approvals and recovery codes still work — only the TOTP option is withheld.

If the upload fails on file permissions

WordPress reports “the update cannot be installed because some files could not be copied” without naming the file, which sends you looking in the wrong place — it is file ownership under wp-content/plugins, not a fault in the package. And despite the alarming “Removing the current plugin…” line that appears above it, the existing plugin directory survives. Make sure the web-server user owns the plugin directory, then upload again.