Deployment & Sharing
Custom Domains
By default, deployed Webase apps get a Netlify URL like my-app-abc123.netlify.app. With custom domains, you can use your own URL instead — like www.myapp.com — giving your app a professional, branded web address.
Prerequisites: Before setting up a custom domain, you need two things: (1) your app must be deployed to Netlify through Webase, and (2) you must own a domain name purchased from a domain registrar like Namecheap, Google Domains, GoDaddy, or Cloudflare.
What Custom Domains Do
A custom domain replaces the auto-generated Netlify URL with your own domain name. Visitors type your domain into their browser and see your Webase app. SSL certificates are provisioned automatically, so your site works securely over HTTPS with no extra configuration.
Setting Up a Custom Domain
Deploy Your App to Netlify
If you haven't already, deploy your app to Netlify from the Application Editor. Click the Deploy button in the toolbar. Once deployed, your app will have a Netlify URL. You need this before adding a custom domain.
Add Your Custom Domain
In the Application Editor, navigate to your app's domain settings. Enter the domain you want to use (e.g., www.myapp.com or myapp.com). Webase will register the domain with Netlify and provide you with DNS configuration instructions.
Configure Your DNS
Log in to your domain registrar (the service where you bought your domain) and add a CNAME record that points your domain to your Netlify site. The settings are:
- Type: CNAME
- Name:
www(or@for the root domain) - Value: Your Netlify site URL (e.g.,
my-app-abc123.netlify.app) - TTL: 3600 (or "Auto")
Root domains: If you want to use a root domain like myapp.com (without www), some registrars require an A record or ALIAS record instead of a CNAME. Check your registrar's documentation for details.
Wait for DNS Propagation
After saving your DNS changes, it can take anywhere from a few minutes to 48 hours for the changes to propagate across the internet. Most changes take effect within 1-2 hours. Webase checks the DNS status automatically and updates you when your domain is verified.
SSL Certificate Provisioning
Once DNS is verified, Netlify automatically provisions a free SSL certificate for your domain. This happens within minutes and requires no action from you. After the certificate is active, your site is fully accessible over HTTPS.
Domain Status Tracking
Your domain goes through several stages during setup. You can track the current status in your app's settings:
- Unconfigured — Domain has been added but DNS changes haven't been made yet.
- Pending DNS — Waiting for your DNS changes to propagate and be verified.
- Provisioning SSL — DNS is verified and the SSL certificate is being issued.
- Active — Everything is set up. Your domain is live and serving your app over HTTPS.
Troubleshooting Common Issues
- Domain stuck on "Pending DNS" — Double-check that your CNAME record is correct in your registrar's DNS settings. Make sure there are no typos in the Netlify URL. If it's been more than 48 hours, try removing and re-adding the DNS record.
- "DNS record not found" error — Your DNS changes may not have propagated yet. Wait a few hours and check again. You can use a tool like
digor an online DNS checker to verify your records. - SSL certificate not provisioning — This usually resolves on its own within a few minutes after DNS verification. If it persists, ensure no conflicting DNS records (like an existing A record) are interfering.
- "Domain already in use" error — The domain may be configured on another Netlify site. Remove it from the other site first, or contact support for help.
Tip: We recommend using www.yourdomain.com as your primary domain, as CNAME records are simpler to configure than root domain setups. You can then set up a redirect from the root domain to the www version.
Next Steps
- Deploying to Netlify — Learn how to deploy your app before adding a custom domain.
- Website Generation — Generate a professional website to host on your domain.