I've been using Hestia wrong all this time, help :)

Hey Team,

I’ve been using Hestia CP over several different servers over the last 5 years, and i’ve just figured out i have been using it wrong all this time and im hoping someone can help me rectify my mistake.

When i first setup the server, i setup an admin user, and then a regular user … I have been putting all my clients web / email under the regular user.

Recently given the big wp2shell fun, I have been wondering why Hestia doesnt create a new linux user for each website as if one site gets breached then they are all at risk … But then i realise that i should be creating a regular user for each website / email domain that i put on the server … I know what you’re thinking dont worry hahahaha

I want to do things properly asap … Is there any way to propagate the websites / email domains to their own accounts without toooo much downtime or do i have to start all over again?

Really appreciate any help on this.

You can do a lot of this with the CLI.

If you create the users you can move a site and database from one user to another using the v-change-domain-owner and v-change-database-owner there should be no downtime this way.

Now depending how many sites you have and how many users you need to create you also may do the user creation with v-add-user for faster user creation. If you have a lot of users you can probably write a bash script and pass a CSV file with all the info and automate the process of user creation.

I also have been doing it that way but we host about 120 sites so I really don’t want to deal with creating an account for each user. My biggest issue is when I need to restore a single site. Since Hestia does a backup per user account, and not per site. I have to download the entire 50Gb zip just to extract one site. This is the only reason I may decide to separate all sites into their own account.

What I would do is take this information: https://search.brave.com/ask?q=hestiacp+how+to+migrate+site+from+one+user+to+another&conversation=095b050b0cbf0789fec44a903441006e7188

Roll up a new server, migrate all the data to it, and experiment on writing a wrapper conversion script until it was good enough to use.