Open maria-pro opened 5 years ago
It started happening with me too. The interesting in it is that a few hours before the same script worked totally fine and then all of a sudden I get the HTTP failure: 403. I genuinely have no idea, why.
Getting same 403 error. :(
It is curious because after putting it to rest yesterday, today it worked again for 3 calls - and then the HTTP failure: 403 came again.
So I figured out, why this is happening. If you exceed your daily quota limit, you get this HTTP failure 403. However, the daily quota resets itself every day (midnight, pacific time). You can calculate your quota with a quota calculator here: https://developers.google.com/youtube/v3/determine_quota_cost and you can check your past API requests in your google console dashboard. cheers
I get the same error when requesting and it is not due to the daily request quota. It generally doesn't work anymore. Worked smoothly for a long time. Recently but not any more. What could be the reason?
Tansania_coments <- get_all_comments(video_id = "J4wf02KbZRA")
Returns: "Error: HTTP failure: 403"
I am now having the same issue with "get_all_channel_stats()." It is not due to the daily quota, as I haven't used it in the past 2 days.
I installed tuber today. I really enjoyed its functions. However, now all returns are "Error: HTTP failure: 403". Why?
I also tried use
library(devtools);
devtools::install_github("soodoku/tuber", build_vignettes = TRUE)`
but the error remains.
I get the same error when requesting and it is not due to the daily request quota. It generally doesn't work anymore. Worked smoothly for a long time. Recently but not any more. What could be the reason?
Perhaps you used all of your daily quota. It is possible to use 10000 queries per day. You can solicite more quotes send a request for Youtube.
I constantly get the 403 error after ~4,5 queries, each of which return around 600 results. That is not even close to the limit.
What works for me as a temporary fix is to remove the .httr-oauth file that caches login data, restart R, and then log back in with the same credentials. Sometimes I have to wait for some time in between queries. Not sure if this error is coming from the Google API for some reason or other, or if it has to do with the package, but it makes working with tuber incredibly tedious.
Hi, I'm having the same problem. I managed to auth, but couldn't get stats on a list of video that I had already done before. Is somebody having the same issue?
Can you please post a reprex
@muschellij2 There is literally no need for a reprex in this case. the error is called after authentication with even the documentation examples. Use the documentation itself as a reprex.
Here, since you're giving a thumbs down for a factual statement regarding your request for a reprex:
app_id <- "myuniqueappidthatIwillnotposthere" app_secret <- "myappsecretthatIwillnotposthere" yt_oauth(app_id = app_id, app_secret = app_secret, token = "")
tuber::yt_search(term = "Barack Obama")
Error: HTTP failure: 403 The request cannot be completed because you have exceeded your quota.
I have not used this function for over a month, and since I tried it 2 days ago, it has not worked once. So there is no way I have gone over my available quota. Yesterday it just said "Erro 403", now it is giving a different error, but still the same lack of results.
1) this is a non-funded project for me, so respect developer's time if you want a response in the future. You are clearly not a developer. 2) Please read what an MCVE is because that clearly is not one.
I had the same issue. I had to start a new project because I believe there are issues with quotas for youtube API limits because of the changes to the API over time. Please start a new GCP project, enable YouTube APIs and then retry.
Go to https://console.cloud.google.com/iam-admin/quotas and ensure that all are in green:
and check each one to make sure none are at zero.
Made multiple new Oauths, and a new project with a new one, tested all of them, all say within quota limit. Still the problem persists --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168
On Wednesday, December 30, 2020, 10:21:01 p.m. GMT+7, John Muschelli <notifications@github.com> wrote:
I had the same issue. I had to start a new project because I believe there are issues with quotas for youtube API limits because of the changes to the API over time. Please start a new GCP project, enable YouTube APIs and then retry.
Go to https://console.cloud.google.com/iam-admin/quotas and ensure that all are in green:
and check each one to make sure none are at zero.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Can you try a service account with desktop client and download the json file and try that?
On Wed, Dec 30, 2020 at 11:53 AM R J Gray notifications@github.com wrote:
Made multiple new Oauths, and a new project with a new one, tested all of them, all say within quota limit. Still the problem persists --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168 https://www.google.com/maps/search/705+alligator+ranch+rd.+New+Smyrna+Beach,+FL,+USA.+32168?entry=gmail&source=g
On Wednesday, December 30, 2020, 10:21:01 p.m. GMT+7, John Muschelli < notifications@github.com> wrote:
I had the same issue. I had to start a new project because I believe there are issues with quotas for youtube API limits because of the changes to the API over time. Please start a new GCP project, enable YouTube APIs and then retry.
Go to https://console.cloud.google.com/iam-admin/quotas and ensure that all are in green:
and check each one to make sure none are at zero.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-752688383, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIGPLR4LOAESMWHHNACEHDSXNLHJANCNFSM4GMTA3FQ .
-- Best, John
I don't know how to do that. Is this package working on your end?? --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168
On Thursday, December 31, 2020, 02:05:59 a.m. GMT+7, John Muschelli <notifications@github.com> wrote:
Can you try a service account with desktop client and download the json file and try that?
On Wed, Dec 30, 2020 at 11:53 AM R J Gray notifications@github.com wrote:
Made multiple new Oauths, and a new project with a new one, tested all of them, all say within quota limit. Still the problem persists --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168 https://www.google.com/maps/search/705+alligator+ranch+rd.+New+Smyrna+Beach,+FL,+USA.+32168?entry=gmail&source=g
On Wednesday, December 30, 2020, 10:21:01 p.m. GMT+7, John Muschelli < notifications@github.com> wrote:
I had the same issue. I had to start a new project because I believe there are issues with quotas for youtube API limits because of the changes to the API over time. Please start a new GCP project, enable YouTube APIs and then retry.
Go to https://console.cloud.google.com/iam-admin/quotas and ensure that all are in green:
and check each one to make sure none are at zero.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-752688383, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIGPLR4LOAESMWHHNACEHDSXNLHJANCNFSM4GMTA3FQ .
-- Best, John
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Yes it is. Again, I had to 1) make a new project (not new key), then 2) enable YouTube APIs and 3) I had to make a new credential, in the same way inidcated as https://gargle.r-lib.org/articles/get-api-credentials.html#oauth-client-id-and-secret Best, John
On Fri, Jan 1, 2021 at 11:09 PM R J Gray notifications@github.com wrote:
I don't know how to do that. Is this package working on your end?? --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168
On Thursday, December 31, 2020, 02:05:59 a.m. GMT+7, John Muschelli < notifications@github.com> wrote:
Can you try a service account with desktop client and download the json file and try that?
On Wed, Dec 30, 2020 at 11:53 AM R J Gray notifications@github.com wrote:
Made multiple new Oauths, and a new project with a new one, tested all of them, all say within quota limit. Still the problem persists --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168 < https://www.google.com/maps/search/705+alligator+ranch+rd.+New+Smyrna+Beach,+FL,+USA.+32168?entry=gmail&source=g
On Wednesday, December 30, 2020, 10:21:01 p.m. GMT+7, John Muschelli < notifications@github.com> wrote:
I had the same issue. I had to start a new project because I believe there are issues with quotas for youtube API limits because of the changes to the API over time. Please start a new GCP project, enable YouTube APIs and then retry.
Go to https://console.cloud.google.com/iam-admin/quotas and ensure that all are in green:
and check each one to make sure none are at zero.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-752688383, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAIGPLR4LOAESMWHHNACEHDSXNLHJANCNFSM4GMTA3FQ
.
-- Best, John
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-753428469, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIGPLROB5TDSRRP7DO3V73SX2L7DANCNFSM4GMTA3FQ .
Hi again John, I did make a new project (not a new key), enabled Youtube API (while making sure it didn't say I had reached a quota limit for any reason) and made new oauth credentials. This still doesn't work. I have also tried this on a different google account, and I have also had several of my colleagues make one for themselves (for the first time, never having used Youtube API before), and the exact same thing happens to them too. --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168
On Monday, January 4, 2021, 05:57:44 a.m. GMT+7, John Muschelli <notifications@github.com> wrote:
Yes it is. Again, I had to 1) make a new project (not new key), then 2) enable YouTube APIs and 3) I had to make a new credential, in the same way inidcated as https://gargle.r-lib.org/articles/get-api-credentials.html#oauth-client-id-and-secret Best, John
On Fri, Jan 1, 2021 at 11:09 PM R J Gray notifications@github.com wrote:
I don't know how to do that. Is this package working on your end?? --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168
On Thursday, December 31, 2020, 02:05:59 a.m. GMT+7, John Muschelli < notifications@github.com> wrote:
Can you try a service account with desktop client and download the json file and try that?
On Wed, Dec 30, 2020 at 11:53 AM R J Gray notifications@github.com wrote:
Made multiple new Oauths, and a new project with a new one, tested all of them, all say within quota limit. Still the problem persists --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168 < https://www.google.com/maps/search/705+alligator+ranch+rd.+New+Smyrna+Beach,+FL,+USA.+32168?entry=gmail&source=g
On Wednesday, December 30, 2020, 10:21:01 p.m. GMT+7, John Muschelli < notifications@github.com> wrote:
I had the same issue. I had to start a new project because I believe there are issues with quotas for youtube API limits because of the changes to the API over time. Please start a new GCP project, enable YouTube APIs and then retry.
Go to https://console.cloud.google.com/iam-admin/quotas and ensure that all are in green:
and check each one to make sure none are at zero.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-752688383, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAIGPLR4LOAESMWHHNACEHDSXNLHJANCNFSM4GMTA3FQ
.
-- Best, John
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-753428469, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIGPLROB5TDSRRP7DO3V73SX2L7DANCNFSM4GMTA3FQ .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
One last thing to check - you used the json file, correct? Something like (where json is your json file for desktop app): app = gargle::oauth_app_from_json(json) yt_oauth(app_id = app$key, app_secret = app$secret) At this point, I don't know how to resolve this - I think @soodoku might have to address this (I'm not the maintainer). Best, John
On Sun, Jan 3, 2021 at 9:13 PM R J Gray notifications@github.com wrote:
Hi again John, I did make a new project (not a new key), enabled Youtube API (while making sure it didn't say I had reached a quota limit for any reason) and made new oauth credentials. This still doesn't work. I have also tried this on a different google account, and I have also had several of my colleagues make one for themselves (for the first time, never having used Youtube API before), and the exact same thing happens to them too. --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168
On Monday, January 4, 2021, 05:57:44 a.m. GMT+7, John Muschelli < notifications@github.com> wrote:
Yes it is. Again, I had to 1) make a new project (not new key), then 2) enable YouTube APIs and 3) I had to make a new credential, in the same way inidcated as
https://gargle.r-lib.org/articles/get-api-credentials.html#oauth-client-id-and-secret Best, John
On Fri, Jan 1, 2021 at 11:09 PM R J Gray notifications@github.com wrote:
I don't know how to do that. Is this package working on your end?? --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168
On Thursday, December 31, 2020, 02:05:59 a.m. GMT+7, John Muschelli < notifications@github.com> wrote:
Can you try a service account with desktop client and download the json file and try that?
On Wed, Dec 30, 2020 at 11:53 AM R J Gray notifications@github.com wrote:
Made multiple new Oauths, and a new project with a new one, tested all of them, all say within quota limit. Still the problem persists --Russell J. Gray Wildlife Ecology & Conservation Consultant |
0934581341 | rjgrayecology@gmail.comhttps://www.rjgrayecology.com/ 705 alligator ranch rd. New Smyrna Beach, FL, USA. 32168 <
On Wednesday, December 30, 2020, 10:21:01 p.m. GMT+7, John Muschelli < notifications@github.com> wrote:
I had the same issue. I had to start a new project because I believe there are issues with quotas for youtube API limits because of the changes to the API over time. Please start a new GCP project, enable YouTube APIs and then retry.
Go to https://console.cloud.google.com/iam-admin/quotas and ensure that all are in green:
and check each one to make sure none are at zero.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-752688383, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AAIGPLR4LOAESMWHHNACEHDSXNLHJANCNFSM4GMTA3FQ
.
-- Best, John
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-753428469, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAIGPLROB5TDSRRP7DO3V73SX2L7DANCNFSM4GMTA3FQ
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/soodoku/tuber/issues/66#issuecomment-753721815, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIGPLXNY2XIEPRZRQFARULSYEP4NANCNFSM4GMTA3FQ .
Tried your suggestion and this also didn't work.
I just ran a query using the API key with vosomSML and it worked without issue. So I have narrowed the issue down to using the API oauth with app id and app secret. I have deleted my projects and started new ones with new app_id and app_secret, I have checked the limits and they're fine. I have done literally everything I can think of and nothing has worked.
I guess I will have to wait for @soodoku to respond
I was having this same problem, and it was due to hitting quota limits instantaneously. I think it is related to this:
Creating a new project didn't work on its own -- I also had to shut down my inactive project. Hopefully that works for someone else.
Hi, does anyone have a follow-up on this? I have been trying to collect data, but I always get a 403, even after deleting and creating again the apps. For the solutions proposed here, we don't seem to have it fixed.
@lucasdedavid En este link comento lo que creo que es la razón del error: https://github.com/soodoku/tuber/issues/15
Me parece que por cambio de política de youtube la cuota definida está en 0.
Para aumentarla parece que es necesario asociar una cuenta de Facturación.
Aprecio que lo puedan confirmar.
I also experienced the same issue, even though quota was definetely not reached. One thing I discovered that seems to solve the issue (at least for me) was to not scrape bigger amounts of data at once, and more importantly, not too frequent.
If you take a look at your google dashboard for the app you are using, you can observe the traffic you are causing. I assume if you reach a traffic cap, google blocks you until the quota is resetted. My advice therefore would be to download data by (small) waves. You can do this manually or by implenting "sys.sleep()" before your scrape-commands.
i am able to pass authentication with yt_oauth but when I try to do get_channel_stats or list_channel_resources it returns: "Error: HTTP failure: 403"
get_channel_stats(channel_id="UCMtFAi84ehTSYSE9XoHefig")
Can you help? ty