You don't need this. Every website already lives at your Weesify address, like weesify.com/noor-studio/, with HTTPS and nothing to set up. Websites there run locked down, so a website's code can never reach your members' accounts; the only limit is that the website's own scripts can't keep cookies or browser storage.
A separate hosting domain is an advanced option that lifts that limit: each website is then also reachable at a name of its own, like noor-studio.wees.site, where its scripts can use cookies and storage. Set it up only if websites you host need that.
Before you start
- Register a short domain that is not part of your Weesify domain. For example, if Weesify runs on weesify.com, use something like wees.site. Weesify refuses a hosting domain inside its own domain.
- You need access to WHM/cPanel for the server Weesify runs on.
Steps
- DNS. Where the domain's DNS is managed (WHM › DNS Zone Editor, or your registrar), add two A records pointing at your server's IP address: one for @ (the domain itself) and one for * (every name under it).
- Add the domain in cPanel. Open cPanel › Domains › Create A New Domain. Enter the domain (wees.site) and keep Share document root ticked so it uses the same folder as Weesify. Save.
- Add the wildcard. Still in Domains, create *.wees.site the same way, sharing the same document root.
- Certificates. Open cPanel › SSL/TLS Status, tick wees.site and *.wees.site and choose Run AutoSSL. A certificate for every name under the domain needs the domain's DNS hosted on this server; if your DNS is elsewhere, move the nameservers to the server or ask your host to issue a wildcard certificate.
- Tell Weesify. Open Console › HTML Websites, open Advanced: separate hosting domain, enter the domain and choose Save.
- Check it. Choose Check setup. All four checks should be green: wildcard DNS, the domain itself, HTTPS certificate, and served by Weesify. The check runs again every day and shows here.
If a check is red
| Check | What it means | Fix |
|---|---|---|
| Wildcard DNS | A random name under the domain doesn't reach this server | Add or correct the * A record; wait for DNS to update (up to a few hours) |
| The domain itself | The bare domain doesn't resolve | Add the @ A record |
| HTTPS certificate | No valid certificate answers for subdomains | Run AutoSSL again for the wildcard; check DNS is hosted on the server |
| Served by Weesify | Another site answers | The domain's document root must be Weesify's folder |