Hello,
I have mainly given you the instructions outlined from two to four of the sections “Adding a custom domain for your application” of the document <https://cloud.google.com/appengine/docs/standard/python/mapping-custom-domains#adding_a_custom_domain_for_your_application> that you shared. I have noticed that you are using original App Engine SDK which does not have gcloud commands. As a possible workaround you can download Google Cloud SDK for Python from here <https://cloud.google.com/appengine/docs/standard/python/download#installing-cloud-sdk-for-python> in a different machine and try to run the gcloud commands. Unfortunately, I do not have the privilege to run the command for you. On Wednesday, December 12, 2018 at 11:33:07 PM UTC-5, Devel63 wrote: > > @Mohammad I, thanks for the response. I think the screen capture shows > that we are already using Google managed security. Everything is working > except the https://mydomain.com > > www.mydomain.com, https://www.mydomain.com, mydomain.com ... all work and > end up on https://www.mydomain.com > > Only https://mydomain.com does not work. > > Given that, do you think your advice will still work? Unfortunately, I > cannot use gcloud commands, as I use the original App Engine SDK, and will > lose access to the appcfg command if I overwrite it with the GCloud SDK ( > https://cloud.google.com/appengine/docs/standard/python/download bottom > of page). Is there another way to do this, or can you do it for me? > > > > On Wed, Dec 12, 2018 at 10:05 PM 'Mohammad I (Cloud Platform Support)' via > Google App Engine <[email protected] > <[email protected]>> wrote: > >> It is appearing the naked custom domain has already been mapped. You can >> verify that by running the GCLOUD command “gcloud app domain-mappings >> list” >> <https://cloud.google.com/appengine/docs/standard/python/securing-custom-domains-with-ssl#verify_a_managed_certificate_has_been_provisioned>which >> >> should show the list of your domains, subdomains and their corresponding >> certificates or you can run the GCLOUD command “gcloud domains verify >> DOMAIN” >> <https://medium.com/google-cloud/app-engine-transition-your-website-to-https-b280f0bf5147> >> >> to verify your domain is registered as verified by Google Cloud Platform. >> After that you can upgrade to Google managed SSL certificates using the >> GCLOUD command “gcloud app domain-mappings update DOMAIN >> --certificate-management='AUTOMATIC'” following the instructions outlined >> here >> <https://cloud.google.com/appengine/docs/standard/python/securing-custom-domains-with-ssl#verify_a_managed_certificate_has_been_provisioned>. >> >> If you are using your own SSL certificates you should follow the >> instructions outlined here >> <https://cloud.google.com/appengine/docs/standard/python/securing-custom-domains-with-ssl#using_your_own_ssl_certificates>. >> >> After that you should be able to redirect the naked domain to HTTPS on the >> naked domain. >> >> I have noticed that you have shared your personal information like >> “Project Id” and custom domain in this Google Groups post. I would advise >> you to take caution before sharing any personal or project specific >> information like these in any public forums as they can be used to harm >> your application. >> >> >> On Sunday, December 9, 2018 at 9:07:19 PM UTC-5, Devel63 wrote: >>> >>> We have an existing app engine project started a number of years ago. >>> It serves managed security HTTPS on the www subdomain. >>> >>> [image: Custom_Domain.png] >>> At the time of creation, naked domains were not supported. The >>> instructions >>> <https://cloud.google.com/appengine/docs/standard/python/mapping-custom-domains> >>> only >>> cover how to do that for a new project, and don't work for an existing one. >>> >>> Following the clues in the instructions, we added the 4 AAAA records to >>> our DNS provider (a "new" requirement), and now the HTTP naked domain >>> redirects to HTTPS for www, which is good. But we'd like it to do the same >>> thing for HTTPS on the naked domain, and that gets an ERR_CONNECTION_CLOSED. >>> >>> We tried adding the naked custom domain via the console, but that >>> doesn't work because it's already at least partially mapped: >>> >>> [image: Custom_Domain_Step2.png] >>> What can we do to get the naked domain working with HTTPS? >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Google App Engine" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-appengine/XNefdPm_jkk/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected] >> <[email protected]>. >> 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/05a963c9-0e1b-4b45-83c5-d7fc1c9f646f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-appengine/05a963c9-0e1b-4b45-83c5-d7fc1c9f646f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/d3d83179-2dcd-4d6d-9ef6-2d9c499d292b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
