UniFi Default SSH Credentials

Default SSH Credentials in UniFi Network Devices

Whether you are recovering an orphaned access point, performing a manual Layer 3 adoption, or troubleshooting a network failure, knowing the default UniFi SSH credentials is essential. UniFi devices handle default credentials differently depending on their hardware type and their current adoption status.

The Default UniFi Credentials

When a UniFi device is in a factory-reset state (unadopted), it uses standard default credentials. However, these vary slightly between standard network devices and UniFi OS Consoles.

UniFi Independent Gateways:

  • User: root
  • Password: ui or ubnt

UniFi Network Devices (Access Points & Switches):

  • User: ui or ubnt
  • Password: ui or ubnt

Note: For some Consoles and Gateways, SSH is disabled by default.

The "Gotcha": Pre-Adoption vs. Post-Adoption

The most important rule of UniFi credentials is this: Factory defaults vanish the moment a device is adopted.

  • Pre-Adoption: The factory default credentials function perfectly. The device is waiting for instructions.
  • Post-Adoption: The moment you click "Adopt" in your UniFi Network Application, the controller automatically overwrites the default SSH credentials with a secure, randomised password or the one you set.

If your device is showing as "Online" in your controller, the default credentials will no longer work.

Locating Your Post-Adoption SSH Credentials

If you need to SSH into an adopted device for advanced troubleshooting, you must retrieve the new credentials from your UniFi Network Application.

  • To find them in the modern UniFi interface:

1. Open your UniFi Network Application or UniFi OS server

2. Navigate to the UniFi devices tab, which is on the left side of the screen

3. Once you open the dashboard for the UniFi devices, you should see a button called Device Updates and Settings, just click there and a window at the right side will appear

4. Scroll down to the bottom, where you will see the Device SSH settings. The user can be a random user or the username of the main admin of the controller. The password is a randomized set of characters. Just click on the eye icon to reveal the password

  • For older controller versions:

1. Open your UniFi Network Application

2. Navigate to Settings (the gear icon)

3. Go to System > Advanced

4. Scroll down to the Device Authentication section

Troubleshooting: When You Cannot Log In

If you cannot SSH into a device using either the factory defaults or the controller's Device Authentication credentials, you are likely dealing with an "orphaned" device. This happens when a device was adopted by a different controller that you no longer have access to. If the credentials are truly lost, your only option is a physical factory reset.

  • How to factory reset a device:

Locate the physical reset button on the device (usually a small pinhole on the back or bottom). While the device is powered on, use a paperclip to press and hold the reset button for about 10 seconds. Release the button when the device's LED begins to flash or turn off. Once the device reboots and the LED returns to a steady white, it is back to factory defaults, and the default credentials should work again.

  • You can see an example for an access point here:

https://www.youtube.com/watch?v=XneypN1n6Rg

Summary

Understanding UniFi SSH credentials boils down to knowing the state of your device. If it is fresh out of the box or newly reset, the default ubnt/ubnt or root/ubnt credentials will get you in. The moment that device is adopted, you must rely on the Device Authentication settings housed within your central UniFi Network Application. By keeping track of where these credentials live, you can easily troubleshoot, execute advanced commands, and seamlessly manage your network infrastructure.

When does Managed UniFi hosting make more sense?

Managing UniFi at scale introduces operational risk: inconsistent versions, manual backups, expiring certificates, and hardware failures. Many MSPs move to hosted UniFi controllers to centralize infrastructure while retaining full network control.