As of 22:00 UTC yesterday (2013-11-15) our servers suddenly started getting "Unknown authorization header" failures when connecting to Google Calendar API (V2) via OAuth.
The problem seems completely intermittent. Right now we retry after each failure twice (with a four second delay each time) and approximately 10% of these retries succeed.
I saw on this page that Google engineers monitor this tag on stackoverflow. If that is you - please help! My service is suffering and our customers are losing business. Please help me convince them they were right to bet on us and Google Calendar!
I managed to get in touch with a Google SRE. They have since diagnosed the issue and they are pushing a fix now. Should be fixed sometime in the next few hours, I'm told.
The fix has been pushed and I just did a test confirming everything is working fine now. Hopefully you are good to go as well.
Related
Well like the title suggest I am having a strange problem with the api oauth2.0 I wanted to play with the API in the sandbox before deploying live like any sane person to start pulling call recordings. Well when I was setting up the Oauth and it was a pain but I got to work, or at least I thought until it asked me to add an address for the sandbox profile after accepting all the other steps in order to go any father. Every time I tried to add the address from the zapier login window it kept telling me it failed to try again later. I thought no big deal I will just add it from the user profile and well what do you know that didn't work either. I than made a new extension with a new number and email to see if it was just the account that was messed up, or if the dev account couldn't use the api for whatever reason but again no dice same problems all the way down. I even tried using three different browser to see if anything would change but no dice (not like that really matters everything is chrome based these days). I am wondering if anyone else has had this problem, did I miss something really simple that I am clearly over looking since I am running on 4 hours of sleep for the last two days.
If anyone could help I would appreciate it, love a very tired programmer.
In case anyone runs into the same problems, make sure when making a POST request to ring central you put the paramotors in the body of the request.
I can't login to iTunes.connect anymore. It delivers an empty white page since the whole day now. There is no 401 and no 404, just plain html that renders an empty page:
https://www.youtube.com/watch?v=UhIy6OeaBZY&feature=youtu.be
My friends can log into itunes connect and see the real page, but not me.
I tried different browsers, cleared cache and everything else.
What to do now? Apple isn't interested in this issue because it works for lot of people apparently....
I don't think there is anything you can do about it on your end, but I wouldn't panic. I believe it may be traffic and/or account related. We have it happen every now and then and usually after a couple of hours things are back to normal. Should the issue persist, I absolutely would contact Apple regarding it though.
As #Ramsay also commented, some more people had this issue yesterday...
How i ended up with this: i switched the network to 3G UMTS where everything worked fine.
Then I disconnected the router for a while to achieve an IP-address-change from my provider for my office. But iTunes.Connect then worked only in incognito mode, so i had to clear browser cache with cookies again. Now it works.
Apparently iTunes.Connect had some serious issues in general. The processing-state for a new release in the internal-testing-phase of Testflight took more than 5 hours yesterday. Usually 10 minutes where enough to process.
Tried logging into Web UI to run some queries this AM, UI never loads.
https://bigquery.cloud.google.com/welcome
Anyone else experiencing this?
Yep. Same issue... Logged out, logged back in. Tried in incognito. Nothing seems to work. Probably a system outage at G.
I believe that you may be affected by a known issue. This is a high priority issue that Google is working to resolve as soon as possible. Here are some details about the issue:
Description:
We are currently investigating an issue with Authentication services.
Next update will be provided an update at 7:30 PDT.
I found a lot of posts about this issue, but none is like mine.
I have a website that subscribes to IG real-time updates. Since some time ago trying to subscribe to new notifications returns the above error. Seems like IG can't reach the callback_url.
Interesting findings while troubleshooting:
I tried to manually (directly) access the callback_url and it works flawlessly.
When I run the site on my local machine and make sure the callback_url is to my server + the verify_token is a valid one then it all works as it should! IG reaches the callback_url.
I used the apigee console to make the subscription request and there it sometimes works.. Meaning - I craft the request to IG API and click Send. If it fails then I click again (I don't change parameters) and then it works..
Web server logs are in line with the results I get (when it complains it can't reach then there's no log of a request).
Does anyone have any tip or suggestion how to fix this?
Thanks!
While chasing my own tail for a solution I also contacted IG support. I described the issue using same description as above.
After 2 weeks suddenly everything started working again. Magic! Suddenly no errors at all! Needless to say nothing has changed on my end (hardware / network / code).
I didn't receive any response from their support, but considering that a previous email to them a few months ago took about 2 weeks to answer then I am quite sure some support guy simply fixed the issue on their side and didn't even bother to let me know what was going on.
This could be related to the fact that they killed most of their real time notifications API.
Anyway, leaving this here so that if anyone encounters a similar issue then just know you may need to email IG support.
I was using Instagram realtime API for some time and everything was working fine. I have only one subscription on users.
Lately it started to behave totally strange. I'm not getting all of the content, and there's no way to find any pattern. Every request triggers a log right when it hits my server so I can tell whether or not Instagram notifies me about the new content pretty accurately.
I'm starting to suspect that rate-limit is causing this problems. Does anybody knows if there's some rate-limit that can cause that behavior? Did anybody else have similar problems with the Instagram real-rime API ?
There is a rate limit of 5000/post/hour [BY experience and best of my knowledge]
However Instagram is very good in explaining the root cause so, if you see the error message it would clearly say "RateLimitExceeded" or what ever the root cause may be.