Troubleshooting

Your own domain

A domain stuck on Waiting for DNS or Setting up, links that still say nemilab.com, and a domain that worked and then stopped.

On this page

Connecting a domain has three steps that can each stall: the two DNS records have to be visible to us, an HTTPS certificate has to be issued for the hostname, and a link has to be opened on it once. The status in the Domain tab tells you which of the three you are waiting on. Setting it up is described in Sending links from your own domain.

It stays on Waiting for DNS#

What is probably wrongHow to tellWhat to do
The TXT record is at the wrong nameYour DNS panel shows something like _nemi-challenge.share.yourcompany.com.yourcompany.com.Many panels add your domain to whatever you type. Enter only the part before your domain, or use the full name if the panel does not append.
The value was pasted with something extraQuotation marks or a trailing space around the value.Use the copy button in the Domain tab and paste it as the whole value.
The CNAME points somewhere elseThe message names what it found instead.Set the CNAME target to exactly what the Domain tab shows.
It was only just savedEverything looks right.Wait and press Check DNS again. Records usually appear within minutes and can take up to an hour.

It stays on Setting up#

Your records are right and your links already use the domain; what has not finished is the HTTPS certificate. The usual cause is a proxy or CDN in front of that subdomain: the record has to be set to DNS only, because a proxied record stops the certificate from being issued. If your provider has a proxy toggle, switch it off for this record and press Check again. Opening one of your links yourself also finishes it.

Links keep the address they were created with, so anything made before you connected the domain stays on nemilab.com and keeps working. Create a new link and it will use your domain. If a new one still does not, check two things: the Domain tab has to be past Waiting for DNS, and you have to be sharing from the workspace the domain belongs to, because a link made from another workspace uses the Nemi domain.

It worked and then stopped#

The Domain tab shows the reason under the status. Nemi re-checks every connected domain daily, and there are two usual causes: the DNS records were changed or removed, or the workspace owner's plan no longer includes custom domains. In both cases every link keeps working on nemilab.com, so nothing your recipients hold is broken while you fix it.

Can I use my bare domain, without a subdomain?

No. The record this needs cannot exist on a bare domain, and pointing your bare domain here would take your website down. Use something like share.yourcompany.com.

Can two workspaces use the same domain?

No. A hostname belongs to one workspace, so connecting one that is already in use is refused.

I do not see the Domain tab.

Only the workspace owner sees it, it is part of Creator and up, and it may not have been switched on for your account yet.

What happens if I disconnect it?

Every link goes back to nemilab.com immediately and keeps working. Nothing you have sent breaks.

Related

Still stuck? Email support@nemilab.com and tell us what you were trying to do.