to Airbrake

Home → Problems →

<head><title>502 Bad Gateway</title></head>

geoffw8's Avatar

geoffw8

29 Jun, 2012 12:20 PM

Hey,

I'm not sure if you can see my account history, but I've brought this up before - we never receive errors. Strangely, it started working about 30 days ago and then stopped.

See below for something that we have a lot in our logs, /trends/feed/1.rss doesn't exist, and so it throws an error internally, but as you see your server isn't wanting to receive it and is spitting back an error.

Started GET "/trends/feed/1.rss" for 107.21.136.126 at Fri Jun 29 13:07:13 +0100 2012
 Processing by TrendsController#feed as RSS  Parameters: {"id"=>"1"} Completed 500 Internal Server Error in 11ms
[Hoptoad] Timeout while contacting the Hoptoad server. [Hoptoad] Environment Info: [Ruby: 1.8.7] [Rails: 3.1.0] [Env: production] [Hoptoad] Failure: NilClass [Hoptoad] Environment Info: [Ruby: 1.8.7] [Rails: 3.1.0] [Env: production] [Airbrake] Failure: Net::HTTPBadGateway [Airbrake] Environment Info: [Ruby: 1.8.7] [Rails: 3.1.0] [Env: production] ** [Airbrake] Response from Airbrake:
502 Bad Gateway

502 Bad Gateway

nginx/1.1.17


PLLLEEAAASEEEE help! Its such a nuisance that we aren't able to receive errors. I desperately need them!

Thanks very much in advance.

Regards,

Geoff

  1. Support Staff 2 Posted by Morgan on 29 Jun, 2012 06:18 PM

    Morgan's Avatar

    Hello Geoff,

    I am going to close this ticket out but keep a reference to the info in this ticket.
    Let's continue with this from your other ticket

    From,
    Morgan

  2. Morgan closed this discussion on 29 Jun, 2012 06:18 PM.

Comments are currently closed for this discussion. You can start a new one.

2 people watching.

  • New Issue

  • Conversation Started

  • The discussion is closed

    No more actions from Airbrake or the discussion starter are required.

  • Re-open the discussion

Recent Discussions

18 Jun, 2013 09:59 PM Timeouts
16 Jun, 2013 04:09 PM No subject
12 Jun, 2013 11:30 PM time zone for times in notifications
12 Jun, 2013 10:22 PM Some information on the occurrence of this error is still being processed and is not yet available. This data may not processed due to invalid XML. See the knowledge base for more information.
12 Jun, 2013 11:36 PM exception_message is undefined, js error in notifier.js

Recent Articles

Adding Assembla Integration
Alternate Plugins, Widgets, Addons and Extras
Gitblame
Jira integration common issues
Installing Airbrake gem