Dangling domain

Is there someone from CF I can give my account ID and bucket name to to have a quick look at it? 🙏
10 Replies
Unknown User
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
kev-ac
kev-acOP•15mo ago
Thanks for your help, @Sid | R2. I recreated the whole bucket, now it seems to work. If it is helpful for you to get the data nethertheless to find out why it was dangling, I'm happy to give you the details. While doing this I noticed two things: - After recreating the stats (bucket size, class a/b operations) were retained - The DNS UI shows a warning icon left to the subdomain that indiciates that no certificate is issused for this subdomain (two-level-subdomain), but a certificate was indeed issued.
Unknown User
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
kev-ac
kev-acOP•15mo ago
I don't really care if the stats reset to 0 or not, so don't worry. Just something I noticed. Is the warning in the DNS UI just a bug or do I have to worry that a certificate renewal could fail in the future?
kev-ac
kev-acOP•15mo ago
.
No description
Unknown User
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
kev-ac
kev-acOP•14mo ago
Done ✌️ @Sid | R2 I hope its okay pinging you for this here because we've communicated about this before. I'm having the same issue again on a different bucket, this time its an active domain which cannot be removed with the "The specified bucket does not exist. (Code: 10006)" error. For this bucket I cannot recreate it because its in an active deployment. Will you be able to help me with that and/or remove the domain from your end?
Unknown User
Unknown User•14mo ago
Message Not Public
Sign In & Join Server To View
kev-ac
kev-acOP•14mo ago
I meant that is in active use and cannot be recreated (last time it happened I just deleted and recreated the bucket). The problem is actually solved for me. Someone here told me its an issue in the dashboard for buckets with EU jurisdiction. Altering the DELETE request to the api by changing the jurisdiction header from „Default“ to „eu“ solved it. Btw. The endpoint returns a 200 status even it is does „nothing“ with „Default“ jurisdiction. See here and the messages below: https://discord.com/channels/595317990191398933/940663374377783388/1170703191059480606
Unknown User
Unknown User•14mo ago
Message Not Public
Sign In & Join Server To View
Want results from more Discord servers?
Add your server