We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on Vesta 2.0 and expect to release it by the end of 2024. Read more about it: https://vestacp.com/docs/vesta-2-development
Switching to vesta from bare metal, few questions
Switching to vesta from bare metal, few questions
I'm going to be installing vesta on my server soon. I have a running site on it now running with a LEMP stack with postfix for smtp, memcached, and letsencrypt.
I know when I run the install all of my settings will get erased and it will be like a new server for the most part.
Will this wipe all of the mysql databases? Will it give me the ability to change the mysql root password? (I forgot it and its on my list of things to do).
Will I be able to use my existing letsencrypt cert or will I have to make a new one?
Will I need to move all of my web site folders somewhere else or can they all stay where they are?
Will I get to specify where the mysql databases get stored in the file system? I don't want it on the ssd, I want it on the raid with the website.
Thanks for helping me prepare. If there's an easier way, please let me know, lol.
I know when I run the install all of my settings will get erased and it will be like a new server for the most part.
Will this wipe all of the mysql databases? Will it give me the ability to change the mysql root password? (I forgot it and its on my list of things to do).
Will I be able to use my existing letsencrypt cert or will I have to make a new one?
Will I need to move all of my web site folders somewhere else or can they all stay where they are?
Will I get to specify where the mysql databases get stored in the file system? I don't want it on the ssd, I want it on the raid with the website.
Thanks for helping me prepare. If there's an easier way, please let me know, lol.
Re: Switching to vesta from bare metal, few questions
Anybody have any ideas on any of these questions?
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Switching to vesta from bare metal, few questions
You can't install vesta on an existing server that is already running mysql, php, ... the best way is to install new server install vestaCP and copy all your websites to vestaCP.
Re: Switching to vesta from bare metal, few questions
The docs say you can force the install. I don't have the flexibility to just start a new server. I have one dedicated server and my site is running on it right now. Surely there's a way I can get this going?
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Switching to vesta from bare metal, few questions
Yes, you can force the installation. The installation will work. But your existing websites will not exist in VestaCP, so you need to move everything to the correct place. All your MySQL databases are not in VestaCP so again you need to move this.
You need to know that if you install VestaCP on your server, you're not done.
You also have postfix, VestaCP is using Exim, so you need to migrate to move everything into VestaCP.
If you have modified configs, there can be some conflicts.
Before you start take good backups because installing vesta gonna break your current setup. So if it went wrong you can go back.
You need to know that if you install VestaCP on your server, you're not done.
You also have postfix, VestaCP is using Exim, so you need to migrate to move everything into VestaCP.
If you have modified configs, there can be some conflicts.
Before you start take good backups because installing vesta gonna break your current setup. So if it went wrong you can go back.
Re: Switching to vesta from bare metal, few questions
Yup, I know all of that already, that's why I'm asking the questions I'm asking. I'm prepared for everything to break, and I'm tryign to know ahead of time all the things I will need to do to minimize downtime. But first I need some questions answered:
1) Can I specify the actual storage location of the mysql databases? (I know I need to re-import existing db's)
2) Can I re-use my existing letsencrypt cert?
3) When I create a web space, can I specify where the files are located?
4) When I specify the locations of the web pages, is that folder modified in any way or is it left alone?
Since I'm only using smtp (not pop3 or receivign any mail) I don't care if it's exim or postfix...I'll probably need to remove postfix manually right?
1) Can I specify the actual storage location of the mysql databases? (I know I need to re-import existing db's)
2) Can I re-use my existing letsencrypt cert?
3) When I create a web space, can I specify where the files are located?
4) When I specify the locations of the web pages, is that folder modified in any way or is it left alone?
Since I'm only using smtp (not pop3 or receivign any mail) I don't care if it's exim or postfix...I'll probably need to remove postfix manually right?
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Switching to vesta from bare metal, few questions
You are trying it way harder than it is.
Installing it on existing server is fatal... you will have more problems than you can solve.
Backup everything that you listed, sites + DB + certificates + any custom configs, wash and reinstall your server afresh and then install VestaCP. Then start restoring your sites one by one. However this ia a risky affair if you don't afford downtime.
The best approach would be to get a new server, fresh install and configure VestaCP. Test things and verify.
Then start moving your sites one by one (or chunks of 5 if many sites). This way you have the redundancy of sites working while you are migrating and do not risk crashing all your sites at once.
Installing it on existing server is fatal... you will have more problems than you can solve.
Backup everything that you listed, sites + DB + certificates + any custom configs, wash and reinstall your server afresh and then install VestaCP. Then start restoring your sites one by one. However this ia a risky affair if you don't afford downtime.
The best approach would be to get a new server, fresh install and configure VestaCP. Test things and verify.
Then start moving your sites one by one (or chunks of 5 if many sites). This way you have the redundancy of sites working while you are migrating and do not risk crashing all your sites at once.
Re: Switching to vesta from bare metal, few questions
I only have one site...I just wanted an easy way to manage it. I may add more later. Getting a new server would cost me a lot of money...60 bucks to be exact. That's not just something one does is it? I'd be better off just dealing with the downtime of reinstalling ubuntu.
Re: Switching to vesta from bare metal, few questions
Maybe someone can offer me a better solution for management that isn't VestaCP?
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Switching to vesta from bare metal, few questions
I have no idea, but I guess if it is a config you can do that. After the installation.1) Can I specify the actual storage location of the mysql databases? (I know I need to re-import existing db's)
In vestaCP you can add all certificates that you want. There is letsencrypt support in vestaCP. So you can enable letsencrypt with auto update.2) Can I re-use my existing letsencrypt cert?
The webspace in vestaCP is as follow: /home/[USERNAME]/web/[DOMAINNAME.COM]/public_html/ you can change config files but it is not recommended.3) When I create a web space, can I specify where the files are located?
Vesta do not change any of your files.4) When I specify the locations of the web pages, is that folder modified in any way or is it left alone?