Reset an n8n password on a KVM VPS

Procédure

You can reset access to your n8n instance directly from your server’s Docker command line without losing any workflow. n8n is a workflow automation platform that lets you connect different services and applications together through visual scenarios. This procedure allows you to restore administrator access in just a few secure commands.

The steps

  1. Find the VPS server IP address

    Go to the Overview section of your KVM Panel. In the Server IPs box, note the public IPv4 address of your machine (for example, the fictitious IP 203.0.113.10).

    Reset an n8n password on a KVM VPS
  2. Create a backup snapshot

    Click Snapshots in the left sidebar menu, then click the + Create a snapshot button. This instant image freezes the server’s complete state and ensures your data stays safe before any intervention.

    Reset an n8n password on a KVM VPS
  3. Connect to the server via SSH or console

    Open your terminal and connect with the command ssh root@203.0.113.10 (replacing it with your real IP address). If you do not have direct SSH access, click the Console menu in the KVM Panel to open the noVNC rescue session.

    Reset an n8n password on a KVM VPS
  4. Identify the active Docker container

    In the root terminal, enter the command docker ps. Find the name of the container linked to the n8n service shown in the right-hand column.

  5. Reset n8n user accounts

    Run the command docker exec -it n8n user-management:reset by replacing with the name identified in the previous step. Confirm the operation to reset the instance’s access configuration.

  6. Restart the container and reconfigure access

    Restart the container using the command docker restart . Then open your n8n URL in your browser to recreate the owner administrator account and verify that all your workflows are present.

Troubleshooting common errors during the procedure

Here are the common issues encountered in the console and how to fix them quickly:

  • Changed SSH fingerprint (WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED) — Reset the local entry with ssh-keygen -R before trying the connection again.
  • Docker container not found (No such container) — Check the exact capitalization and name of the container by running docker ps.
  • Insufficient permissions (permission denied) — Switch to the superuser account with the command su - or run your commands with root privileges.

Frequently asked questions

Are my n8n workflows kept after this command?

Yes. The user-management:reset command acts exclusively on the credentials and permissions table. All created flows, saved API credentials, and execution histories remain intact in the Docker volumes.

Why shouldn’t the VPS be reinstalled from the KVM Panel?

The reinstall button completely resets the VPS NVMe disk. This erases the Docker engine, containers, and all volumes containing your creations. Only the internal Docker command should be used.

What should I do if the command says the container cannot be found?

Check the exact spelling of the name returned by the docker ps command. If no container appears, list all stopped containers with docker ps -a and start the n8n container before trying the reset again.

Why does the terminal show a 'Permission denied' error?

This error occurs if you are not connected with administrator privileges. Make sure to open the session as the root user or prefix your commands with sudo.

What should I do if the SSH connection reports a 'Host key verification failed' error?

This message means that the server’s cryptographic fingerprint has changed in your local known_hosts file. Remove the old saved key with ssh-keygen -R 203.0.113.10 (using your VPS IP) and then restart the SSH connection.

Useful links

help.lws.net/a/7953
Was this article helpful?

Yes

No

Read 1 times

Thank you! Feel free to ask questions about our documentation if you would like more information, and help us improve it.

Similar articles

A question about this article?

Ask the LWS team and the community. Answers are published after moderation.

Ask the LWS team and its community a question

GDPR: Controller: LWS-Ligne Web Services. Purpose: moderation and public publication of your question, possible notification of an answer. Legal basis: consent (Art. 6(1)(a) GDPR). Email retention: 90 days after notification, 12 months maximum without an answer. To exercise your rights, see the GDPR section of our Terms and Conditions.