Domain Puzzle

81 views
Skip to first unread message

Joshua Smith

unread,
Jan 8, 2019, 10:38:11 AM1/8/19
to Google App Engine
I have a site that I set up ages ago, back when you had to have gsuite to map domains to google app engine.

On the GSuite console, it redirects the naked domain to www, as one did back then. The redirect monkey is stupid, though, in that it discards the path part of the URL.

Now I’d like to support the naked domain directly on GAE, but it won’t let me because it says that the naked domain is already being used.

I can’t remove the mapping in gsuite, because there’s no button to remove it. Only a button to change it (and there’s no “delete” option there).

Helpful screenshots attached.

Has anybody who’s been around forever like me managed to make the transition to modern naked domains successfully?

-Joshua


Tiago (Google Cloud Platform Support)

unread,
Jan 14, 2019, 4:56:42 PM1/14/19
to Google App Engine
Hello Joshua,

The error message you provided indicates that the domain is currently in use by some other project. You can add custom domains using the Cloud Console, the Cloud SDK or through the App Engine APIs. In your particular case, the best way to re-add the domain to this particular project is to use the App Engine APIs since it gives you the additional option to override any existing mappings for the domain in question (assuming, of course, that the domain ownership has already been verified via the Webmaster Central portal).

Here’s a brief set of instructions on how to use the API: 
1. Visit the API Explorer and authorize OAuth requests to be performed for your account
2. Enter your App ID under appsId, set overrideStrategy to OVERRIDE, and provide the domain in the body request as an “id” property. 

You can enable SSL support afterwards in the Cloud Console by going to App Engine > Settings > Custom Domains, selecting the domain in question and clicking on “Enable managed security”.

As for the G Suite mapping, in order to remove a primary domain in the Admin Console, a second one has to be added and verified first. Then you can make the newly added domain your secondary, and later remove the original domain. This operation can cause issues with some G Suite services though, so I would suggest going for the API and Cloud Shell routes first. 

Joshua Smith

unread,
Jan 15, 2019, 1:25:09 PM1/15/19
to Google App Engine
I’m not going to pretend I have any idea how that spooky magic worked, but you solved my problem!

I’ll buy you a beer next time I’m near your googleplex.

-Joshua

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/d6900f1f-88e5-4008-8f1f-62c55502f51c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tiago (Google Cloud Platform Support)

unread,
Jan 18, 2019, 1:07:20 PM1/18/19
to Google App Engine
Happy to be helpful, Joshua. And here’s hoping your promises are fulfilled.

Cheers! 
Reply all
Reply to author
Forward
0 new messages