Unexpected expected error when using curl -sLv -X POST \ for Custom Domain

Developers Command Line Tools
1

Hello everyone! I’m not sure if you guys encountered an “unexpected error” when running the following code to get the REQUEST_ID for the domain name set up. It worked awhile ago but currently it is not working. Is it really like that? Thank you!

CURL Line

curl -sLv -X POST \
	-H 'Content-Type: application/json' \
	https://icp0.io/registrations \
	--data @- <<EOF
{
	"name": "CUSTOM_DOMAIN"
}
EOF

Result

*   Trying 147.28.156.126:443...
* Connected to icp0.io (147.28.156.126) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=boundary.dfinity.network
*  start date: Apr 20 17:18:48 2023 GMT
*  expire date: Jul 19 17:18:47 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
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x55c0603bc560)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> POST /registrations HTTP/2
> Host: icp0.io
> user-agent: curl/7.81.0
> accept: */*
> content-type: application/json
> content-length: 32
> 
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* We are completely uploaded and fine
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 500 
< server: nginx/1.21.3
< date: Fri, 09 Jun 2023 09:56:13 GMT
< content-length: 16
< access-control-allow-origin: *
< access-control-allow-methods: HEAD, POST
< 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
< 
* Connection #0 to host icp0.io left intact
unexpected error
2

Just to be sure, you are not providing CUSTOM_DOMAIN as domain name as in your above snippet but, your effective domain right?

curl -sLv -X POST \
	-H 'Content-Type: application/json' \
	https://icp0.io/registrations \
	--data @- <<EOF
{
	"name": "CUSTOM_DOMAIN" // <---- here
}
EOF
3

Nvm my last question, it seems we are able to reproduce it. Team will have a look.

4

Hi @dindog18

we found the issue and are working on resolving it. We will let you know once it is working again! Sorry for the inconvenience!

5

As a temporary workaround, you can target one specific node that is working:

curl -sLv -X POST \
        -H 'Content-Type: application/json' \
        --resolve icp0.io:443:2604:1380:45e1:a603:5000:cfff:feaf:ee86 \
        https://icp0.io/registrations \
        --data @- <<EOF
{
        "name": "CUSTOM_DOMAIN"
}
EOF
6

Hi @dindog18

We have fixed it and it should work again. Please let us know if it is not the case for you!

2 Likes
7

Hello @rbirkner and @peterparker!

The issue has been fixed and accessible in multiple computers. Thank you very much for your help!

2 Likes