Connecting a website to veilx essentially means routing visitor requests to veilx's edge nodes first, so each node can decide whether to serve a cached response directly or fetch from your server. The whole process requires no changes to your site's code — you simply register the domain and origin in the console, then point the domain's DNS to veilx. Let's walk through it in order.
Before you begin
Before you start, make sure you have the following in place. This helps you onboard successfully on the first try and avoids back-and-forth troubleshooting.
- A registered, verified veilx account whose plan still has available site slots.
- A domain you control DNS for, such as
www.example.com. - The public IP or origin domain of your origin server, along with the port it serves on (usually 80 / 443).
- If your origin already has HTTPS configured, make sure the certificate is valid; if not, veilx can issue a free certificate after you connect.
Step 1 · Add a site
Log in to the console, go to the "Sites" page, and click "Add site". In the form, enter the domain you want to accelerate and choose the protocol type — if you want visitors to always use HTTPS, you can also enable "Force HTTPS redirect".
After you submit, veilx assigns a dedicated CNAME endpoint to the site (something like example.veilx-cdn.com). This address is the key piece of information you'll need when updating your DNS records later, so make a note of it now.
Step 2 · Configure the origin
The origin is where veilx fetches data from when there's a cache miss. In the "Origin configuration" section of the site detail page, enter the origin address — it can be either an IP or a domain — and specify the origin-fetch port and protocol.
- If your origin serves on a domain, we recommend also setting an "Origin Host" so the origin matches the expected domain's virtual host.
- If you have multiple origin servers, you can add them as primary/backup or load-balanced, and veilx will switch over automatically when the primary origin fails.
- Set the origin-fetch protocol to match what your origin actually listens on, to avoid 301 redirect loops.
Step 3 · Update DNS records
This is the step that actually routes traffic into veilx. Go to your DNS provider's console and change the DNS record for the domain you want to accelerate so it points to the CNAME address from Step 1.
- For a subdomain (such as
www), add or update aCNAMErecord and set its value to the endpoint veilx assigned. - Before making the change, we recommend lowering the record's TTL (for example, to 600 seconds) so the switch takes effect faster and rolling back is more flexible.
- Root domains (apex domains) usually don't support CNAME — use your provider's CNAME flattening / alias record, or follow the docs to connect via an A record instead.
DNS changes take some time to propagate globally, usually anywhere from a few minutes to an hour, depending on the original TTL setting.
Verify the site is live
Once the DNS change has propagated, you can confirm from a few angles that the site's traffic is now served by veilx.
- Query the domain with
digor an online tool to confirm it now resolves to veilx's endpoint. - Visit the site and check the response headers — a veilx cache-hit header (such as
X-Cache) means the request went through an edge node. - Return to the site monitoring page in the console and watch whether metrics like request count, hit rate and origin-fetch latency begin to show data.
When monitoring shows real traffic and the hit rate climbs steadily as visits accumulate, your first site has been successfully connected to veilx. Next, you can fine-tune the cache rules to get acceleration to its best.