Custom domain registered and valid, but ports 80/443 are timing out

Developers SNS Framework
1

Hi, our Jupiter Faucet custom domain stopped working today, 21 August, after working normally yesterday. There haven’t been any frontend changes or deployments.

Affected domains:

  • jupiter-faucet.com
  • www.jupiter-faucet.com

The direct canister URL is still working normally:

  • https://jufzc-caaaa-aaaar-qb5da-cai.icp0.io/

We’ve run through diagnostic steps and found:

  • both custom domains report registered;
  • both pass ICP validation as valid;
  • the expected canister ID and ACME DNS records are present;
  • authoritative DNS, 1.1.1.1 and 8.8.8.8 all agree;
  • the deployed /.well-known/ic-domains file is correct;
  • both ports 80 and 443 time out before TLS begins;
  • even curl -k cannot establish a connection.

Both domains currently resolve to:

  • IPv4: 23.236.116.77
  • IPv6: 2602:fb2b:120:100:e86a:b3ff:fe92:77ea

This looks like it may be a custom-domain gateway or edge-routing issue rather than a DNS, certificate-validation or frontend problem. Could someone from DFINITY check the gateway state for these domains? @rbirkner, @bjoern

2

‘ello there, mates.

This is going to come as a shock, but our team actually has quite a bit of experience with this problem we do.

Just sayin we’re happy to look into it.

No strings attached mates.

3

Normally, I wouldn’t trust @Dionysus but I think he’s actually telling the truth this time.

4

Yeah, don’t worry precious, it can trust us.

Let’s just take a little look under the hood and see what we find.

Don’t mind if we do!

5

Oh we have wonderful news precious yes!

wonderful news we do.

Not only did we find the problem precious,

We fixed it we did! Can you believe that?

Jupiterfaucet.com

6

Hey @Jupiter_Faucet

Your domain is pointing to one specific HTTP Gateway that has been retired. That’s why your domain is not working anymore.

Ideally, you would not point to a single gateway using A/AAAA, but rather use an CNAME/ANAME/ALIAS record pointing to jupiter-faucet.com.icp1.io. That’s more robust.

7

Thanks for pointing that out, we’ll get that sorted. Cheers

8

Ok I’ll admit, I was wrong.

You would think I would have learned by now not to trust him.

Fortunately, rbirkner is a helpful member of the community.

9

Fixed, thanks @rbirkner

JUPITER FAUCET