Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Hi Kamran I have changed the CNAME to be ghs.googlehosted.com. and that did sort out the problem Thanks for your help. Regards Tim Hoffman On Tuesday, September 19, 2017 at 7:46:08 AM UTC+8, Kamran (Google Cloud Support) wrote: > > > Hello Tim, > > It looks like that CNAME record of your

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Please send me your project id and domain that's having the issue privately and we'll take a look. On Fri, Sep 22, 2017 at 6:33 AM, Tapir wrote: > > > On Thursday, September 21, 2017 at 5:55:29 PM UTC-4, Lorne Kligerman wrote: >> >> Glad it kicked in! If DNS entries aren't

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

On Thursday, September 21, 2017 at 6:01:07 PM UTC-4, Kamran (Google Cloud Support) wrote: > > Tapir, > > You can use "secure" handlers subelement to automatically redirect HTTP > requests to the HTTPS URL with the same path. For more information on > this visit this article >

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

On Thursday, September 21, 2017 at 5:55:29 PM UTC-4, Lorne Kligerman wrote: > > Glad it kicked in! If DNS entries aren't found, the system will > automatically retry, however it will back off and the retry is less > periodic the longer time passes. Have you tried checking off only one >

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Tapir, You can use "secure" handlers subelement to automatically redirect HTTP requests to the HTTPS URL with the same path. For more information on this visit this article . On Thursday, September 21, 2017 at 6:45:56 AM

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Glad it kicked in! If DNS entries aren't found, the system will automatically retry, however it will back off and the retry is less periodic the longer time passes. Have you tried checking off only one domain in the table? Are the buttons still disabled then? On Thu, Sep 21, 2017 at 3:45 AM,

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

On Wednesday, September 20, 2017 at 8:32:16 AM UTC-4, Tapir wrote: > > > > On Monday, September 18, 2017 at 7:54:13 PM UTC-4, Kamran (Google Cloud > Support) wrote: >> >> >> No. Updating the CNAME to point to *ghs.googlehosted.com >> *shouldn't interrupt your

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

On Monday, September 18, 2017 at 7:54:13 PM UTC-4, Kamran (Google Cloud Support) wrote: > > > No. Updating the CNAME to point to *ghs.googlehosted.com > *shouldn't interrupt your HTTP service. > how long will it take effect after clicking the "Enable Managed

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

No. Updating the CNAME to point to *ghs.googlehosted.com *shouldn't interrupt your HTTP service. On Monday, September 18, 2017 at 7:50:12 PM UTC-4, timh wrote: > > Ok > > The cname record is what was there from the many years old mapping. > > I havent changed

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Just a bit more background This site was mapped to a google apps domain back in September 2012, that is when the cname record as it currently is was set up. Thanks Tim > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Ok The cname record is what was there from the many years old mapping. I havent changed that as I was concerned we would then lose access to the site. Ignoring the ssl security do you see it changing causing a problem for http Thanks Tim On 19 Sep. 2017 7:46 am, "'Kamran (Google Cloud

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Hello Tim, It looks like that CNAME record of your domain is not correctly configured. Please login to your domain registrar and modify the CNAME record of your domain to point to *ghs.googlehosted.com. *Right now I can see that it's configured incorrectly pointing to ghs.google.com. After

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Hi Lorne Here is the link https://issuetracker.google.com/issues/65781183 The DNS changed in cloud console on reverification, and our site is accessible using the name. So I don't have any evidence to suggest it didn't . Regards Tim Hoffman On Tue, Sep 19, 2017 at 1:00 AM, 'Lorne

[google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Tim, are you sure your DNS records have been updated? Could you send me a link to the public issue you logged with more details? Thanks! On Sunday, September 17, 2017 at 8:22:02 AM UTC-7, Mike Hardy wrote: > > Likewise. I posted it here > . > > On

[google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Likewise. I posted it here . On Saturday, September 16, 2017 at 6:24:25 PM UTC-7, timh wrote: > > Hi > > Thanks have done so. > Other than it not working there isn't much to report, there are no error > messages as such, just the forever spinning

[google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Hi Thanks have done so. Other than it not working there isn't much to report, there are no error messages as such, just the forever spinning circle. The main bit of info will of course be the appid. Cheers T On Sunday, September 17, 2017 at 5:58:40 AM UTC+8, Kamran (Google Cloud Support)

[google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

Hello Tim, I'd recommend filing an issue on Google Issue Tracker include reproduction steps, the error messages that you receive or a redacted screenshot of the error, your Project ID and any other information that could help us to investigate

[google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

+1 I've got the same problem. On Friday, September 15, 2017 at 9:47:38 PM UTC-7, timh wrote: > > So I re-verified the same domain which appeared to work. > It's details now look different but everything still working. > > I then "Enable Managed Security", and it started to show "Google-managed,

[google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

So I re-verified the same domain which appeared to work. It's details now look different but everything still working. I then "Enable Managed Security", and it started to show "Google-managed, auto-renewing " under SSL Security. However an hour later the adjacent spinning gif is still spinning,