Your web3 gateway steals websites

What is the name of the domain?

ledechaine.quebec

What is the error number?

1001

What is the error message?

web3 dnslink: “Hostname already exists”.

What is the issue you’re encountering

No, it doesn’t.

What steps have you taken to resolve the issue?

-Delete everything from Cloudflare
-“Remove from cloudflare”
-Re-connect and retry

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

-Set a Cloudflare web3 gateway.
-Deactivate it because, for some reason, it stopped working.
-Try to reactivate it
-Realize Cloudflare stole your domain and you can’t link it to anything anymore because the first “/ipns/link” you chose is forever hard-coded somewhere in the Cloudflare infrastructure, inaccessible to the user who actually owns it.

1 Like

Hey @ledechaine I was able to reproduce this at first but then after a short few minutes the domain freed itself from Cloudflare’s grasp and I was able to add it again.

Is there a specific subdomain you have this issue with, or the ledechaine.quebec domain as a whole? And if you try it again now after some time, does it still happen?

4 Likes

Hi!

Both ledechaine.quebec and www.ledechaine.quebec can’t be modified anymore. Everything else can be modified as normal. I also paused Cloudflare for 12 hours, nothing changed.

Still says “Hostname already exists”, but doesn’t appear in the (now empty) list of gateways.

There’s definitely a mismatch there.

(Fun fact: I started getting a ton of “404 not found” pages today. So after all that I set a web3 gateway for www2.ledechaine.quebec, linking to the same /ipns/website. It worked in seconds, which also apparently re-provisioned your IPFS mirrors… therefore it fixed www.ledechaine.quebec at the same time. No more 404s on the main website either.)

2 Likes

Any ideas why it’s bugged? I don’t know… what my domain needs to do to, or is waiting for, to “free itself from Cloudflare’s grasp”. Someone might need to manually add www.ledechaine.quebec to my Web3 Gateways, so I can then re-modify it.

By the way… Your Cloudflare web3 gateway really needs to be its own, separate, thing, separated from web2. All you need to do is CNAMEipfs.cloudflare.com” to “your.website” (from any DNS), and set an /ipns/address in your Cloudflare web3 gateway, and it’s done. Why would I need to use “ns.micah” and etc. to “verify my account”, when the CNAME means I already allowed everything to be redirected to you?

Oh, I fixed it. DNSlink conflicts. My fault.

Forgot I had dnslinks with other DNS servers than cloudflare. Whatever you write in “DNSlink” doesn’t matter when your website’s DNSlinks are already set by other DNS servers. Apologies.

3 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.