Guides

Deployment

Custom Domains & SSL

Attach your own domain to any Nexon project. Certificates are provisioned and renewed automatically — no manual configuration required.

schedule

min to read

Updated

Mar 2026

checklist

Prerequisites

Before you begin, make sure you have the following:

A Vertex project deployed to production
A domain registered with any DNS provider
Access to your domain's DNS management panel

info

Overview

By default, every Vertex project is assigned a subdomain under vertex.app. You can replace this with any domain you own by adding it to your project and updating your DNS records.

Nexon handles TLS certificate provisioning automatically — certificates are issued within minutes of DNS propagation and renewed before expiry without any action on your part. You can attach multiple domains to a single project.

‍

How it works

The process has four stages: register the domain in your project, update DNS records to point to Nexon infrastructure, wait for propagation, then the platform issues the certificate automatically.

Certificates are issued and renewed automatically with zero downtime
HTTPS is enforced — all HTTP traffic is redirected
Wildcard domains are supported on Pro and Enterprise plans
All attached domains serve identical content unless routing rules override this

format_list_numbered

Instruction

Step 1 — Add the domain

Open your project settings in the dashboard and navigate to the Domains tab. Enter your domain and click Add Domain. You can also use the CLI:

# Add a custom domain
vertex domains add yourdomain.com

# Add a subdomain
vertex domains add app.yourdomain.com

# List all attached domains
vertex domains list

Note: You can attach up to 50 custom domains per project. Wildcard domains like *.yourdomain.com require Pro or Enterprise plan.

‍

Step 2 — Configure DNS records

Once the domain is added, Nexon shows the DNS records to create. Go to your DNS provider and add the following:

Apex domains: Root domains must use A / AAAA records. CNAME records cannot be used at the apex per DNS specifications.

‍

Check propagation status

DNS changes can take a few minutes to 48 hours to propagate globally. Monitor via CLI:

vertex domains status yourdomain.comvertex domains status yourdomain.com --watch

‍

Step 3 — SSL certificate

As soon as DNS resolves correctly, a TLS certificate is provisioned automatically — typically under 2 minutes after propagation.

Certificates cover both root domain and www subdomain by default
Valid for 90 days — renewed automatically 30 days before expiry
HSTS headers set with 1-year max-age

vertex domains cert yourdomain.com

‍

Step 4 — Set a primary domain

If multiple domains are attached, designate one as primary. All others redirect to it unless overridden by routing rules.

vertex domains set-primary yourdomain.com

All set. Your project is now live at your custom domain with a valid SSL certificate. All future deployments are served here automatically.

build

Troubleshooting

DNS records not resolving

If your domain shows DNS pending status after 30 minutes, check the following:

Confirm the records are saved correctly in your DNS provider's control panel
Check for conflicting A or CNAME records on the same hostname
Flush your local DNS cache — ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (macOS)
Use a public DNS propagation checker to verify records are globally visible

‍

Certificate not issuing

Certificate issuance requires DNS to resolve correctly to Vertex infrastructure. If the certificate stays in Pending after DNS propagates, remove and re-add the domain from the dashboard to trigger a new attempt.

If the issue persists, contact support with the output of:

vertex domains status yourdomain.com --verbose

arrow_back

Setting Up Log Drains

arrow_forward

Your Cart