When the connection fails

In most cases, once you fix the problem, the verification screen checks again on its own and continues. If an error stays, find the same message below.

 

A different value is in place

Cause: The record value you entered at your domain provider differs from the value on the screen.

Fix: Copy the value from the previous screen again and compare it with the value at your provider. Check for a trailing dot (.), leading or trailing spaces, and the domain entered twice in the name field (www.example.com.example.com). Once fixed, it moves on automatically.

 

Verification never finishes on Cloudflare

Cause: The proxy (orange cloud) is on for the records you added. Verification stalls without any error message.

Fix: In your Cloudflare DNS settings, turn off the proxy on the Weekerp records so they show a gray cloud (DNS only).

 

This domain is attached to another CloudFront distribution

Cause: This domain is registered as an alternate domain on another CloudFront distribution you used before.

Fix: Remove it from Alternate domain names in that CloudFront distribution's settings. Once removed, it continues within 1 minute.

 

The validation record wasn't found within 72 hours

Cause: The certificate line wasn't added within 72 hours, or its value was different, so the validation period expired.

Fix: Click Check again to get a new validation line. Delete the old line and add the new one.

 

Certificate issuance was blocked by your domain's CAA record

Cause: Your domain's CAA record doesn't allow Weekerp's certificate authority (Amazon).

Fix: Delete the CAA record or add the line 0 issue "amazon.com", then click Check again.

 

You hit the certificate rate limit

Cause: Too many certificates were requested in a short time.

Fix: Try again in a moment and it clears.

 

We could not reach your origin server

Cause: Weekerp can't fetch your site from your origin server. For the first 10 minutes after connecting, this shows as waiting.

Fix: Check that your origin server is running and that your site opens at its current address. Also check that your server firewall isn't blocking outside requests.

 

The nameserver change isn't confirmed

Cause: The nameserver change is taking time to take effect, or you changed only some of the 4.

Fix: At your registrar, check that all 4 Weekerp nameservers are entered and the old nameservers are deleted. It can take up to one day to take effect. Checking continues even if you close the screen.

 

The root address can't be connected to Weekerp

Cause: Your domain provider doesn't support ALIAS records on the root (@) (Gabia, Cafe24, Whois, etc.).

Fix: Connect your primary address with www, or switch to the nameserver method. Connect a domain with records (CNAME)

 

This address is already connected to Weekerp

Cause: The same address is connected to another workspace.

Fix: Contact support.

 

Something went wrong while checking

Fix: Click Check again. If it keeps appearing, contact support. The support link on the connection screen opens in a new tab, so the screen you are working on stays as it is.