How to bypass "admin" replacement?

Community Support
1

Really I would be okay with avoiding the replacement of “admin” credentials or just knowing how to create a new user with the same credentials as the original admin.

I am using an EC2 Debian 12 instance from AWS Academy, these machines require you to set a key for authorization.
Of course, when I run the Hestia installation, the credentials for “admin” get replaced with the new ones and AWS Academy only lets me authorize the remote connection via key, so creating a new user to authenticate as is just not possible.

Does anyone know if I can leave intact “admin” original authorization key?

2

In 1.9 we replace the user with an “user” generated account to solve this issue won’t solve it for now

3

That’s great. Looking forward to it.

4

Nevermind, turned out I was being ignorant, I just needed to change the settings in the file /etc/ssh/sshd.conf to allow password authentication instead and create a new user with sudo permissions.

5

I usually create users like 50 at a time
u101
u102
u103
u104

Then each user is owned by admin.

What exactly are you doing that you need another user with sudo permissions?

You’re on Ubuntu ?
Are you doing node.js or python or something??

6

Each user has one primary domain. Maybe a couple of other sub domains

I like having my usernames with the same length. If makes scripting easier

7

You see, my problem could just be solved by having password_authentication set for SSH, I was just having trouble to log in after installing Hestia, since I am using a VPS that has admin as their log-in user and a set of keys to authenticate.

I just needed another user having sudo so I could then log using root, because I also don’t have the password of root, given it is a VPS.

I just want the root privileges to examine the structure of Hestia, I am right now working on a project that makes a comparative between Hestia, myVesta and aaPanel.

Hope this solves the confusion, I really don’t need anymore help but maybe I did make it sound trickier or more stupid than it was, have a good day.

8

your vps provider INSISTS that ‘they are in control of the admin user’?

I’d find a new VPS provider. I’ve got plenty of affiliate links.

I don’t think that vps providers should screw with ANYTHING except the root user.

PS - one thing that is CLOSE to this same discussion, is I was writing some custom ‘uptime scripts’ yesterday… and I noticed that there is a GROUP called ‘adm’.

I assume that THE admin user is a member of ‘adm’ group.
I don’t know the ramifications of creating OTHERUSER1 and then assigning THEM to the adm group. IF I was designing the system, that’s all it would take.