Recommended Free Tools
If you cannot sign in to a self-hosted Coolify root account and an emailed reset link is unavailable, reset the password from the server terminal. SSH to the host, verify that the coolify container is running, and run Coolify’s password-reset Artisan command. The operation changes only the root password; it does not restart Coolify or interrupt deployed applications, databases, or services.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
This procedure is for self-hosted Coolify installations. Coolify Cloud users cannot access the container that runs the command and should contact the Coolify team for account recovery.
As an Amazon Associate I earn from qualifying purchases.
Before you begin
Prepare the access and information needed to complete the reset without locking yourself out again.
Confirm that this is a self-hosted installation
The terminal method requires access to the machine that runs Coolify’s Docker container. It is appropriate for a server you administer, whether that server is at a cloud provider, in a data center, or on your own hardware. A Coolify Cloud account does not provide shell access to the underlying container, so the documented command cannot be used there.
Have SSH access to the host
You need an SSH account that can run Docker commands. The documented example uses the root account and a server IP address:
ssh root@<server-ip>Replace <server-ip> with the address of the machine running Coolify. If your organization disables direct root SSH access, connect with an administrative account and use sudo for the Docker commands, provided that account is allowed to run Docker.
Free tools Windows power users keep installed
One-click scans. No signup required.
Know the current root email address
A password reset does not change the account’s email address. You will need the root account’s current email when you return to the login page, unless the email itself is also wrong or inaccessible and you perform the separate email-change procedure described later.
Choose and store a strong password
Have a long, unique password ready before opening the reset prompt. The terminal command checks that the two entries match, but it does not enforce the password rules shown in the dashboard. Use a randomly generated password that is not reused elsewhere and save it in a password manager. Avoid pasting it into shell history, chat, tickets, or screen recordings.
The complete terminal reset
Run these steps in order. Keep the SSH session open until you have verified that the new credentials work.
1. Connect to the Coolify server
- Open a terminal on your workstation.
- Connect to the host with SSH, for example
ssh root@<server-ip>. - If you use a non-root administrative account, confirm that it can invoke Docker. Add
sudoto the commands below when required.
Do not run the command on your personal computer unless Coolify is actually installed there. It must be executed on the server that owns the Coolify container.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →2. Check the container state
Verify that the container is available before attempting the reset:
docker inspect --format '{{.State.Status}}' coolifyThe expected output is:
runningWith a non-root Docker account, use:
sudo docker inspect --format '{{.State.Status}}' coolifyThe command reads the state of the container named coolify; it does not modify anything. A result of running means the next command can be sent to the application.
3. Start the root-password reset
Run Coolify’s Artisan command inside the container:
docker exec -it coolify php artisan root:reset-passwordUse the equivalent with sudo if your SSH account needs elevated Docker permission:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minutesudo docker exec -it coolify php artisan root:reset-passwordCoolify prompts you to enter the new password twice. Terminal input is intentionally not echoed: you will not see characters, dots, or asterisks while typing. Enter the password carefully at both prompts and press Enter after each entry. The command verifies that the entries match before applying the change.
4. Sign in and verify the result
- Open the Coolify login page in a private or incognito browser window. A private window prevents an old session or cached form from making the test misleading.
- Enter the root account’s current email address.
- Enter the new password.
- If two-factor authentication is enabled, enter the current 2FA code.
Once the login succeeds, close the SSH session only after you have confirmed that the dashboard loads and that you can reach the account settings needed for any follow-up work.
What the reset changes—and what it does not
Only the root password is changed
The command updates the password for the root account. It does not alter the email address, other users, deployed applications, databases, or services. It also does not restart Coolify.
Running workloads are not interrupted
Because the procedure changes account data without restarting the Coolify container, deployed workloads continue running. The reset is an administrative credential operation, not a redeployment or maintenance restart.
Every root session is signed out
A successful reset signs the root account out on every device. If another browser, terminal-based dashboard session, or shared workstation was logged in as root, that session must authenticate again with the new password.
All root-owned API tokens are revoked
The reset revokes every API token owned by the root account. Other users’ sessions and tokens are unaffected. Revoked tokens cannot be restored, so any automation, scripts, integrations, or deployment tooling that used a root token will stop authenticating until you create replacement tokens.
Create replacement tokens deliberately
After signing in, audit where the old root token was used. Create new tokens only where they are required, give them the minimum practical scope, update the dependent secret stores, and remove the obsolete values. Do not assume a token will continue working merely because an application is still running; token revocation affects authentication, while already-running services may continue independently.
Choosing the right recovery method
The correct method depends on which part of the login flow is unavailable. Use the following decision guide before changing anything.
| Situation | Access still available | Appropriate action | Main dependency |
|---|---|---|---|
| You can sign in and only want to change the password | Coolify dashboard | Change the password from the root profile or account settings | Existing authenticated session |
| You forgot the password, but the reset email works | Login email inbox | Use the dashboard’s emailed password-reset link | Transactional email delivery and access to the inbox |
| You forgot the password and email recovery is unavailable | SSH plus Docker permission | Run docker exec -it coolify php artisan root:reset-password |
Host access and a running Coolify container |
| The password is known, but the email address is wrong or inaccessible | SSH plus Docker permission | Run the separate root email-change command | Host access; the command changes the email immediately |
| The password is known, but 2FA blocks sign-in | Account recovery access | Follow Coolify’s separate 2FA reset procedure | Verification of the current password and the applicable 2FA procedure |
The terminal reset is the least dependent on email, but it cannot be performed without access to the host and permission to run Docker.
Troubleshooting the command
The inspect command says the container is not running
The reset command must execute inside the Coolify container. If the inspect output is not running, do not repeatedly submit the reset command. First determine why the container is stopped using your normal Docker and server-management procedures, then rerun the inspect command and continue only when it reports running. Starting or repairing a stopped production container is a separate operational task from changing the password.
Docker reports a permission error
Your SSH account does not have permission to access the Docker daemon. Reconnect with an account that has that permission or prefix the command with sudo:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →sudo docker inspect --format '{{.State.Status}}' coolifysudo docker exec -it coolify php artisan root:reset-password
If your organization restricts sudo, ask the server administrator to run the two commands. Do not weaken host permissions merely to complete a password reset.
Docker cannot find a container named coolify
The documented procedure expects the container name coolify. A “no such container” result means either you are connected to the wrong server or this installation uses a different deployment layout or container name. Confirm the host and the installation documentation before substituting a name. Do not run an Artisan command in an unrelated container.
The password prompts appear blank
Blank terminal input is normal for secret entry. The terminal does not echo the characters. Type the password, press Enter, type it again, and press Enter. If the command reports a mismatch, start it again and enter both values carefully.
The command completes but the browser still rejects the login
- Verify that you are using the root account’s current email, not an email belonging to another Coolify user.
- Open a private browser window to avoid an old session, stale form data, or a password-manager entry for the previous password.
- Check that the password was entered exactly as created; keyboard layouts and password-manager autofill can change characters.
- If 2FA is enabled, enter a current code from the configured authenticator. A correct password does not bypass 2FA.
- Confirm that the command was run on the server hosting the Coolify instance you are trying to access.
Do not create repeated password changes while troubleshooting. First isolate whether the failure is the email, password, 2FA, browser session, or wrong host.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Automation stopped after the reset
Look for root-owned API tokens in deployment scripts, CI/CD variables, monitoring integrations, and secret stores. The reset revokes those tokens even though it leaves applications running. Generate replacement tokens after signing in, update each dependent system, and test one integration at a time. Other users’ tokens do not need replacement solely because the root password changed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If the email address is also a problem
Changing the password does not repair an inaccessible or incorrect root email. For a self-hosted instance, Coolify documents this command:
docker exec -it coolify php artisan root:change-emailUse sudo docker exec -it coolify php artisan root:change-email when necessary. The email changes immediately and does not send a verification message. Because this is a separate operation, verify the new address carefully before leaving the server. After changing it, use the new address with the password you set or already know.
If two-factor authentication is the blocker
A password reset and a 2FA reset solve different problems. If you know the password but cannot produce a valid 2FA code, use Coolify’s separate Reset 2FA procedure rather than repeatedly changing the password. Clearing 2FA removes the authenticator setup and the associated recovery codes, so treat it as a security change: regain access, enroll a new authenticator, and store fresh recovery codes securely. Follow the current official 2FA instructions for the version of Coolify you operate.
Security steps immediately after recovery
Confirm the account identity
Check the root email in the dashboard and ensure it is an address your team controls. If you changed it during recovery, record the change in your operational documentation without recording the password.
Rebuild authentication dependencies
- Create replacement root API tokens only for integrations that genuinely require root privileges.
- Update secret stores and automation systems, then remove revoked token values.
- Ask other administrators to use individual accounts rather than sharing the root login.
- Review active sessions and sign in again only on trusted devices.
Protect the new credential
Store the password in an approved password manager, enable the organization’s access controls, and keep recovery information available to the authorized administrators who would need it during an outage. Never place the password in shell scripts or command history.
Server sizing is separate from password recovery
Coolify’s self-hosted documentation lists a baseline of 2 CPU cores, 2 GB of RAM, and 10 GB of disk space. Those figures describe infrastructure requirements for running a self-hosted installation; they are not additional requirements imposed by the password-reset command. A reset does not require resizing the server, stopping deployed services, or provisioning new storage.
When to stop and escalate
Contact the server or Coolify administrator instead of guessing when you lack SSH access, cannot establish which host runs the instance, do not have Docker permission, or see a container layout that does not match the documented coolify name. For Coolify Cloud, contact the Coolify team because the underlying container is not available to customers. Escalation is safer than running a credential command against the wrong environment or changing host permissions without authorization.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
