New deployment isn't reflected on custom domain

[Patrick Prasquier]

I uploaded my site a few months ago and it is since deployed on my custom domain: http://viamotion.viadialog.com.br/

Today, I wanted to update the site and the new version was deployed on http://viamotion-br.appspot.com/ but my custom domain still shows the previous version.

1. Why? In this case, I'm not talking about DNS propagation since nothing has changed at the DNS setup level.

2. Going to the old GAE admin console (for some reason, I couldn't find this menu in the new one), no domain is listed in domain setup. I don't remember the process I went through when assigning my site to my custom domain but I'm pretty sure it should have been in this section (and my CNAME points to ghs.googlehosted.com.). I tried to add my domain (again) but once I get to the Google Apps Admin console and see that the domain viadialog.com.br is verified, I have no option to "push" it to GAE.

Thanks

[Nick (Cloud Platform Support)]

Hi Patrick,

This does indeed seem odd. While Google Groups isn't the best place to raise a specific technical issue or defect report (although we can't know for sure until we investigate), I'll be happy to help by asking some basic questions here and hopefully we can either figure it out together or you can move on to creating a thread in the public issue tracker, where defects are triaged, logged, and responded to with solutions.

So, the first idea which springs to mind is that somehow the new version is not the default version. You can check this in the Developers Console in your project, under "Compute > App Engine > Versions". 

The second thought which occurs to me is that since Custom Domains have moved into being purely set-up through the Developers' Console and webmaster tools, something may have changed or need alteration on your side. Could you provide a screenshot of what you see in "Compute > App Engine > Settings > Custom domains"?

Finally, are you the user who initially verified the domain, owns the domain, or attached it to the App?

With this information, it'll be more clear what's happening for your custom domain mapping.

Best wishes,

Nick

[Patrick Prasquier]

Hi Nick, 

I didn't know where "Custom domains" was located in the new console so I couldn't do it earlier. But now that I've found it, I confirmed that although my domain WAS attached to the account, the sub-domain wasn't defined. When I did define it, the new version of the site became immediately accessible. 

So, for me: problem solved. Now what remains a mystery (although I must say selfishly that I don't really care/need to know the answer) is why, if GAE was handling the sub-domain (although not reflecting it in the admin console) it pointed to an old version of the site... 

Thanks for your help. 

Best, 

Patrick

[Nick (Cloud Platform Support)]

Hi Patrick,

My best guess is that when you uploaded the new version of the site, you didn't update the "default version" in the "Compute > App Engine > Versions" interface, so the old version was still the default. When GAE receives a request to a subdomain and you've set up a wildcard subdomain mapping, it will check if the version/module exists. If it doesn't, it will route to the default version/module.

However, it's unclear to me what relation this might have to explicitly defining the subdomain, since it seems as though that would simply mean that your default version/module would be served from subdomain.domain.com...

Overall, since your issue is fixed, I wouldn't worry and consider this a strange edge case of the Custom Domains transition from Apps to Developers Console.

If anybody in future is able to observe similar behaviour and hasn't yet implemented the "fix", and by good luck lands in this thread, I'd advise them to open a public issue tracker issue and attempt to get the issue looked into by Support Engineers while it is still "live".

At any rate, best wishes for developing your app,

-- Nick