I am calling this API
"URL: https://api.lyft.com/v1/rides?start_time=2016-01-01T00:00:01%2B00%3A00&limit=50, Header: {"Authorization"=>"Bearer tJVICf23213p1k2ksdjskadsd0KMuOVgWsdkc7rGs4g/WNKreAFqK4EroFDwj/sdjljas_dlkjasdksdfdf="}"
I get correct responses for all the users except 2.
In ruby, this is my code to call the lyft dev api
response = RestClient::Request.execute(method: :get, url: url, headers: header)
It just goes inside the rescue and gives either 504 gateway timeout. Earlier, it used to give 500 internal server error.
Also, the access tokens get renewed successfully. No issue with that.
Any kind of help will be appreciated here. Thanks in advance.
I found an answer to the issue.
We were using max limit of getting 50 rides of the user. Lyft server was giving 504 gateway timeout because it was not able to process the number of trips. We changed the max limit to 20 and it worked without any issues.
Related
Trying to make call from my app to a number using Twilio API's
When call is received, getting application error
and here is the debugger logs for that call:
Error - 11200 HTTP retrieval failure 502 Bad Gateway errors
Passing a URL when POST Request.
Can anybody help me through this?
have you taken a look at this information from Twilio? They give possible causes and possible solutions for the error you received. Did you specify the correct content-type header in your response?
If you could share your code, that would be great!
Hope this helps!
I've got a bot up and running, most of the time it is working ok, but Twilio throws some 500 and 502 errors on every inbound SMS.
An attempt to retrieve content from https://sms.botframework.com/api/sms returned the HTTP status code 500.
or
An attempt to retrieve content from https://sms.botframework.com/api/sms returned the HTTP status code 502.
The 502 requests continue fine and responses are sent, but the 500s do not - the user doesn't get a response.
How can i get logging from the sms.botframework.com service to see what's going on? No errors are showing on the azure side for my bot.
Thank you
Right now the Bot Framework isn't set up for you to be able to get to the logs inside our SMS connector; the 502's are benign, but the 500's aren't something I normally see. If you wish, you can contact me with your botid at bf-reports#microsoft.com and I'll take a look, or DM me on twitter (#jameslew).
#Philnash happy to fill you in more on the BotFramework and how developers can use it with Twilio; just let us know how to contact you.
I am having an intermittent issue with Twilio. Once out of every 50 or 75 calls, we get a call that fails, and when I check the logs, it states that it is error 11200, and it gives a Bad Gateway 502 message "An upstream server received an invalid response".
I've taken a look at Twilio's suggestions regarding this error (found at https://www.twilio.com/docs/errors/11200). They list a bunch of probable causes for a bad gateway error:
1) Web server returned a 4xx or 5xx HTTP response to Twilio - as far as I can see in the logs, the web server is returning a 200 HTTP response to Twilio.
2) Misconfigured Web Server - We have checked the configuration of our web server, and believe it to be correct.
3) Network disruptions between Twilio and your web server - we have tested the ping response time, and the packet loss between www.twilio.com and our server. The ping time is < 100ms, and there seems to be no packet loss when testing with ping -n 100 www.twilio.com
4) No Content-Type header attached to response - we set our Content-Type to application/xml.
5) Content-Type doesn't match actual content - We set our Content-Type to application/xml and are using the TwiML language to send our responses back.
We have also checked all elements in Twilio's Possible Solutions section for this error.
A bit about what we are doing:
API Version: 2008-08-01
We only make outgoing calls.
We use TwiML to send a Say command, followed by a Gather. It is during the Gather that we get our intermittent error. The user will press a key, which gets sent back to us. Depending on which key is pressed, we then send another Say to Twilio - for example "You pressed 1. This offer has been accepted. Thank you." or "You pressed 2. This offer has been declined. Thank you."
I'm not ruling out that it's something at our end that is causing the issue, but we don't really know what to check next. The web server appears to be sending a 200 response back, but Twilio seems to be receiving a 502.
Does anybody have any suggestions that might help us out? Could it be a problem with the API we are using? Should we be upgrading to 2010-04-01?
Thank you in advance!
When creating a new Client ID for OAuth 2.0, I got a message "An error has occurred. Please retry later.". I tried several times this week without success. But I am user with the role owner and I created successfully a Client ID last month with the same user.
Besides, by checking the requests and responses sent with the Chrome Developer Tools, I can notice that I get a 500 error for https://console.developers.google.com/m/project/my_project/client/web/create?xsrf=qwerty
Is there something wrong at Google or it's me ?
Yes, the problem is in the Request you are sending and the Response is an Error response. So if you want to identify the exact error, I suggest if you are passing credentials, double check it once; it might have changed or upgraded.
Hi i am trying to collect data from twitter search Api using Twitter4j. Every thing is working fine but after certain no. of calls to the Api it is throwing the following error.
403:The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following).
message - Missing or invalid url parameter
code - 195
Using thread.sleep i am calling Api every 1 min. so at the max it can have 60 calls. But the limit is 350 with authentication, then also i am getting this error.
Please help me out i am very new to this. Thanks in advance.
What are you sending in the DM. From now on it seems that if your message contains an URL the DM will be rejected:
https://support.twitter.com/articles/14606-posting-or-deleting-direct-messages