Labels

3G (1) 8600GT (1) AI (4) amazon (1) API (1) apple (3) apple mail (1) atlassian (1) audio (1) bambo (1) Bamboo (1) bloat (1) boost (1) bugbear (1) C++ (5) calling conventions (1) cdecl (1) chromecast (1) CI (1) compiler (1) continuous integration (1) coursera (1) custom domain (1) debugging (1) deltanine (1) diagnosis (1) diy (5) DLL (1) dns (1) don't be evil (1) ec2 (1) education (1) electronics (1) express checkout (1) fail (6) fink (1) firewire (1) free hosting (1) GAE (1) google (1) Google App Engine (4) H170 (1) hackerx (1) hackintosh (1) Haskell (3) homebrew (2) i1394 (1) icloud (2) iOS 9 (1) ipad2 (2) jobhunting (2) lag (1) letsencrypt (2) libjpeg (1) linux (1) mac (2) mbcs (1) mechanic (1) memory (1) MFC (3) Microsoft (1) migration (1) ML (1) mobile (1) movi (1) MSBuild (1) music (1) naked domain (1) NLP (2) o2 sensor (1) obd (1) Optiplex960 (1) osx (1) outlook express (1) payments (1) paypal (1) photos (2) PIL (1) Project Euler (1) projectmix (1) python (2) raspberrypi (3) recruitment (1) renwal (1) skylake (1) soundcloud (1) ssl (2) stdcall (1) stripe (1) subaru (2) supermemo (1) supermemo anki java (1) sync (2) Telstra (1) tests (1) thunderbird (1) udacity (1) unicode (1) Uniform Cost Search (1) university (1) upgrade (2) vodafail (1) vodafone (1) VS2010 (1) vs2013 (1) VS6.0 (1) weather (1) win (1) Win32 (1) Z170 (1)

Thursday 7 September 2017

Google App Engine... ready for prime time?

Google recently announced the availability of google cloud and google app engine in Australia. Since that's where my users are located I decided to migrate my Google App Engine application to the Australian availability zone.

Google don't make it particularly easy to do this, there is no button in the console to move your application, you must do the following manual steps:


  1. create a new application
  2. upload the code to the new application
  3. disable datastore writes on your existing application
  4. grant permissions to the bucket used to store your datastore backups so the new application can read them
  5. backup the data store of the existing application
  6. then restore the backups to the new application 
  7. then create a mapping of your custom domain to the new application
at this point, I tested my new application and I could see that google was serving the new application, so it looked like everything was working and I went to bed.

The next morning, my application was no longer working. It was configured to accept secure connections only, and when I remapped the custom domain, app engine decided to delete my certificate without telling me.

Well, that's not so bad, all I need to do is upload the ssl certificate to my new application, right?

Trouble is, app engine won't let me. Every time I try, it fails with an extremely unhelpful error message.


This seems to me to be some unexpected error in the backend, which is no surprise as the whole App Engine infrastructure is a little half baked. Turns out I had uploaded the wrong private key file, which I figured out by using a certificate checker site.



Sorry, there’s a problem. If you entered information, check it and try again. Otherwise, the problem might clear up on its own, so check back later.
Tracking Number: 6120870777002247692