Creating a Directory "authorized_keys" for SSH Causes Both Console & Shell to Become Unusable

Description

New user here, so most people probably won't make my mistake, but still:
(1) I used the Shell to "mkdir" "~/.ssh/authorized_keys". Stupid, yes, but it's what I did.
(2) I repeatedly receive the error "IsDirectory: authorized_keys".
(3) But there's no way to rectify it, because Shell remains blank. It shows the "RECONNECT" button, but it doesn't reconnect.
(4) Even the console is bugging out. It remains mostly blank, displays something for a nanosecond, then returns to blank again.
(5) I AM running TrueNAS in a VM, so I can easily restart, but hopefully no one else is as silly as I am, LOL.

Session ID: 11ebecfa-ca74-c32a-ee11-bfccf7e1038a

Problem/Justification

None

Impact

None

Activity

Show:

Bug Clerk 3 days ago

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk 3 days ago

Unfortunately we cannot handle every single edge case scenario caused by manual changes to the system:

Warning: the supported mechanisms for making configuration changes
are the TrueNAS WebUI, CLI, and API exclusively. ALL OTHERS ARE
NOT SUPPORTED AND WILL RESULT IN UNDEFINED BEHAVIOR AND MAY
RESULT IN SYSTEM FAILURE.Welcome to TrueNAS

Michelle Johnson 3 days ago

Thank you for your report, !

This issue ticket is in the queue for review. An Engineering representative will update with further details or questions.

Not Applicable
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Priority

More fields

Katalon Platform

Created 3 days ago
Updated 3 days ago
Resolved 3 days ago