Custom domain
Serve your Neleto site from your own domain, with an automatic SSL certificate.
Every Neleto site is reachable at a neleto.app subdomain out of the box
(for example your-name.neleto.app). On a paid plan you can serve your
site from your own domain instead, with an SSL certificate issued automatically.
neleto.app subdomain. See pricing for the plan that fits.Connect your domain
- Open the Neleto Console and go to your instance.
- In the Domain & certificate section, click Use your own domain.
- Enter the domain you own (for example
example.com) and confirm. The Console validates the domain and then shows you the exact DNS record to create.
Point your DNS at Neleto
Create a single A record for your domain, pointing at the server IP address shown in the Console:
| Type | Name | Value |
|---|---|---|
A | example.com | the IP address shown in the Console |
That is the only record you need, there is no CNAME, AAAA or TXT verification record to add. Create it at your domain registrar or DNS provider and then give it time to propagate (this can take anywhere from a few minutes to a few hours, depending on your provider).
SSL certificate
Once your DNS points at the server, Neleto requests a free SSL certificate for your domain automatically. This can take up to a few hours after your DNS has propagated, and you don't need to do anything.
If you'd rather not wait, open the instance in the Console and click Retry certificate to request it immediately. Only do this once your domain's DNS already points at the server shown above, otherwise the request will fail.
Troubleshooting
| Message | What it means |
|---|---|
| "… is already connected to another site" | The domain is already in use by another Neleto instance. |
| "That domain belongs to Neleto and can't be used" | You entered a Neleto-owned domain (neleto.io or neleto.app). Use a domain you own. |
| "That's not a valid domain" | Check the format, enter the bare domain like example.com, without https:// or a path. |
| Site not loading or certificate warning | DNS probably hasn't propagated yet, or the A record is wrong. Confirm the A record points at the IP shown in the Console, then use Retry certificate. |