View source for WHM Restore Error: Username Conflicts With Unmanaged MYSQL User

== Cannot create or restore account: ''The system could not create the user "username" because it conflicts with an unmanaged MySQL database user'' ==

=== Overview ===
When attempting to create or restore a cPanel account in WHM, the restore may fail with an error stating that the system cannot create the account username because it conflicts with an unmanaged MySQL database user.

This usually occurs when MySQL already contains a user and/or database name that matches (or begins with) the cPanel username being restored.

=== Error Message ===
You may see an error similar to the following:

<pre> Failed to create the account: (XID xxxxxx) The system could not create the user "username" because it conflicts with an unmanaged MySQL database user. at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 1380. </pre>

=== Cause ===
cPanel account restores rely on creating:

A Linux system user (cPanel username)

Related MySQL database users and databases that usually follow the naming pattern:

<code>username_dbname</code>

<code>username_dbuser</code>

This error occurs when one of the following already exists on the destination server:

A MySQL user named exactly <code>username</code>

A MySQL user starting with <code>username</code> (example: <code>username_wp</code>)

A MySQL database starting with <code>username</code> (example: <code>username_wordpress</code>)

Leftover MySQL users/databases from an old/deleted account

MySQL users/databases created manually outside of cPanel (unmanaged)

Because cPanel detects these objects as ''unmanaged'', it blocks the restore to prevent conflicts and permission issues.

=== Resolution / Workaround ===
To resolve the issue, you must locate the conflicting MySQL user/database and remove or rename it (only if it is safe to do so).

{{Warning|Do not delete any MySQL user or database unless you are sure it is not required by an active website/application. Always take backups before making changes.}}

== Find the Conflicting MySQL User / Database (Root Access) ==

=== Step 1: Access the server as root ===
Log in to the server as the <code>root</code> user using either:

WHM → ''Terminal''

SSH access

=== Step 2: Access MySQL ===
Run:

<pre> mysql </pre>

=== Step 3: Switch to the mysql system database ===
Run:

<pre> use mysql; </pre>

=== Step 4: Locate conflicting MySQL users ===
Run the following query to locate MySQL users that match the cPanel username pattern:

<pre> select User, Host from user where User like "username%"; </pre>

=== Step 5: Locate conflicting database permission entries ===
Run:

<pre> select Host, Db, User from db where Db like "username%"; </pre>

=== Notes ===

Replace <code>username</code> with the actual cPanel account username you are restoring.

The <code>%</code> symbol is a wildcard, which helps locate partial matches like:

<code>username_wp</code>

<code>username_db1</code>

<code>username_site</code>

== Additional Checks (Recommended) ==

=== List databases matching the username ===
Run:

<pre> SHOW DATABASES LIKE 'username%'; </pre>

=== List user grants (to confirm what the user can access) ===
If you discover a conflicting MySQL user, you can review its grants:

<pre> SHOW GRANTS FOR 'username'@'localhost'; </pre>

(Replace <code>localhost</code> with the correct host if needed, such as <code>%</code> or an IP.)

== What to Do After Identifying the Conflict ==

Once you identify the conflicting MySQL database or user:

Determine whether the MySQL user/database is still required by any live website or service.
If it is not required, remove it or rename it safely.
Retry the account restore in WHM.

Because the correct action depends on what the MySQL user/database is being used for, a systems administrator or database administrator should decide the safest approach.

== Common Fix Options ==

=== Option 1: Remove the conflicting MySQL user (if safe) ===
If the MySQL user is confirmed unused, it can be removed:

<pre> DROP USER 'username'@'host'; </pre>

Example:

<pre> DROP USER 'username'@'localhost'; </pre>

=== Option 2: Remove the conflicting database (if safe) ===
If the database is confirmed unused:

<pre> DROP DATABASE username_database; </pre>

=== Option 3: Rename objects instead of deleting (safer for investigation) ===
If you are unsure whether the objects are needed, renaming can be safer than deleting.

Database rename example:

<pre> RENAME TABLE old_db.table1 TO new_db.table1; </pre>

(For full database renaming, it is usually done via dump/import or admin tools depending on the environment.)

=== Option 4: Restore the account under a different username ===
If you cannot remove the conflict safely, you can restore the cPanel account using a different username (example: <code>username1</code>).

This avoids the conflict but may require updating application/database configuration afterward.

== Final Step ==

After resolving the conflict, retry the restore:

WHM → ''Restore a Full Backup/cpmove File''
or

WHM → ''Transfer Tool''

The account restore should complete successfully once no conflicting MySQL objects exist.