Change domain name or add alias for already registered site

[w14w16]

Hi, there's a way to change the domain name or add aliases of a site without deleting the whole site?
Thanks

[0rangebananaspy]

yes, we need in some cases to edit domain name without delete the site already created. we hope in the next release we can see this feature, a big boom! Now for change domain name, I must delete and recreate the site again.

[7heMech]

You could use this to clone the site easily: https://github.com/7heMech/clp-stager

[github-oneyue]

Adding the corresponding domain name or sub domain name in the vhost file can be achieved. If you are unsure, you can send the text to chatgpt for modification

[s-a-s-k-i-a]

The honest answer is that CloudPanel doesn't have a first-class "rename domain" operation — the clpctl command list confirms it: you've got site:add:*, site:install:certificate, site:delete, and that's the site lifecycle. So this is feature-gap territory and you have to choose between two paths depending on what you actually need.

Aliasing (adding additional domains to an existing site) — supported in the Frontend Area:

1. Open the site in CloudPanel UI
2. Settings → Domains → add the additional domain
3. Issue a Let's Encrypt cert that covers all configured domains (UI does this in one step)

That's it for the alias use case. The site keeps the original site user, docroot, and DB — extra hostnames just route to the same nginx vhost.

Real rename (the primary domain changes) — no UI flow, but a workable sequence:

1. Issue the new cert first (UI: SSL/TLS → install for new domain, or clpctl lets-encrypt:install:certificate)
2. Edit the vhost — for stock CloudPanel installs it lives in /etc/nginx/sites-enabled/<old-domain>.conf; replace server_name and the cert paths. Don't edit by hand if you can avoid it; better, use a custom vhost template (Admin Area → Vhost Templates) so you can re-render with the new domain. clpctl vhost-templates:list / vhost-template:view confirms which template the site uses.
3. For WordPress sites specifically: update siteurl / home and run a search-replace for the serialised values in post content/meta. WP-CLI is the safest path here:

   sudo -u <site-user> -i -- wp search-replace 'https://old.example' 'https://new.example' --all-tables --skip-columns=guid

   The site user (the one CloudPanel created for this site) is required — don't run as root, and don't run as clp.
4. Reload nginx: systemctl reload nginx.
5. If the docroot path itself is keyed to the old domain (it isn't by default — CloudPanel docroots are under /home/<site-user>/htdocs/<domain>/ — so this matters), you may also need to move the directory and update root in the vhost. Most templates use a variable that resolves correctly on its own; check before moving anything.

The fully-clean way is still delete + re-add if you can afford the downtime — that's the only path that touches every CloudPanel-managed file consistently. The vhost-edit path above works but you're effectively maintaining the site outside of what CloudPanel knows about, so the next time you clpctl site:install:certificate or change a setting in the UI, the system may overwrite parts of your edits unless you've moved to a custom vhost template.

(Editing the vhost on a ChatGPT-suggestion as the only step misses the cert, the DB rewrites, and the template-overwrite trap — that's why it tends to leave sites half-working.)

[7heMech]

Or you could use my script... https://github.com/7heMech/clp-stager

[7heMech]

You could use this script to recreate the site at another domain: https://github.com/7heMech/clp-stager