Provisioning Subdomains

Every site or app hosted on Inklura is served over HTTPS on its own hostname: a *.inklura.fr subdomain, or a domain you own. The platform handles DNS for Inklura subdomains, certificates, and routing; there is no server for you to configure.

*.inklura.fr subdomains

When you create your Inklura account, the setup wizard asks for your space's subdomain, for example my-shop.inklura.fr, and checks its availability as you type. The name must follow these rules:

  • 3 to 63 characters;
  • lowercase letters, digits and hyphens only, with no hyphen at the start or end;
  • not already used by another space, and not reserved by the platform (admin, api, app, auth, billing, manage, onboarding, staging, status, support, www).

If the name is taken, the wizard suggests a few variants to check. The platform then:

  • publishes the site on that hostname, with no DNS change on your side (every *.inklura.fr subdomain already points to the platform);
  • serves it over HTTPS with a certificate it manages for you.

In the console's Domains page (Settings > Domains), the *.inklura.fr subdomain carries the "Assigned" badge: it is managed by the platform and cannot be removed there.

An Inklura subdomain is also covered by the platform's framing policy, see Iframe Embedding.

Your own domain

To serve a site on your own domain (for example www.example.com), open the console's Domains page:

  1. Add the domain. It is attached to your space's current site (each row in the list shows its site) and stays inactive until DNS, the HTTPS certificate and routing are validated. inklura.fr names cannot be added: they are managed automatically.
  2. At your domain registrar, create a CNAME record pointing to the DNS target shown on the page (a button copies it), or an A record pointing to that target's IP address. A root domain such as example.com usually cannot carry a CNAME: use the A record there.
  3. Click Verify DNS. The check succeeds when the CNAME points to the target, or when the domain's IPv4 address is the target's. The certificate and routing are then prepared, and the domain goes live.

While it is being prepared, the page refreshes on its own and shows the domain's state:

State Meaning
DNS to verify The domain is added, the DNS check has not succeeded yet
Queued DNS verified, preparation is about to start
HTTPS being prepared The certificate and routing are being set up
Ready / Active The domain serves your site
To retry A step failed; the Retry button restarts preparation
Action required The failure will not clear on its own; the step and the error message are shown under the domain
Removing The domain is being removed

The site's *.inklura.fr subdomain stays available. To detach a custom domain, use Remove on the same page (the button is unavailable while preparation is in progress).

A domain can only be attached to one site: if it already is elsewhere, adding it is refused with an error saying the domain is already attached to another space.

Note

DNS propagation can take from a few minutes to a few hours depending on your domain registrar. The check only succeeds, and the certificate can only be issued, once it has completed.

In your app

The domain is set in the console, not in code. A few things to respect in your app:

  • Callback URLs. URLs the platform calls (queue handlers, scheduler routes) must be on an address allowed for your app. Adding a domain in the console does not change that list: keep the address your handlers are already registered with.
  • Cookies. Each hostname has its own cookies. A session opened on my-shop.inklura.fr is not visible from www.example.com; see Single Sign-On.
  • Internal links. Prefer relative paths (/cart) over absolute URLs, so the site works on all of its hostnames.

See also