I made this URL public a few years ago as a way to retrieve data. It was working yesterday. Today my site is crashing as it relies on this data, but google is now returning a 500 error if I try to retrieve it programmatically (through axios).
https://spreadsheets.google.com/feeds/list/1DLAVN3q758sPohCFeZlVSVRZKXzEser1SIsQnH2mvrw/ogwtdyp/public/basic?hl=en_US&alt=json
I have also created a code sandobox with react to demonstrate: https://codesandbox.io/embed/xjmy9vl2z4
However, I am still able to view the response in the browser if I am logged in.
Did google recently change their API so that it is no longer possible to retrieve data this way? Is there a way to configure my axios request in such a way to continue retrieving this data?
UPDATE:
Issue is being tracked here: https://issuetracker.google.com/issues/131613284
According to the support team: "The engineering team believes they have located the source of the problem and are rolling back to a previous build in order to resolve issue. Please stand by."
https://issuetracker.google.com/issues/131613284#comment109
UPDATE:
It seems like the issue has been resolved by rolling back to a previous build. I am no longer experiencing these issues. The link above, and the code sandbox example are both functioning. Reading the forum, it seems like others are also no longer experiencing issues. If you are still experiencing issues, I would encourage opening another (perhaps more specific) post or issue.
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.
Many of our users are reporting that they are getting a blank page when using IE11 to access our website. Sometimes they don't even get a blank page, the browser just stays on the last page visited. These users can access other domains (such as google.com) without a problem.
For the browsers that are failing, if those users disable Protected Mode in IE, then they can again access our site, but this isn't a good solution because we have thousands of users and we can't go telling each of them to reconfigure their browsers, not to mention that we're completely losing the business of those potential customers who just surf by, see a blank page, and then keep on going without filing an error report.
Firefox and Chrome work fine. Also, even when using IE11 in protected mode, some users have zero problem, their computers just seem to work.
We are running the site off of IIS7. Other sites on the same server run fine, it's just the one particular site that is having the problem, and it's intermittent, affecting some computers and not others.
There must be something I can do on my side in the server or network settings to keep this problem from happening, but I'm baffled as to what it might be. When I look at the network traffic on a browser that's failing, the GET request is just being aborted with no explanation. When looking at the traffic with Wireshark, I see no errors, and no errors are showing up in the IIS logs. Of the browsers that fail, they are not even opening a connection to our web server to make a GET request, the request is just aborting immediately.
Any advice appreciated!
(followup): Another test we did: We can reproduce the problem on our development server, with the same pattern of which computers "work" and which don't. We tried turning off the webserver, and the problem stayed consistent, we'd still get a blank page error. So it's obviously not to do with anything that's in our page content? I've run tests on 9 computers on our office network: 5 worked, 4 failed. We're all baffled. :/
(January 24 followup): We figured out what's causing the problem, but not how to fix yet. Deep in the Windows registry, a key is being set in a Zonemap folder, adding a "play.net" domain with a key value of 2. IE sees that key when someone types play.net, and quivers and dies without an error message (Firefox and Chrome handle it fine).
So next question, what is setting that key in the first place? Probably an ActiveX control somewhere, but we haven't had any luck finding it in this 15 year old site, as many of the coders who may have created ActiveX controls in the past are long gone.
Does anyone know of a way to scan an entire domain and list anything that might be twiddling a registry key?
Followup mail threads from Elonka indicated that some users had the play.net domain mapped to a specific / non-default Internet Explorer security zone, and those users were the ones having problems.
Try add
<meta http-equiv="X-UA-Compatible" content="IE=10" />
into the header. It fixed IE11 for my website. It just forces it into IE10 mode (A complete joke though)
I accessed your domain in Internet Explorer 11, with Protected Mode enabled. I was unable to get a fully broken experience, but I did see something perhaps related to what your customers are experiencing. Some directories on your domain would hang for me, resulting in a white screen if they've not yet been loaded, or staying on the present page while the forthcoming page is loaded.
When I navigated to /dr, I found that my browser hung for over 7 seconds while your files loaded. Note, there were roughly 60 items, totaling about .78mb. This isn't much, but I'm presently on a relatively slow connection, and this resulted in a hang for me.
I would inquire what connection speeds your clients are on when experiencing this issue - it could very well be nothing more than some directories being served up more slowly than others. Regardless, you could optimize the experience considerably by compressing and concatenating your CSS files, as well as all of your JavaScript files. This results in fewer parallel requests, and quicker downloads.
If you have a reproducible example, please feel free to share and I'm sure myself and many others here will be more than happy to assist you.
For me box-shadow on an element caused this behavior. I removed the box-shadow(but left -webkit-box-shadow and -moz-box-shadow) and the problem disappeared. The interesting thing is that I still have box-shadow on another element...
If you are using 'offline.js' in your project, and you have version less than 0.7.19, then IE11 latest security update will see this code as potential security threat and block pages which are using 'offline.js' code.
Solution: Update to latest 'offline.js' version.
Whenever I try to set a root password I get a message saying "Instance busy".
How can I then set a password for the instance? Is there a third party tool I can use to connect to the cloud-sql instance and maybe set a password from there?
I have found no resolve, and the issue persists.
However, if you remove the IP address to the instance periodically, there should be no way of accessing it outside the internal app engines code.
This bug is still a big security concern though.
Using the new console, try waiting for a good length of time if you haven't already, as that message eventually went away for me
Once I set the password I just used MySQL Workbench to connect, and it was all copacetic.
Background:
I just set up my Cloud SQL this week, and in the Developers Console under Access Control and I had the same problem at first, in the small yellow box "Instance Busy".
My solution was to clear my cache on Chrome (I recommend using Chrome with Google UIs as it rules out any funky incompatibility with AngularJS), I saw the error message again after I went back, waited a while (maybe 30 seconds) and it went away, I then assigned an IP address and it came back, again for a while and eventually went away and I was able to set the password then.
Hopefully this answer was helpful (and it works for you; although not guaranteed I thought I would offer it as an answer as my experience was very similar).