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
Change VestaCP server/domain name for control panel
Change VestaCP server/domain name for control panel
I installed VestaCP, created several users/domains that are up and running. However, I now need to change the host and domain name of the VestaCP server itself. What is the best way to do that? I thought I could just use an alias for the new name, but it appears I can't manage SSL certificates for an alias.
Suggestions?
Suggestions?
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Change VestaCP server/domain name for control panel
If you had given your fingers some trouble, you could have got the answer by now
https://www.google.com/search?q=vestaCP+change+hostname
https://www.google.com/search?q=vestaCP+change+hostname
Re: Change VestaCP server/domain name for control panel
Believe me, I read at least 5 or 6 search results before poating a question. but i did not find a good solution. I will look again.
Re: Change VestaCP server/domain name for control panel
Doesn't look related to my need.floown wrote:Here a solution : viewtopic.php?f=10&t=14534
Re: Change VestaCP server/domain name for control panel
Here is my challenge... I created a server with a hostname and domain name that was temporary. Now that everything is up and running I'd like to assign a new domain name to the server itself (for the VestaCP URL, mail server, etc.)
However, the server/host name for web access to VestaCP itself can't seem to be changed. I've seen other posts about changing server hostname, but not a solution how I can change the domain name for my server's VestaCP pages. Also, the domain name for email for SMTP, POP3, IMAP, Roundcube are based on that original (temporary) server domain.
I'd hate to have to reinstall to change the host / domain for my VestaCP-based server.
However, the server/host name for web access to VestaCP itself can't seem to be changed. I've seen other posts about changing server hostname, but not a solution how I can change the domain name for my server's VestaCP pages. Also, the domain name for email for SMTP, POP3, IMAP, Roundcube are based on that original (temporary) server domain.
I'd hate to have to reinstall to change the host / domain for my VestaCP-based server.
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Change VestaCP server/domain name for control panel
you are really not trying to understand it simply... Just change your hostname from Vesta Web UI or commandline
You can also do it from SSH in Debian's preferred way
After that make sure their is an A record pointing for the new hostname to the IP
Code: Select all
v-change-sys-hostname
Code: Select all
hostnamectl set-hostname <name or FQDN to set>
After that make sure their is an A record pointing for the new hostname to the IP
Re: Change VestaCP server/domain name for control panel
I'll try that again, but I don't believe that changed the virtual hostname for VestaCP on the server. I'll report back!
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Change VestaCP server/domain name for control panel
you don't have to believe anything... just do in your ssh
if it shows the changed one, you are done.
Code: Select all
hostname
Re: Change VestaCP server/domain name for control panel
Yes, the Linux server hostname changes, I'm trying to make sure that VestaCP operates under the new fqdn, and it does NOT.mehargags wrote:you don't have to believe anything... just do in your sshif it shows the changed one, you are done.Code: Select all
hostname
VestaCP still shows the old fqdn as the admin domain, and the LetsEncrypt certificate is still for the old domain. also the email certificate is still for the old domain.
So as it stands, there isn't apparently a way to migrate the VestaCP server to a new fqdn.