We have developed a website, which was wroking fine until some days back, but suddenly it stopped working on custom domain. It still wroks fine on appspot subdomain. I rechecked all the settings, they are all okay as per gae guidelines...
http://www.thesudokutimes.com/ (This one is not working)
http://thesudokutimes.appspot.com/ (It is accessible here)
Can any one suggest what could be the problem?
This does not seem related to Google App Engine but to a more generic DNS problem.
Using Dnsstuff tools you can see that your domain name was updated by your Registrar the 23th november 2010 and the IP for thesudokutimes.com can't be determined.
I suggest you to double check your configurations and contact your Registrar asking for support.
Related
I'm doing a server-side GTM setup. I managed to set up a Google cloud App engine.
I added a custom domain (verified with Google webmaster central, added DNS records etc.).
I can see in the Cloud settings that the custom domain (actually it's a subdomain) is set up, using also Google-managed, auto-renewing SSL.
So, everything looks fine except when I try to access this custom domain (directly or while doing a GTM container preview), I get the connection error in the browser (ERR_CONNECTION_CLOSED).
Since all DNS records looks OK (I have TXT record for the GWC/ownersip verification, 4 A records and 4 AAAA records for Google cloud) I did a tracert where I can see that it gets to the google server (hop 5), but then it gets lost:
The last hop should be the subdomain, but it's a "random" Google server).
It's more than 24 hours from the DNS records change so I don't believe it's a DNS propagation issue (although it still might be of course but the chances are very small). So if anyone has any idea, what could be wrong, I'd be very glad :D
I managed to repeat exactly the same setup with another subdomain (on totally different domain). I had issues with geeting Google-managed certificate - it took the App Engine a really long time to install it. But at the end it worked.
So it looks like the issue is indeed with Google and the certificate. I'll wait and let you know if this was the issue.
Edit (additional explanation): it turns out that the issue is with the client's domain which doesn't allow another CAA (in this case Google or Let's encrypt) to issue a certificate.
You haven't mentioned a CNAME record for the subdomain. You need a DNS record like this for the subdomain to work:
www CNAME ghs.googlehosted.com
I've assumed that www is you subdomain but you would use your subdomain if different.
I added a custom domain to point to one of my Google App Engine Projects. It has been approximately 18 hours since I made this change.
How long does it take for DNS changes to propagate. After 18 hours when I hit the domain, I still get "Site can't be reached" on Chrome.
ping: cannot resolve: Unknown host, when I do a ping.
UPDATE: I figured out the issue. I bought the domain uisng Google Domains. It seemed like Google App engine settings, where I added, custom domain was going to update A records in Google Domains for my domain. It didn't. Created A records in Google Domains, and now it works fine. My domain, and subdomain are pointing to a project in Google App engine.
At the bottom of the Add a new custom domain screen from the GAE App's Custom Domains page in the developer console you can see:
DNS changes can require up to 24 hours to take effect
A snapshot of that screen is illustrated at step 5 of the Adding a custom domain for your application procedure.
Side note: maybe it's also worth re-checking the updated settings, it actually happened to me once - I was waiting (in vain) for DNS propagation only to notice that the changes I thought I completed weren't there - I must have missed an ok/confirm button or something...
If the settings are there you could also try checking using some network other than your usual internet provider (which often is involved in the DNS propagation). Mobile/office maybe?
You can also try some online DNS lookup tools or even website verification tools - often propagation to such servers is faster than to end-user internet providers. It doesn't matter if the app is not up, all you want to see if they're able to get the IP address for your domain. If any of them can get an address then it's really just a matter of time.
I had two custom domains on my setup. Now one is not there, the domain in question, www.emlakair.com is still working and pointing to the app engine code, but missing from the developers console. The other domain is www.catchamove.com. This is working also and visible under custom domains.
I have not done anything with the custom domains since they have been working so no changes on my part there. However, I have recently setup an account on with Google's search console and both the same domains are listing on there. My domain settings remain unchanged since verification of the domain first time around and everything seems fine that end.
Does anyone have a clue, I could try to re-verify the missing domain but that will mean changing the CNAME record and that will take the domain down for a while.
Here is the CNAME record data:
Can anyone from Google or anyone else for that matter explain this or provide a solution.
Thanks
Ok, I just had to re-verify again. But why? It would be nice to get some answers as to why a custom domain falls of the face of the map without explanation, yet still manages to point to the app engine project code no problem?
However, there is one anomaly still remaining and that is the other custom domain www.catchamove.com is showing A and AAA records on the developers console, but www.catchamove.com is setup with a CNAME record on my DNS management system, but it is working at the moment.
When will SSL support for custom domain be available within the developer console, instead of having to go over to Google Apps? I read somewhere it says Q3 of 2015. But seems like people have some ways of getting that to work already. Is it a private beta feature?
Building some apps for a client and they can't get their Google Apps account to work and we already have the custom sub-domain mapped to the GAE, and just need the last piece. Help!
This is the tracking issue, indeed Q3 seems to be more likely: https://code.google.com/p/googleappengine/issues/detail?id=10794
FWIW, I detailed a bit my solution to get things working via Google Apps in this Q&A: AppEngine subdomains to modules without wildcard mapping, maybe it can help with your customer's problems in the meantime.
A few months ago I posted this question because I tried to follow all of the Google instructions, perfectly, for setting up a domain with your Google App Engine application.
I still couldn't get my new domain (purchased through Google) to work properly. After a bit of triple checking in my Google Apps account and DNS setting tweaks (with the ENOM registrar which Google uses), I gave up and figured I'd just wait a few days to see what happened.
Surprise, after a few days my domain started to work without any problems and I've begun to wonder if the problem was that it takes Google a bit of time to get everything setup on there end.
Today, I've once again published an App Engine application and went through the process of purchasing a domain through Google and setting it up in Google Apps. After following Googles instructions, going to my new domain points to a generic welcome page (seen here.)
I have a hunch that I've setup my web site correctly and I should probably just be patient. However, I've never seen Google documentation stating that the setup may take a while, so I'm still a wee bit skeptical.
How long should I have to wait for my domain, Apps site and App Engine application to be fully setup and functional against my new domain?
When you register your new Domain name, the new Domain will typically take between 24 to 96 hours to propagate.
Once the Domain is propagated, you can setup your Google App Engine application in few minutes.
Usually you will need to tweak the DNS of your Domain for a couple of operations that does not require more than 10 minutes of work:
TXT record creation to allow Google to verify you own that Domain
CNAME record creation to map your App engine application to the new registered Domain