custom domain SSL not activating

360 views
Skip to first unread message

Miika Anundi

unread,
May 13, 2021, 12:39:43 PM5/13/21
to Google App Engine
I am stuck on " The certificate is being activated." with my app engine naked domain SSL. 
https://www.lorugames.com/
www subdomain is working.

http://lorugames.com also works if I change app.yaml  secure: always to optional. 

SSL connection is required for our site. 

Thing I've done:
-I've changed the whole domain to my another domain and it worked in 10mins also naked SSL
-Changed back to original and no luck. Still stuck.
-https://toolbox.googleapps.com/apps/dig/ shows correct ips.
-I have removed all the dns records from my registrar multiple times and waited for 12hours.




NoCommandLine

unread,
May 13, 2021, 3:28:26 PM5/13/21
to Google App Engine
1) Did you try signing out and signing back in?

2) You could also try removing the link for the 'www' subdomain, and try adding the naked domain first. If you get that working, then add the 'www' subdomain. Separately - I think you should have only of them (either naked or www) and then redirect the other to it. This way you have one set of urls for SEO purposes

  ..... NoCommandLine ......
 https://nocommandline.com

A GUI for Google App Engine

Miika Anundi

unread,
May 14, 2021, 9:57:35 AM5/14/21
to Google App Engine
1) Did you try signing out and signing back in?
Yes
2) You could also try removing the link for the 'www' subdomain, and try adding the naked domain first. If you get that working, then add the 'www' subdomain. Separately - I think you should have only of them (either naked or www) and then redirect the other to it. This way you have one set of urls for SEO purposes
AppEngine sets app www automaticly as CNAME when creating custom domain. Could try to add them seperately but I think it wont solve the problem:

Using cloud shell I found out that even when I remove all domain mappings there are 2 managed certs on the cert listing, these cannot be deleted because they are connected to domain mapping. I have now sent feedback to google about this issue and hope it will be resolved by them.
Reply all
Reply to author
Forward
0 new messages