"failed to create acme order" when configuring custom domain to a canister

I am trying to host a canister under a custom domain, Everything was ready, but it reported such a error:

curl -sLv -X GET \
    https://icp0.io/registrations/da0beb0015d850703b3f3afefa402c85adeaf82b2ead707eb63eb625a68185f9
{"name":"panda.fans","canister":"c63a7-6yaaa-aaaap-ab3gq-cai","state":{"Failed":"failed to create acme order"}}

Hello @zensh

It is an issue on our end. We have identified the problem and will let you know once the service is operational again. Sorry for the inconvenience!

1 Like

Hello @zensh,

I just wanted to confirm that the issue is resolved and it is operational again. Your registration already went through and your domain is available :slight_smile:

1 Like

Thank you every much

Hello @rbirkner

I’m also facing the same issue

Hey @ahdrahees

This is an internal error, which is being retried. In the meantime, your registration went through:

$ curl -sL -X GET \
  https://icp0.io/registrations/90004879ce043bb260a6762045137e8543f7ef573c3ff75063ea3e188dda862c
{"name":"cipherbox.at0.app","canister":"pidie-caaaa-aaaag-acn6q-cai","state":"Available"}%
1 Like

I’m getting ā€œfailed to create acme orderā€ on canister id 4gcg2-6yaaa-aaaah-qp4pq-cai

https://icp0.io/registrations/188ba32e9a244a90d497253b9747e7e4a201b531b7ca224dd91003a7dc56ddbd

I’m now getting state: available but its not loading in the browser.

curl -sL -X GET \
    https://icp0.io/registrations/188ba32e9a244a90d497253b9747e7e4a201b531b7ca224dd91003a7dc56ddbd
{"name":"www.canister.co","canister":"4gcg2-6yaaa-aaaah-qp4pq-cai","state":"Available"}%

dns records are verified

dig TXT _canister-id.www.canister.co +short
dig CNAME _acme-challenge.www.canister.co +short

"4gcg2-6yaaa-aaaah-qp4pq-cai"
_acme-challenge.www.canister.co.icp2.io.

Have cleared the browser cache. It’s just https://www.canister.co thats not working, https://canister.co is fine

Hey @jakepeg,

you are missing a DNS entry:

www.canister.co CNAME www.canister.co.icp1.io

See here:

$ dig www.canister.co +short
<NO OUTPUT>

You can see that the HTTP gateways correctly serve the domain, if you force the DNS resolution:

curl -sLv -X GET \
    --resolve www.canister.co:443:147.28.197.114 \
    https://www.canister.co
1 Like

doh! thanks @rbirkner

1 Like

Hey @rbirkner
I’m facing the same issue ā€œfailed to create acme orderā€ when trying to register my domain.

https://icp0.io/registrations/4221cc19fe689cb9770af67c25c5badd93ef34a1c3f3814a3054dbb5f2d274a0

seb@MacBook-Pro-de-Seb web % dig A openinternetcamp.fun +short && dig CNAME _acme-challenge.openinternetcamp.fun +short && dig TXT _canister-id.openinternetcamp.fun +short
145.40.67.238
145.40.67.162
147.75.202.74
63.251.162.12
_acme-challenge.openinternetcamp.fun.icp2.io.
"w3hgi-dqaaa-aaaan-qzzcq-cai"

I’ve set up my DNS records on Namecheap following the documentation (using ALIAS for apex domain as instructed): DNS configuration guide | Internet Computer

Any idea?

Edit: I’ve succeeded with the www. subdomain but still not with the main one
Edit 2: I’ve deleted the original request and tried again with a new request id (https://icp0.io/registrations/d5e5a78d260db6d9c845c3975f2d895e886abce8921e8b47bc7faef65d529173) and this time the error is ā€œfailed to mark acme order as readyā€"
Edit 3: Now both the root domain and www. are working and redirect to my canister — even though I only successfully registered the www. version. I’ve got no clue but at least it works. :face_with_raised_eyebrow:

Hey @Seb

Sorry for the late reply: from our point of view, both the root and www. have been successfully registered. I see both of them. Also, the HTTP gateways do not understand that one is a subdomain of another. They just treat them as different names.

The user experience of the custom domain feature is not that great. For example, the errors that you observed are rather internal errors, which are being retried and usually disappear. So, when you saw ā€œfailed to mark acme order as readyā€, it didn’t mean that this registration failed. It just meant that we had an issue with one step and will retry it soon. That’s also what happened and your registration succeeded in the meantime. Ideally, we would not expose such errors as they are not actionable for the user and rather confusing.

We have conducted a survey here and will get to improving it towards the summer.

2 Likes

I’m encountering a similar but slightly different issue when trying to configure a custom domain for my canister. Thanks for the existing thread, it’s been helpful to read through.

My domain is doxadao.org and the canister ID is 5snzc-piaaa-aaaak-apb6q-cai.

When I check the registration status using:

curl -sL -X GET https://icp0.io/registrations/<YOUR_REGISTRATION_ID>

I get the following error:

{ā€œnameā€:ā€œdoxadao.orgā€,ā€œcanisterā€:ā€œ5snzc-piaaa-aaaak-apb6q-caiā€,ā€œstateā€:{ā€œFailedā€:ā€œfailed to mark acme order as readyā€}}

Previously, I was seeing ā€œfailed to create acme orderā€, but now it has changed to ā€œfailed to mark acme order as readyā€.

Does anyone have insights into what might cause the ā€œfailed to mark acme order as readyā€ error, and how it might differ in resolution from the ā€œfailed to create acme orderā€ issue? Any suggestions on what to check or try next would be greatly appreciated.

Thanks!

Hey @Vishnu

This is an internal error, which is being retried by the service. Usually, this is resolved after a retry. This is also the case for your domain, which is now available: https://doxadao.org/

1 Like