# Issue Registering Domain \> 500 Error @ https://icp0.io/registrations

**URL:** <https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010>\
**Category:** Developers\
**Created:** [March 19, 2023, 5:01pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010 "2023-03-19T17:01:40Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hazel](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hazel](https://forum.dfinity.org/u/Hazel)\
**Post date:** [March 19, 2023, 5:01pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/1 "2023-03-19T17:01:40Z")

</div>

```auto
(base) hazel@Hazels-MBP-2 src % curl -sLv -X POST \
    -H 'Content-Type: application/json' \
    https://icp0.io/registrations \
    --data @- <<EOF
{
    "name": "app.unid.ooo"
}
EOF
* Trying 139.178.83.182:443...
* Connected to icp0.io (139.178.83.182) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* CAfile: /Users/hazel/opt/anaconda3/ssl/cacert.pem
* CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
* subject: CN=boundary.dfinity.network
* start date: Feb 16 19:26:59 2023 GMT
* expire date: May 17 19:26:58 2023 GMT
* subjectAltName: host "icp0.io" matched cert's "icp0.io"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* h2h3 [:method: POST]
* h2h3 [:path: /registrations]
* h2h3 [:scheme: https]
* h2h3 [:authority: icp0.io]
* h2h3 [user-agent: curl/7.84.0]
* h2h3 [accept: */*]
* h2h3 [content-type: application/json]
* h2h3 [content-length: 28]
* Using Stream ID: 1 (easy handle 0x7fcc5800da00)
> POST /registrations HTTP/2
> Host: icp0.io
> user-agent: curl/7.84.0
> accept: */*
> content-type: application/json
> content-length: 28
> 
* We are completely uploaded and fine
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 500 
< server: nginx/1.21.3
< date: Sun, 19 Mar 2023 16:50:35 GMT
< content-length: 16
< access-control-allow-origin: *
< access-control-allow-methods: HEAD, POST
< access-control-allow-credentials: true
< access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-None-Match,If-Modified-Since,Cache-Control,Content-Type,Range,Cookie
< access-control-expose-headers: Accept-Ranges,Content-Length,Content-Range
< access-control-max-age: 600
< 
* TLSv1.3 (IN), TLS alert, close notify (256):
* Closing connection 0
* TLSv1.3 (OUT), TLS alert, close notify (256):
unexpected error                                                                                                                                                                                   

```

```auto
(base) hazel@Hazels-MBP-2 src % dig TXT _canister-id.app.unid.ooo 

; <<>> DiG 9.10.6 <<>> TXT _canister-id.app.unid.ooo
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19452
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_canister-id.app.unid.ooo.	IN	TXT

;; ANSWER SECTION:
_canister-id.app.unid.ooo. 60	IN	TXT	"2ddhz-5aaaa-aaaam-abf4a-cai"

;; Query time: 84 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Mar 19 13:02:59 EDT 2023
;; MSG SIZE rcvd: 94

```

```auto
(base) hazel@Hazels-MBP-2 src % dig TXT _acme-challenge.app.unid.ooo

; <<>> DiG 9.10.6 <<>> TXT _acme-challenge.app.unid.ooo
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52651
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;_acme-challenge.app.unid.ooo.	IN	TXT

;; ANSWER SECTION:
_acme-challenge.app.unid.ooo. 60 IN	CNAME	_acme-challenge.app.unid.ooo.icp2.io.

;; AUTHORITY SECTION:
icp2.io. 1060	IN	SOA	clay.ns.cloudflare.com. dns.cloudflare.com. 2304582871 10000 2400 604800 3600

;; Query time: 65 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Mar 19 13:03:40 EDT 2023
;; MSG SIZE rcvd: 169

```

[2ddhz-5aaaa-aaaam-abf4a-cai.icp0.io/.well-known/ic-domains](http://2ddhz-5aaaa-aaaam-abf4a-cai.icp0.io/.well-known/ic-domains)

---

<div class="post-metadata">

**Author:** ![diegop](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/diegop/32/569_2.png) [@diegop](https://forum.dfinity.org/u/diegop)\
**Post date:** [March 20, 2023, 12:24am UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/2 "2023-03-20T00:24:06Z")

</div>

Let me pass it to folks

---

<div class="post-metadata">

**Author:** ![raymondk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/raymondk/32/6174_2.png) [@raymondk](https://forum.dfinity.org/u/raymondk)\
**Post date:** [March 20, 2023, 12:41am UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/3 "2023-03-20T00:41:48Z")

</div>

Hi @Hazel - your setup is perfectly fine. The issue is on our side and we will have it fixed but EOD tomorrow.

To make a long story short, we’re upgrading canister that orchestrates and stores the custom domain registrations and there is a bug that is preventing new registrations from going through. (The upgrades are required to future proof the custom domains canister - eg paginating results and things of the sort)

We’ll kick off the registration for you as soon as the update is rolled out. Apologies for the inconvenience.

-Raymond

Updated to mention that domains that are already hosted are not affected, however certificates are valid for 3 months and get renewed regularly. When the canister is upgraded there will be the equivalent of a renewal and (like for regular renewals) the setup must be correct as specified in [Internet Computer Content Validation Bootstrap](https://internetcomputer.org/docs/current/developer-docs/production/custom-domain/)

---

<div class="post-metadata">

**Author:** ![Hazel](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hazel](https://forum.dfinity.org/u/Hazel)\
**Post date:** [March 20, 2023, 1:12pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/4 "2023-03-20T13:12:02Z")

</div>

> [@raymondk](#):
>
> Updated to mention that domains that are already hosted are not affected, however certificates are valid for 3 months and get renewed regularly. When the canister is upgraded there will be the equivalent of a renewal and (like for regular renewals) the setup must be correct as specified in [Internet Computer Content Validation Bootstrap](https://internetcomputer.org/docs/current/developer-docs/production/custom-domain/)

Thank you! So, if I’m using the boundary nodes I _do not_ have to take any other action aside from making sure my configurations are correct?

---

<div class="post-metadata">

**Author:** ![raymondk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/raymondk/32/6174_2.png) [@raymondk](https://forum.dfinity.org/u/raymondk)\
**Post date:** [March 20, 2023, 4:48pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/5 "2023-03-20T16:48:00Z")

</div>

> [@Hazel](#):
>
> Thank you! So, if I’m using the boundary nodes I _do not_ have to take any other action aside from making sure my configurations are correct?

That’s correct - basically keeping the required configuration the same as you had it for the registration to complete.

---

<div class="post-metadata">

**Author:** ![raymondk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/raymondk/32/6174_2.png) [@raymondk](https://forum.dfinity.org/u/raymondk)\
**Post date:** [March 21, 2023, 12:58am UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/6 "2023-03-21T00:58:35Z")

</div>

FYI @Hazel your cert is available now:

```auto
❯ curl https://icp0.io/registrations/0da6b7c85ab580841a396de26aaadf75bd0726a0d7282da865aa9b66aea9d1de
{"name":"app.unid.ooo","canister":"2ddhz-5aaaa-aaaam-abf4a-cai","state":"Available"}%

```

---

<div class="post-metadata">

**Author:** ![Hazel](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hazel](https://forum.dfinity.org/u/Hazel)\
**Post date:** [March 21, 2023, 2:03am UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/7 "2023-03-21T02:03:24Z")

</div>

Thanks @raymondk!

Unfortunately, still seeing a 404 error and a cert error.

Not sure whats up → [https://app.unid.ooo](https://app.unid.ooo)

Linking to the [canister directly](https://2ddhz-5aaaa-aaaam-abf4a-cai.icp0.io/) seems fine

---

<div class="post-metadata">

**Author:** ![raymondk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/raymondk/32/6174_2.png) [@raymondk](https://forum.dfinity.org/u/raymondk)\
**Post date:** [March 21, 2023, 2:39am UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/8 "2023-03-21T02:39:34Z")

</div>

🤦‍♂️ it’s only turned on for a canary… we haven’t rolled it out everywhere.  
I’m not sure exactly why we didn’t roll it out entirely to prod yet, I’ll check with the team and send an update in the morning.

If you want to see it working though you can add this entry in your /etc/hosts file (on linux or mac) that’s the ip of the canary.

```auto
162.247.129.233 app.unid.ooo

```

---

<div class="post-metadata">

**Author:** ![Hazel](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hazel](https://forum.dfinity.org/u/Hazel)\
**Post date:** [March 21, 2023, 2:41am UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/9 "2023-03-21T02:41:49Z")

</div>

Appreciate all your help here, have a great night! 😄

---

<div class="post-metadata">

**Author:** ![raymondk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/raymondk/32/6174_2.png) [@raymondk](https://forum.dfinity.org/u/raymondk)\
**Post date:** [March 21, 2023, 3:00pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/10 "2023-03-21T15:00:40Z")

</div>

The updates are rolled out @Hazel, you’re good to go (I double checked this time 😉 )

---

<div class="post-metadata">

**Author:** ![Hazel](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hazel](https://forum.dfinity.org/u/Hazel)\
**Post date:** [March 21, 2023, 3:36pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/11 "2023-03-21T15:36:16Z")

</div>

Thanks @raymondk!

This is super exciting. First domain I’ve linked up to the IC 🥳.

---

<div class="post-metadata">

**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\
**Post date:** [June 15, 2024, 7:08pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/12 "2024-06-15T19:08:21Z")

</div>

Hi Raymond,

 ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/e/d/ed2c28c51d7f1667463c7b045a01bcc5f913d74e.png)

I’m getting a similar error, any ideas why?

Kind regards,  
James

---

<div class="post-metadata">

**Author:** ![rbirkner](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbirkner](https://forum.dfinity.org/u/rbirkner)\
**Post date:** [June 15, 2024, 8:28pm UTC](https://forum.dfinity.org/t/issue-registering-domain-500-error-https-icp0-io-registrations/19010/13 "2024-06-15T20:28:24Z")

</div>

Hey @jamesbeadle

It is not the same issue. I replied to you in the other thread that you started: [Unexpected error registering domain - #2 by rbirkner](https://forum.dfinity.org/t/unexpected-error-registering-domain/32015/2)