2

I'm developing a Node.JS app. When running on localhost everything works fine.

After I've deployed it to AppFog, I randomly get 503 Service Unavailable responses either for static resources (served using express.static() middleware, Express is version 3.1.0), or API calls (serving JSON documents from MongoDB). Also in AppFog console I see reported status 0%. Application logs show nothing. And it seems the applications does not stop.

I tried running single instance with 2GB of memory as well as 16 instances each with 128MB still getting 503.

Application is deployed to US East infra. It uses MongoHQ add-on.

Have you experienced this behavior on AppFog or with your Node.JS apps? Thanks for any help.

Jakub Kulhan
  • 1,572
  • 2
  • 16
  • 37
  • 2
    You need to contact support , directly , and remember , APPFOG still is a beta service. – mpm Mar 05 '13 at 19:09
  • @mpm I also wrote to AppFog Google Group. AppFog's support suggested to restart the app. It did not help. So I wanted to know if anyone else has experienced this. – Jakub Kulhan Mar 06 '13 at 15:39
  • hi @JakubKulhan! i've deployed a rails app on appfog and i have the same 503 errors like you, especially with https. – mathieurip Mar 13 '13 at 23:14
  • @mathieurip Seems like problem with AppFog's HTTPS. https://groups.google.com/forum/#!topic/appfog-users/qg8evGWtLnw – Jakub Kulhan Apr 17 '13 at 08:37

2 Answers2

1

Just a quick tip: you can use the command af logs <appname> to view your application logs.

James Wright
  • 3,000
  • 1
  • 18
  • 27
  • 2
    No one had suggested this, plus I posted a similar response to this question: http://stackoverflow.com/questions/13844376/on-appfog-how-to-find-the-reason-for-500-internal-server-error, as it didn't seem to be a well-known CLI option at the time. Want help in future? Drop the attitude. – James Wright May 17 '13 at 08:24
0

Bug with HTTPS in AppFog confirmed in their Google Group.

Jakub Kulhan
  • 1,572
  • 2
  • 16
  • 37