Addon Domains
The Additional Domains (also called Addon Domains) page lets you host extra domains on the same account—each with its own website folder. Use this when you own another domain and want a separate site without buying a new hosting account.
Who can use this
The signed-in account owner. Resellers/admins can open it for your account, but changes affect only your sites.
Before you start
Make sure the domain is registered and points to this server (nameservers or an A record to your server IP). Decide the folder where the site’s files will live.
What you see on this page
• A usage bar showing how many additional domains you use vs. your plan limit (button disabled if you hit the limit).
• A table listing each domain with its IP, Document root, and an Edit button (three-bar icon).
• A green + button to add a new domain.
Create an additional domain (step-by-step)
1) Click the green + to open Add a new additional domain.
2) In Domain name, type your domain (e.g., example.com
). No http://
or slashes.
3) In Document root, enter only the folder path after /home/<user>/
. Examples:
• public_html/example.com
• domains/example.com
4) Click Add Domain. The list refreshes and your domain appears.
Where to upload files
Put the site files in the chosen document root (for example /home/<user>/domains/example.com
). Add an index.php
or index.html
so the site loads.
Open your new site
In the table, click the link icon next to the domain to open it in a new tab. If you see a placeholder or 404, upload your site files to the document root you picked.
Edit an additional domain
1) Click the Edit button (three-bar icon).
2) Update the Domain or Document root if needed.
3) Click Save Changes. The list refreshes.
Delete an additional domain
In the edit window, click Delete Domain. This removes the web mapping. It does not delete your files—clean the folder in File Manager if you no longer need them.
DNS note (if your DNS is external)
If your domain uses external DNS (registrar/Cloudflare), create an A record to your server IP (e.g., example.com → your.server.ip
and often www → your.server.ip
). DNS changes can take up to a few hours to propagate.
SSL / HTTPS
After the domain resolves here, issue/renew SSL from SSL Manager. AutoSSL can only work once DNS points to this server. If the padlock is missing, check DNS first.
Field rules & tips
• Domain: no protocol (no http://
), no path, just the domain (and TLD).
• Document root: enter a path under /home/<user>/
; don’t start with a slash—it's added for you.
• Keep each site in its own folder (e.g., domains/example.com
) for clean backups and troubleshooting.
Common issues & fixes
• Domain opens the wrong site: check the document root path; make sure files are in that folder.
• Site doesn’t load: upload an index file; verify DNS points to this server; wait for DNS propagation.
• Can’t add (button disabled): you’ve reached your plan’s domain limit.
• No padlock (HTTPS): run AutoSSL in SSL Manager after DNS is correct.
Next steps
Install your app/CMS to the document root. Create mailboxes for this domain in Email Accounts (choose the domain). Adjust PHP settings in PHP Manager if needed.