Skip to Content
Browse documentation

Change Root Password in WAP

Change the Eenos server root password through WAP, use the password controls and verify access safely after the change.

Open Eenos → Preferences → Change Root Password to set a new password for the server's operating-system root account. This is the root credential used to administer the server, rather than a hosting-account or reseller password.

Before you begin

  • Sign in to WAP with administrator access over HTTPS. See First Login.
  • Confirm the server you intend to change and have an independent recovery method, such as your provider's console.
  • Prepare a unique password and store it in your approved password manager.
  • Identify integrations that use the root password so their saved credentials can be updated after the change.

The operation is disabled in demo sessions. The page has no current-password field; it relies on the authenticated WAP session to authorize the request.

This changes a server administrator credential

Make sure you can recover access before submitting. Keep a trusted administrative session open until you have checked a separate login with the new password. Do not share the password in support tickets, screenshots or logs.

Fields and controls

Field or controlPurpose and validation
New Root PasswordRequired. Enter the new root password. The input is masked and marked as a new password for browser autofill.
Show passwordEye button beside the new-password field; toggles visibility so you can inspect the value. Hide it again before sharing your screen.
Generate passwordFills and reveals a generated 32-character password in the new-password field. Review and securely store it, then ensure the confirmation matches.
Password strength indicatorProvides feedback as you enter a password; it is guidance rather than proof that the credential is safe.
Confirm New Root PasswordRequired. Must match New Root Password.
Change PasswordSubmits the change after form validation.

The page recommends at least eight characters with letters, numbers and special characters. Prefer a long, unique password. The current server-side form checks that both fields are nonempty and match; it does not enforce that displayed length or complexity recommendation. The form also strips leading and trailing whitespace, so do not rely on spaces at the ends of a password.

There is no option to choose a different username, change SSH authentication policy or rotate an SSH key on this page.

Change the password

  1. Enter a new value in New Root Password, or select Generate password.
  2. Store the intended password securely before continuing.
  3. Enter the same value in Confirm New Root Password. Check it again if you generated or edited the first field afterwards.
  4. Select Change Password once.
  5. Look for Root password changed successfully.
  6. With recovery access and your current administrative session still available, verify a separate WAP root login using the new credential.
  7. Update approved integrations that authenticate with the root password.

The server hashes the new password and invokes the operating-system password update for root. It records a configuration audit event indicating success or failure. No password value is included in that audit event by this view.

This action does not change SSH keys or enable SSH password authentication. Whether a password can be used for SSH remains subject to the server's SSH policy. Do not assume that every existing authenticated session is terminated by this change; the view does not explicitly revoke all sessions.

Errors and recovery

MessageWhat to do
Please enter a new root passwordFill the first field.
Please re-enter the new root passwordFill the confirmation field.
The passwords do not matchRe-enter both fields with the intended matching value.
Demo server, this operation is unavailableThis session cannot change the root password.
Unable to change root passwordVerify the server's actual authentication state using an authorized recovery path and inspect server-side errors before retrying. Do not assume the new password took effect.

If a successful change used an unintended password, use a still-authorized administrative session to set another known, securely stored value. If access is lost, use the server provider's documented console or recovery procedure. This page has no automatic password rollback.

Do’s and don’ts

  • Do confirm server identity and recovery access first.
  • Do use a unique password and verify a fresh login after success.
  • Do review integrations that store the root credential.
  • Do not interpret the strength indicator as server-side enforcement of a password policy.
  • Do not close every working administrative session before verification.
  • Do not change SSH policy just to test a password when that access method is intentionally disabled.
  • Do not reuse a hosting customer's password for root.

Previous: Server Time. Next: Change Hostname.