Unable to access Cloud DNS

[Willem Grobler]

I am unable to access the cloud DNS page on my Cloud Platform. When I click on Cloud DNS from the menu, I am greeted with a blank page. I can see the title bar & menu, but the content area is blank. It doesn't load my DNS zones nor give me any option to add zones. There is no error anywhere on the page.

Upon checking the DevTools Console I was able to see the following errors:

404: https://cloudusersettings-pa.clients6.google.com/v1alpha1/settings/CONSOLE_NAV_HIDE_PRODUCTS?

{ "error": { "code": 401, "message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.", "status": "UNAUTHENTICATED" } }

404: https://cloudusersettings-pa.clients6.google.com/v1alpha1/settings/SIDENAV_COMPACT_MODE?

{ "error": { "code": 401, "message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.", "status": "UNAUTHENTICATED" } }

I don't know how it is possible to have missing authentication credentials within Cloud Console itself. Can anyone help?

[Ahmad Elias Hamanudin]

Can you reproduce this issue using gcloud? This will help indicate whether it's an issue with one of the basic API calls or perhaps an issue with the cloud console itself. Please try running the following:

gcloud dns managed-zones list

Additionally, Google Groups is reserved for general inquiries related to products. I would advise you to please post your question and continue this thread on Stack Overflow [1] or Server Fault [2] to receive technical assistance. Or if you have a support plan [3], please open a ticket with GCP support.

[1] https://stackoverflow.com/
[2] https://serverfault.com/
[3] https://cloud.google.com/support

[Willem Grobler]

Thanks for the reply. I tried it on gcloud as suggested. It is working there, so it must be an issue with the cloud console itself. 

I already opened a ticket on Stackoverflow (https://stackoverflow.com/questions/64159356/unable-to-access-cloud-dns), but haven't received any feedback on that side. I wasn't really sure where the correct place was to post the question so I tried it here as well. Since gcloud is working, I assume my account permissions are correct and as you said, it must be a cloud console error. Don't know if the community would be able to assist me with a cloud console bug, it would suck if I have to sign up for a support plan only to access the web ui. 

[yananc]

We experienced an issue with Cloud Console’s Cloud DNS section. The issue has been resolved by our Product Engineering team. Please let us know if the issue still persists. Thank you.

[Mike Westman]

I still can't access the Console DNS. It keeps saying that it is enabling the API over and over again.

I've been using the service for years and can't manage it.

[Gagandeep Toor]

There is a few things that you can review:

- Ensure that you have billing setup.

- Make sure you don't run any firewall/anti-virus/vpn/filtering service on your machine or network.

- Try to do it from a different machine and from a different network without any extension running

This could be due to something blocking it from enabling. Would it be possible to provide us with a screenshot(s) of the errorPage and from where you're trying to enable it. Also, do you get the same thing if you try to enable any other services?

[Willem Grobler]

I was able to access it again after some time. When I tried to access it again after two weeks it was working fine. So whatever update was made by the product engineering team worked for me.

While I was having problems I shared the project with my personal Gmail account. By giving editing access to the second Gmail account I was able to access my Cloud DNS from the website.  Making the 2nd account an Admin resulted in the same errors, I had to make it an editor or viewer to access the DNS page. Perhaps this solution can work for someone else having a similar issue.

[Dattu Pragnu Nellutla]

Thank you for confirming that the issue was fixed.I'm glad that the issue was fixed by modifying the permission to editor or viewer permission.