Unable to Add Verified Subdomain to Google App Engine

[flyingjet]

I'm attempting to set up a standard App Engine instance using my subdomain. I've confirmed that the subdomain is correctly configured with my domain service provider.

When I try to verify the subdomain in Google App Engine's settings, it fails. However, I can successfully verify the main domain. Now, I'm unable to add the subdomain to App Engine. It indicates that the subdomain is verified, but only the main domain appears in the dropdown. Both the main domain and subdomain properties are visible in Google Search Console.

assume main domain as : mymaindomain.com and sub domain as app.mymaindomain.com. 

How can I resolve this issue?

[KyleMari · Accepted solution]

Hi @flyingjet,

Welcome to the Google Cloud community!

If I understood correctly, Google Cloud console simply couldn't find your subdomain (as it appeared missing in the drop-down selection) while it never indicated that it wasn't verified with a prompt like "Your domain hasn't been verified yet. Finish all the steps in Search Console and then return to this page.". I've also taken note that in the search console, the search result for the subdomain (as well as the root domain) proves its presence with a good status.

Though I'm not quite sure about the underlying status of your subdomain from the Google Cloud App Engine's point of view, here are the initial workarounds that you could try:

• Refresh domains: If you're in the “Add a new custom domain” section of the console, try clicking “Refresh domains” to see if that would allow the list of all the verified domains to appear in the drop-down selection. If the subdomain is proven to be verified/detectable in the search console, try to wait for some time and then re-add the same subdomain as a new domain by typing it in the text box (as mentioned in step #4 of this instruction). Observe how the App Engine will indicate its verification status.
• Make sure the subdomain is not linked to another project: Though this factor could be unlikely for you, still verify that this isn't the case.
• Reverify the subdomain using another account: This workaround was proven to be effective according to @eduardohgs in a similar forum. Add a new project member while seeing to it that it's granted an owner role or at least has an App Engine Admin role. Using that account, re-attempt to verify the same subdomain by obtaining another TXT record from the search console. With another TXT record, add that as a new entry in the current DNS configuration for your subdomain.

If the issue persists, it would be best to contact the Google Cloud support so that the team will be able to dig deeper into your subdomain's internal verification status and provide you with the best steps forward.

Hope this helps!

[flyingjet]

@KyleMari Thanks for explaining the problem in detail. It looks like timing issue. After a few hours it did refresh with the verified status.