Hi Looks like the problem was with the error_handlers directive (new in 1.3.6) I had used
error_handlers: - file: static/default_error.html Which also overlapped with a static file handler I had configured - url: /static static_dir: static expiration: "30d" Moving the static default handler to error_handlers: - file: default_error.html Made the problem go away. Ideally the deployment failure error should at least say "mis- configured app.yaml" or something similar. Regards Tim On Aug 18, 11:23 am, Tim Hoffman <[email protected]> wrote: > Hi > > Just trying to deploy a new version of my code base, and was able to > successfully deploy into a test instance I have. > When trying to deploy to my production instance I am repeatedly > getting the following error. > > Deploying new version. > Rolling back the update. > Error 400: --- begin server output --- > > Client Error (400) > The request is invalid for an unspecified reason. > --- end server output --- > > Which unfortunately is not very informative. There is nothing in the > admin logs. > > appid is q-tracker. > > Thanks > > Tim -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
