# F5OS login with admin/root failed via console

**URL:** <https://community.f5.com/t/f5os-login-with-admin-root-failed-via-console/76787>\
**Category:** Technical Forums\
**Tags:** management, f5os\
**Created:** [December 23, 2025, 10:59am UTC](https://community.f5.com/t/f5os-login-with-admin-root-failed-via-console/76787 "2025-12-23T10:59:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stefan\_Klotz](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/stefan_klotz/32/19800_2.png) [@Stefan\_Klotz](https://community.f5.com/u/Stefan_Klotz)\
**Post date:** [December 23, 2025, 10:59am UTC](https://community.f5.com/t/f5os-login-with-admin-root-failed-via-console/76787/1 "2025-12-23T10:59:55Z")

</div>

Right now we have a new rSeries installed, which is currently only accessible via console cable.  
First login with default password was fine and changing password was also successful.  
Then I prepared the device with our default configuration including TACACS authentication. Also appliance-mode is enabled. All configurations were commited successfully.  
Now when I try to login in again, it failed with “login incorrect” error, but the password is definitely correct.  
What’s the reason for this and how can I get access again? Or do I need to wait until the management port is up and TACACS server is reachable?  
Or how can I fully reset the device again? Power cycle and then interrupting the boot process? Is there a documentation available, how to perform this?  
Thank you!

Regards,  
Stefan

---

<div class="post-metadata">

**Author:** ![Jmtaylor](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/jmtaylor/32/22145_2.png) [@Jmtaylor](https://community.f5.com/u/Jmtaylor)\
**Post date:** [December 26, 2025, 6:22pm UTC](https://community.f5.com/t/f5os-login-with-admin-root-failed-via-console/76787/2 "2025-12-26T18:22:07Z")

</div>

@Stefan_Klotz &nbsp; Hello Stephan,

I found some articles that should help with this, I&nbsp; had AI system format for easy reading.

## Recovery Options

### Option 1: Disable Appliance Mode (Recommended)

Once you can access the device with your admin account:

config system appliance-mode config disabled commit exit

**Important:** &nbsp;This change takes effect immediately without requiring a reboot, and running tenants will not be affected.

### Option 2: Factory Reset (If Necessary)

If you need to completely reset the device, follow KB K20024872: Restore the rSeries configuration to factory default settings ([https://my.f5.com/manage/s/article/K20024872](https://my.f5.com/manage/s/article/K20024872)):

**Via Console:**

config system database reset-to-default proceed yes commit exit system reboot

**Note:** &nbsp;This will delete ALL configuration including passwords and management IP settings. You’ll need to reconfigure everything from scratch using the console.

### Option 3: Password Recovery (If Needed)

If you need to recover the root or admin password, follow KB K000134739: Recover the root or admin user password on F5 rSeries system ([https://my.f5.com/manage/s/article/K000134739](https://my.f5.com/manage/s/article/K000134739)). This involves:

1. Accessing the AOM Command menu via console (ESC+Shift+9)
2. Power cycling the system
3. Interrupting the GRUB boot process
4. Adding&nbsp;rd.break&nbsp;to the boot parameters
5. Entering single-user mode to reset the password

**Important:** Password recovery does NOT disable appliance mode - you’ll still need to disable it separately.