SSH superuser access to NAT

[FormattinG]

can you explain how you managed to use sudo -i thanks

[tommi2day]

there is no user named "root" in TOS, but the installation user is already the superuser but not named as root. no need for sudo afterwards. You can check this with id command.If it returns "uid=0" which means it has "root" privileges.

[PoKeD]

Good afternoon, could you explain how you achieved superuser status? I am having problems creating Docker containers and configuring Tailscale, as it does not allow me to activate the exit node via SSH.
Thank you

[IrisLi]

After accessing TNAS through SSH terminal, enter the following command

Code: Select all

id

[PoKeD]

Hello again, yes, doing id I observe that I have the id 0 of administrator, but equally if I have to modify a file for example of etc/ it does not leave me and tells me access denied.

How can I activate root user?

Thank you

[neoz]

Hi,

sudo -i command doesn't work. The "superuser" (or "superadmin",...) should be the user created in the installation. The user root account is disabled for prevent security reasons.

The sudo -i command reference in the telnet/terminal page configuration is a translation error. If you select the english language the reference to sudo -i disappears from the text. But in other languages (for example spanish) it's being displayed.

[PoKeD]

Thanks

[henryj]

Your current user likely doesn’t have sudo rights, and root access is disabled by default. Use the NAS admin account or check the web interface to enable root or grant sudo privileges. For installing databases, using Docker (if supported) is the easiest way without full root access.

[davidvisokey]

I agree—without sudo access, it’s really hard to fix problems or make changes. It feels too restrictive, and there should be a way to let trusted users do what they need to.