I shared a link with someone to a firebase site that I was hosting, and it worked for some time, but then all of a sudden they said they were getting the message:
We're sorry... ... but your computer or network may be sending
automated queries. To protect our users, we can't process your request
right now. See Google Help for more information.
I was also getting it, and started checking my other firebase hosted sites and started getting the message on all of them. I didn't understand. I couldn't find a common link to understand why it was happening. So many sites linked it to a reCAPTCHA problem, but my sites don't use reCAPTCHA...
I found this link:
GitHub forum Link
The user recommended making sure the url started with "https". As soon as I typed my url with "https://" at the start, everything came up. At that point, I tried all the other URLs, and they worked too. This may be a rule for all Google-related sites.
I'm not sure if it's relevant that Chrome often trims the url in the "omnibox" or address bar, hiding the protocol, making it easy to miss when copying/pasting? E.g. :
Note, I tried accessing these pages without https (by typing "http://") but my browser now seemed to correct it and force it to be "https://", so I couldn't replicate the problem again.
I don't know exactly why it started, but I know that I wish I found this information sooner, because it was very frustrating, and the info out there wasn't helpful, except for the link I posted above. So hopefully, when someone like me searches for "firebase" and the error text "your computer or network may be sending automated queries", they might see this and possibly be saved a headache.
Related
I have been working on an intranet site and recently users have been complaining that when they save a change they get "This site can’t be reached." The users are using Chrome exclusively as far as I can tell, and when I tested with Edge, I got no errors. So, I first tested on the web server, I was unable to recreate the issue. I tried on another server within the network and I was also unable to recreate the issue. I then tried my pc, which was connected through a VPN and was finally able to recreate the issue. What is weird is that this just started happening and I haven't updated the site in quite awhile. The can view most pages and the issue only seems to happen when posting to IIS. At this point, I am not sure where to start to troubleshoot this issue. Any help would be appreciated.
Edit: Updated the title to show the actual error I got.
Edit 2: Someone put me on to checking the httperr log and I see an error for the post request with client_reset as the error message. hope that makes the issue a bit more clear.
I found the issue with help from the network security firm the client was using. Once I was able to confirm the issue only occurred when clients who were using a VPN, he ran some tests. The issue was that the firewall was blocking posts that seemed suspicious. Now, this site has been running for years with no issues. My assumption is that they made some security changes and it caused this problem. What was odd, was that I tried a few fixes and they would work for a few times and then would stop working, such as using the site ip address versus the domain name. I hope this helps the next person.
Wade
I've just bought Paw and, while exploring the app found a mention of pawprints, which appear to be some sort of saved snippets or requests or something. I registered with the website and it tells me I have no saved pawprints. I've searched all over the help files and documentation and can't actually see how to create a pawprint, or even a clear definition of what a pawprint actually is.
So my questions are, what are pawprints and how do I use them?
Okay thanks Micha,
From the Blog Post (which Google couldn't find when I searched)
Last May, we launched Pawprint, a quick way to share the requests you tested in Paw. The idea of a getting a short link that you can paste anywhere, sharing what you just see on screen, was very appealing and something we wanted to do almost since the beginning of Paw.
That's handy to report bugs to the API provider (often those backend guys sitting on the other side of the room), or to show to the consumers (often the client folks playing with smartphones and web browsers) how your PATCH endpoint works.
In Paw, just hit ⌘/, and a permalink will be copied. Paste it anywhere from Slack and GitHub tickets, to StackOverflow answers.
You'll also get client code generated in many languages, plus cURL or HTTPie command lines, to run the same request from code.
Apparently the Paw website is being updated now to make this clearer.
http://api-public.netflix.com/catalog/titles/streaming
doesnt work anymore (it says inactive account). Is there a way to download full catalog? wanted to create app for my use.
Netflix shut down their developer program last year, which was the only way to get the proper credentials to sign a REST request URL and download the catalog... They are not going to be issuing any new developer keys, either. So, if you don't already have one, I am afraid you are out of luck.
If it is saying "account inactive" you are not authenticating your call--you cannot just paste that into a browser. There is a lot of information on the Netflix developer site about this here http://developer.netflix.com/page
I have the same question. I'm able to begin downloading the entire catalog, but due to the size it crashes my browser.
I started reading through this link (http://developer.netflix.com/forum/read/157154) but to be honest I don't really understand it.
Anyone care to enlighten me on how to set up a request, add Accept-Encoding headers, and then parse the output? Sorry for thread highjack...
Having the same issue, 401 for what used to work fine. Seems to be a Netflix issue, not sure what we can do.
I have an odd situation with a DEV site at work. Last week, our sys admin was experimenting with moving our DEV servers but didn't get chance to finish the job so rolled back his changes.
When I type in this URL http://mylocalsharepointsite/anypage.aspx then I get the page easily. However, when I change the protocol to https I first get a message warning me about the certificate, then when I click ignore warning I get a 404 error.
I know the site and pages are there because I go to IIS and can see the site, the directory it is mapped to and the SSL certificate, which since it's DEV we generated ourselves.
I suppose my question should be this, what are the things I should look at first, is there anything obvious I've overlooked.
The problem here was with IIS and the certificates. I re-generated the certificates, even though there didn't seem to be anything wrong with them.
This page helped me a lot, especially the two tools: SelfSSL and SSLDiag.
http://www.iis-aid.com/articles/how_to_guides/creating_self_signed_certificates_iis
I'm creating an ASP.NET application which uses Facebook Connect and fbml tags. It also uses the LinkedIn widget. When I run this app in any browser, there are no warnings and everything works. However, in IE, a message like this comes up:
Security Warning:
The current webpage is trying to open a site in your Trusted sites list. Do you want to allow this?
Current site:http://www.facebook.com
Trusted site:http://localhost
(same for LinkedIn.com). I know how to fix this from a client perspective and to stop the security warning showing up. However, is it possible to ensure this message doesn't come up as it could be off putting for users who don't know how to suppress this warning? I haven't tried uploading it to my webhost, so not sure if this message will appear for everyone in production. However, I always get it on my local machine.
(None of my pages use SSL, so I don't think that's the issue. I tried using FB's HTTPS urls but that didn't make a difference).
Thanks
I have come across the IE message many times. Whilst this might not be the case here I always check in Firebug to see if any requests are going to Https (using Net tab). If may be the case that something you are referencing is itself making a call to something else.
Often you get that message if you are serving an https page and then going to fetch an image over http.
Might not help but is the first thing I do in this situation.