Ошибка rate limit exceeded - Решение и исправление самых разных ошибок на TopOshibok.ru

Cправка — Google Chrome

Войти

Справка Google

Справочный центр
Сообщество
Google Chrome
Политика конфиденциальности
Условия предоставления услуг
Отправить отзыв

Тема отзыва

Информация в текущем разделе Справочного центра

Общие впечатления о Справочном центре Google

Справочный центр
Сообщество

Google Chrome

Источник

Download Article

What this error message means, and how to avoid seeing it

Download Article

What it Means

Max Number Allowed

Why There’s a Limit

Is it a Bug?

How to Avoid It

Do This If You See It

Are you seeing the error message «Rate Limit Exceeded» on a third-party X (formerly Twitter) app? This message occurs when a third-party app that uses the X API reaches the maximum number of API calls that are allowed on your account in one hour. X has also put in place new limits on the number of tweets, DMs, and accounts a regular user can follow in one day. There have been reports of some X users seeing this error message as a bug. This wikiHow article teaches you what the «Rate Limited Exceeded» error message on X means and how to avoid it.

Things You Should Know

Apps using the X API will see «Rate Limit Exceeded» when they exceed the maximum number of API calls.
You may also see this message if you exceed 500 DMs, 2400 tweets, or 400 accounts followed in one day.
In some cases, you may be seeing this error as a bug or glitch.

1
This message usually occurs when a third-party app exceeds the maximum number of API calls in an hour. The X API (application programming interface) is what third-party apps use to request and send information to X servers. X places a maximum number of API calls an account can make using a third-party app per hour. This only applies to third-party apps. It does not apply to the official X website or the X platform app.^[1]
- Any time a third-party requests data from the X platform servers, it counts as an API call. Checking DMs or replies counts as an API call. Requesting data from X counts as an API call. However, sending data to X (posting, direct messaging, favoriting, or following/unfollowing) does not count as an API call.
- A third-party app is any app that requires you to log in to X that is not the X platform itself. Third-party apps can be any application that manages and schedules tweets, like X Pro, formerly called TweetDeck. As of 2011, X Pro is no longer technically a third party app, but still maintains the same usage and purposes. Other social media websites have a crossposting feature to post on multiple platforms. It can also be a desktop or web application or a widget on your phone. It can also be an internal application that developers create to study and analyze data on X.
- While you won’t be able to use the third-party app when your rate limit is exceeded, you’ll still be able to use the X website or mobile app.
2
You may also see Rate Limited Exceeded if you’ve been too active on X. X has limits to keep the service reliable and reduce downtime. If you exceed one of X’s limits, you will generally receive an error message that specifically says what limit you have exceeded:^[2]
- Max number of tweets per day: 2400
- Max number of DMs per day: 500
- Max number of accounts you can follow per day: 400
- Max number of accounts you can follow in total: 5000
- Max number of changes to your account you can make per hour: 4

Third-party apps can make up to 100 API calls per hour. However, different actions can count as more than one API call. For example, refreshing your page takes three API calls because it will request all Tweets, replies, and DMs. There are some exceptions to the 100 API call limit. The following are just a few examples: ^[3]
- Requesting information about why users create, delete, or update X lists allows 300 requests per 15-minute interval.
- Requesting information on who users follow and like allows 900 requests per 15-minute interval.
- Requesting information about who liked a tweet and/or what tweets they liked, allows for 75 requests per 15-minute interval.

There are a few reasons X places a limit on the number of API calls. The following are some of the reasons X has this policy:
- Keep the servers running. X gets tons of API calls at any given moment. Limiting the number of API calls a user helps ensure that the servers don’t get overloaded and can keep up with demand.
- Prevent spam and hacking. Limiting the number of API call requests also prevents users from sending out spam in the form of mass tweets. It also prevents distributed denial of service (DDoS) attacks from hackers.

It is entirely possible. X support has reported in the past that users have been seeing this error message when they weren’t supposed to. It can occur while using the official X app, website, third-party app, or API requests. However, X is usually aware of the problem and works very hard to fix it quickly when it occurs.^[4]

1

Reduce your percent usage to 60 — 70. You can do so in the settings of the app you are using. This will mean that you get fewer updates, but you will use fewer of your allowed API calls per hour.
2

Remove search terms that get fewer results. If you are tracking account engagement, try using fewer words in your search terms. Remove the words that get fewer results.
3

Save your results. If you are going to be using your search results for a long period of time, save them. This will prevent you from making identical requests. Many apps allow you to save your results.

1

Wait until your time expires. X allows you to make 100 API calls per hour. Oftentimes, you can regain your account by just waiting a few minutes. If you receive this message while Tweeting, sending DMs, or following users, you will need to wait 24 hours before you can continue. If you are making changes to your account, you will need to wait an hour before you can make more account changes.
2

Unfollow some accounts. If you are currently following 5000 accounts or more, you will need to unfollow some accounts before you can follow some more.
3

Use the official X app or website. If you can do your work using the official X platform, go ahead and do so. This may not be possible in all cases, but the X API call limit only applies to third-party apps.
4

Change your password. There have been some reports that users were able to reset the API call limit by resetting their password. You should only do this if you are in a bind. It may be easier to just wait to regain your account rather than having to learn and memorize a new password. However, you can make that a little easier by using a password manager.

Ask a Question

200 characters left

Include your email address to get a message when this question is answered.

Submit

References

About This Article

Thanks to all authors for creating a page that has been read 121,654 times.

Is this article up to date?

wikiHow Tech Help Pro:

Level up your tech skills and stay ahead of the curve

Let’s go!

Do you have more questions about this article? Ask and get answers right away.

Ask Question

—

Источник

I have the same problem.
OS: Windows 10
TB: 91.2.1 (64-Bit)

Let’s wait a bit. I see the amounts are going down, this could be a temporary glitch. Worst case I can try a rollback of one patch affecting OAuth.

Hi there!

I have the same problem after updating to Thunderbird 91.2.1 on Windows 10 (64-Bit). My versión of provider is 91.0.2

Same here Win8.1 Thunderbird 91.2.1 — I think I understand the behavior of this nasty bug. After upgrading everyone must relogin on their google accounts and this causes to much traffic. As Philipp said, we must be patient and wait for better times Thanks Philipp for all your work

Experience the same thing. Can you not increase the limit so more people can sign in in a short time? I’m using it daily, missing it already. Great extension for sure, thanks for all the work. But please make it bulletproof on this issue.

Increasing it is up to Google to do, though I will ask.

Thank you for submitting the OAuth Quota Increase request form. A member of our team will review the details and get back to you as soon as possible. This typically takes 2 business days, but in some cases it may take longer. Please monitor your email address for any follow up communication.

kewisch

changed the title
Sign-in rate limit

Sign-in rate limit (Error 403: rate_limit_exceeded)

Oct 26, 2021

Same error…

Errore di autorizzazione
Errore 403: rate_limit_exceeded

È stato raggiunto il limite di frequenza di accesso di questa app.

Same here, fingers crossed on the resolution

It is already working for a day or so here. So this is purely because after an update of Thunderbird you have to sign in again and too many people doing this leads to a kind of cue that exceeds the limits? So after some time it should be possible for everyone again?

regards, Frank

It is already working for a day or so here. So this is purely because after an update of Thunderbird you have to sign in again and too many people doing this leads to a kind of cue that exceeds the limits? So after some time it should be possible for everyone again?

regards, Frank

Yes, this is the case. Once you are in, you should be in for a while. This is purely because I changed the token value and people are logging in, a lot more than usual. It would be great if Google allowed tokens to persist across the same API project, so that I both have control over token usage per version, but folks don’t need to log in again.

Thanks for the information and your work. I’m so happy, that you created this Add-on and work constantly on it. Thumbs up!

I also have the same problem from today, since I updated Thunderbird it asks me to log in to the various accounts and gives me the error in the rate. The curious thing is that I updated the software on two PCs and on the first it didn’t give me any problems. I don’t know if it has anything to do with it, but the software update times were different. On the first PC I also tried unplugging a calendar and resetting it and it just kept working. On the other hand, on the second PC, every attempt failed.
Please do whatever you can to fix this, the add-on was great and great for me at work, giving it up would be awful! Hope you can implement an extension update that fixes everything in a short time!
By from Italy

Same problem. No worries about wating, just adding to the data set.

Same problem here
Update: It worked today.

I’m still getting this issue too. I have tried signing in several times over a couple of days so far. The error message mentions that the developer can request (provider-for-google-calendar@googlegroups.com) to increase this app’s sign-in rate limit. Is this something that can be done so more people can sign in?

Same problem since days. I’m continuously try to sign in but I get I always the rate_limit_exceeded error.
Kind regards
Sven

Same problem. Updated Thunderbird this morning, Google throws error 403 when I try to enable my calendar.

Perhaps sometime today Google comes back (If I am reading comments correctly, they were asked to increase this limit 2 business days ago)?

Best wishes,
Ugis

Oh, just tried again and it worked for me.

Issue appears to be resolved for me also. Thanks.

Seems to be solved for me too. Thanks!

Having the same issue. Started 1/23/2022. Logging into Google and accepting security alert did not fix it. Likely coincidental with sign in rate drop.

Having the same issue. Started 1/24/2022. Logging into Google and accepting security alert did not fix it.

Please stop commenting, if you have the same issue. Just subscribe to this issue ticket and wait for a solution.
You all are disturbing everyone who subscribed to this issue ticket.

I was able to resolve this (if it stays resolved…). Do this at your own risk, and I welcome expert feedback if any of this doesn’t make sense.

Steps, as best as I can recall now:

Log into your Google account via web browser, go to calendars and select the one that’s causing problems. Click the 3 vertical dots to the right and select Settings
Click Calendar Settings
Scroll down to the «Integrate Calendar» section, then down to «Secret address in iCal format».
Click the copy link to get the connection string.
In Thunderbird, File->New->Calendar
Select «on the network», next
Enter your email address and paste the clipboard into Location. Click Find Calendars. Enter your Google password, etc.
Select the calendar from the list that comes up, then OK (or something like that… sorry — it’s not in front of me anymore!)

I have now re-subscribed to the original calendar. Next, I unsubscribed from the old one that was giving errors (in TB, right click the calendar, and unsubscribe). I tested that events sync in both directions.

With this, do we even need the «Provider for Google Calendar» add-in? I see a reviewer’s comment for that add-in that says it’s not needed any more?

Good luck!

@lenhodder That’s the way how it works without the addon.
But this addon let’s you use your main calendar and the shared ones, regardless of private or public and without the need to copy their links.

Updating the addon to 91.0.4 solved the login problem for me.

Edit: I was wrong, after the update it appeared to connect but after restarting Tbird I still get the rate limit error after logging in the extension.

Same issue is here again. The reason is imho that Ubuntu and Mint have finally rolled out the Thunderbird update 78.x to 91.x as part of the automated updates. The add-ons of millions of users worldwide all attempt to re-authenticate with Google and cause the impression of a DDoS. Perhaps someone should drop the guys at Google a note to weaken the restrictions for some days…

I updated the addon to 91.0.4 (dated today) and it still works after restarting TB and rebooting pc. I also updated TB to 91.5.1.

Updated to TB 91.5.1.

Now all my calendars work OK

All ok, now!

All calendars work!

After updating TB to 91.5.1 the problem disappeared

After updating TB to 91.5.1 the problem disappeared

It still doesn’t work for me.

Same here, not working with tb 91.5.1 and plugin 91.0.4:

403: rate_limit_exceeded

Just updated to 91.5.1 and still have the same problem.

I have the same problem, thunderbird and plugin is up to date.

same for me, All components are up2date but code 403 is showing.

Same for me. Sorry but I tend to look for another alternative. Things happen all the time that shouldn’t happen in a productive environment, so that the complete functionality is no longer available. It then makes no difference for me as the end user whether the problem is with Google or with the plugin — it just doesn’t work and I need time to work around it.

What the heck is going on with this??? I have used thunderbird for many many years and now I get this strange 403 error «This app has reached its sign-in rate limit for now.» Never had any issues but this is really very annoying!!!

I have two computers both running Fedora 35. The older machine is running the latest version on Fedora 35 which is tb 91.5.0 and provider 91.0.4 This combination works fine on that machine. On the newer machine running the same version of software it will never work since yesterday. I tried downgrading as well as manual non-repo upgrading to tb 91.5.1 with provider 91.0.4. It wouldn’t work with either of these combinations.

Confirmed, for me it is also wirking again!

I have two computers both running Fedora 35. The older machine is running the latest version on Fedora 35 which is tb 91.5.0 and provider 91.0.4 This combination works fine on that machine. On the newer machine running the same version of software it will never work since yesterday. I tried downgrading as well as manual non-repo upgrading to tb 91.5.1 with provider 91.0.4. It wouldn’t work with either of these combinations.

Now like magic today it’s working again and not a post from anyone why it failed to work for two day. In the end, I am running the same lower version of thunderbird that didn’t work yesterday and the same provider version. It would be good to understand why so it doesn’t happen again.

. It would be good to understand why so it doesn’t happen again.

It looks like an update was pushed out that caused the addon to have to sign back in to the Google calendar. Having many thousand installations of the addon all trying to do this around the same time caused google to reject the logins from the addon due to its login rate limit, hence the error everyone was receiving. I suspect the rate of logins has now dropped to a level where google is happy again.

Start Thunderbird and get the Google login box. Log in and respond to a verification prompt from Google on my phone. Then get 403 error. I then respond to the Google security alert e-mail, log into my Google account, verify myself again, and Calendar works.

This process worked for me as well, Linux, TB version 91.5.0, Plugin version 91.0.4

This procedure didn’t work for me. I’ve tried it several times. Most probably the success is because your attempt went under the access rate limit.

. It would be good to understand why so it doesn’t happen again.

It looks like an update was pushed out that caused the addon to have to sign back in to the Google calendar. Having many thousand installations of the addon all trying to do this around the same time caused google to reject the logins from the addon due to its login rate limit, hence the error everyone was receiving. I suspect the rate of logins has now dropped to a level where google is happy again.

Thanks daveymg-nz , I was reinstalling and trying different combinations for quite some time yesterday. Happy to know the problem is understood.

I was able to resolve this (if it stays resolved…). Do this at your own risk, and I welcome expert feedback if any of this doesn’t make sense.

Steps, as best as I can recall now:

Log into your Google account via web browser, go to calendars and select the one that’s causing problems. Click the 3 vertical dots to the right and select Settings

Click Calendar Settings

Scroll down to the «Integrate Calendar» section, then down to «Secret address in iCal format».

Click the copy link to get the connection string.

In Thunderbird, File->New->Calendar

Select «on the network», next

Enter your email address and paste the clipboard into Location. Click Find Calendars. Enter your Google password, etc.

Select the calendar from the list that comes up, then OK (or something like that… sorry — it’s not in front of me anymore!)

I have now re-subscribed to the original calendar. Next, I unsubscribed from the old one that was giving errors (in TB, right click the calendar, and unsubscribe). I tested that events sync in both directions.

With this, do we even need the «Provider for Google Calendar» add-in? I see a reviewer’s comment for that add-in that says it’s not needed any more?

Good luck!

This worked for me. Thanks!

Источник

Likely something to do with pytorch=1.9:

Works with python=3.7 and pytorch=1.7

Python 3.7.10 | packaged by conda-forge | (default, Feb 19 2021, 16:07:37) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> torch.__version__
'1.7.0'
>>> model = torch.hub.load('pytorch/vision:v0.10.0', 'resnet50', pretrained=True, force_reload=True)
Downloading: "https://github.com/pytorch/vision/archive/v0.10.0.zip" to /home/ml/farleylai/.cache/torch/hub/v0.10.0.zip

Works with python3.9 and pytorch=1.7.1 and 1.8.1.

Python 3.9.5 (default, Jun  4 2021, 12:28:51) 
[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
import torch
>>> torch.__version__
'1.7.1'
>>> model = torch.hub.load('pytorch/vision:v0.10.0', 'resnet50', pretrained=True, force_reload=True)
Downloading: "https://github.com/pytorch/vision/archive/v0.10.0.zip" to /home/ml/farleylai/.cache/torch/hub/v0.10.0.zip

Python 3.9.5 (default, Jun  4 2021, 12:28:51) 
[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> torch.__version__
'1.8.1'
>>> model = torch.hub.load('pytorch/vision:v0.10.0', 'resnet50', pretrained=True, force_reload=True)
Downloading: "https://github.com/pytorch/vision/archive/v0.10.0.zip" to /home/ml/farleylai/.cache/torch/hub/v0.10.0.zip

Failed with python=3.9 and pytorch=1.9

Python 3.9.5 (default, Jun  4 2021, 12:28:51) 
[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> torch.__version__
'1.9.0'
>>> model = torch.hub.load('pytorch/vision:v0.10.0', 'resnet50', pretrained=True, force_reload=True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/site-packages/torch/hub.py", line 362, in load
    repo_or_dir = _get_cache_or_reload(repo_or_dir, force_reload, verbose)
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/site-packages/torch/hub.py", line 162, in _get_cache_or_reload
    _validate_not_a_forked_repo(repo_owner, repo_name, branch)
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/site-packages/torch/hub.py", line 124, in _validate_not_a_forked_repo
    with urlopen(url) as r:
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/urllib/request.py", line 214, in urlopen
    return opener.open(url, data, timeout)
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/urllib/request.py", line 561, in error
    return self._call_chain(*args)
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/home/ml/farleylai/miniconda3/envs/sinet39/lib/python3.9/urllib/request.py", line 641, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 403: rate limit exceeded

Источник

В этой статье вы узнаете как убрать ошибку rate_limit_exceeded, которая появляется в почтовом клиенте Thunderbird.

Приятного чтения!

Заказывайте у нас разработку сайтов, настройку и сопровождение контекстной рекламы, поисковое продвижение и добавление организаций на карты.

Исходные данные:

Thunderbird 91.8.0 (64-битный)

Описание проблемы

При синхронизации почты в Thunderbird гугл аккаунты требуют ввести логин и пароль от аккаунта gmail. После вода данных выскакивает ошибка:

Authorization Error
Error 403: rate_limit_exceeded

This app has reached its sign-in rate limit for now.

Google limits how quickly an app can get new users. You can try signing in again later or ask the developer (provider-for-google-calendar@googlegroups.com) to increase this app’s sign-in rate limit.

If you are the developer for this app, you can request a sign-in rate limit increase.

При просмотре подробностей:

login_hint: xxxxxxx.yyyyyyyyyy@gmail.com
hl: de
response_type: code
redirect_uri: urn:ietf:wg:oauth:2.0:oob:auto
client_id: .apps.googleusercontent.com
access_type: offline
scope: https://www.googleapis.com/auth/calendar https://www.googleapis.com/auth/tasks

Смысл проблемы

Суть проблемы в календарях аккаунтов gmail. Запросы с почтовой программы для синхронизации календарей аккаунтов вызывают превышение лимита.

Решение проблемы

Заходим в гугл аккаунт с которого почтовый клиент Thunderbird собирает почту. Для этого переходим на google.by (.com, .ru). Входим в наш аккаунт. Нажимаем на на 9 серых точек в правом верхнем углу (приложения Гугл) и выбираем там Календари (Calendars):

2. Слева внизу в закладке «Мои календари» (My calendars) выбрать календарь с название как логин аккаунта и нажать на три серых точки:

3. В появившемся меню выбираем «Настройки и общий доступ» (Settings and sharing):

4. На странице настроек спускаемся в самый низ и ищем пункт настроек «Закрытый адрес в формате iCal» (Secret address in iCal format). Он изначально будет скрыт. Нажимаете на иконку «Копировать» (Copy)