When attempting to edit my DNS records in the dashboard, the page looks like it’s about to load but then redirects to a page that says “It looks like we’re having some internal issues. Our team has been notified. If you’d like to help, tell us what happened below.”
This has been occurring for at least the past 4 hours now. I’ve went through the usual process of elimination by clearing cache, incognito, different browser, different desktop/laptop, mobile device, mobile hotspot but I still encounter the same issue. Screenshot below.
1 Like
Are you able to open https://dash.cloudflare.com/?to=/:account/:support? If so, then you should make an account ticket.
I’m able to go to the dashboard but when trying to follow the link you posted, it just says “The Cloudflare dashboard is loading.” and nothing more. Pardon me if this is not the relevant location for my post.
I have escalated this issue.
2 Likes
Hi @timmo sorry for the issues, I made some adjustments to your account, can you clear cache & cookies and see if the error persists?
1 Like
Hey Cloonan, I appreciate the response but I’m still experiencing the same issue.
1 Like
I am also encountering the same issue.
For added context: it is only isolated to one of my sites on my account, and it began when I tried making a custom domain for a Cloudflare Pages app/site.
After I put the subdomain I wanted, it said the record was already created and so when I went to go check it gave the same reasoning as the OP’s image.
1 Like
Hi there,
I’ve just raised a ticket on your behalf and am now requesting some additional information on it.
#2938147
Take care.
5 Likes
Appreciations.
Apologies for the rudimentary question but will I be able to see the ticket you’ve made in my https://support.cloudflare.com/hc/en-us/requests page in order to clarify any questions someone may have (as I don’t see any ticket there now) or is this something I should just be waiting on for someone to contact me further?
I’ve worked with support and can confirm that the issue is now resolved. Not sure if it was unique to my account or what but I’m thankful for the response and support.
1 Like
Hi there,
Hey @baron100 , can you test if it’s also solved in your account? It might be, but as per your description it might also be unrelated.
Please let us know when you can.
Take care.
Thanks for the follow-up.
So I believe I solved my problem using Cloudflare’s API on Sept 20th or so, it solved my specific issue but unfortunately did not give me a reason as to why this was happening beyond what I describe below:
I made an API token, accessed the records for the site and deleted the offending DNS record through “Delete DNS Record” DELETE method.
The record itself when I viewed it before deletion via GET did not look malformed and was identical (or so it seemed) to the records around it.
After that I was totally able to view the DNS management page for the domain.
But for context — because I couldn’t for the life of me understand why — when I tried creating the CNAME for the Cloudflare Pages site again the problem only returned (the problem being the inability to view the DNS records for the site via the DNS management page) when using the subdomain string hjkl in the Name field which was also a substring in the Content field.
Perhaps it was just something I was missing, but I thought it was very odd. I have other subdomains for the same site whose Name fields have a string that is a substring of the Content fields that work fine.
When changing the hjkl Name field string to anything else the DNS management page for the domain was completely normal and viewable, which is what I winded up doing (although my Cloudflare Pages site is still not really viewable through the new subdomain, this issue (Error Code 522) was present while the DNS management page was un-viewable and am unsure if it’s related; it is possible that it’s something I’ve done incorrectly and have not yet had the time to fix, I don’t know).
Hi there,
So, for a little context, this was related to a punycode issue on the dashboard. After we figured it out in a couple of users, we rolled out a fix on the 21st that should solve all related issues.
Take care.
2 Likes