Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why does firefox provoke '429 too many reqs' block on Vimeo website?

  • 4 replies
  • 6 have this problem
  • 1 view
  • Last reply by Derek C

more options

When I try to visit vimeo.com with Firefox (version 37.0) I am receiving a block message from the server titled '429 Too many requests'. I can however then use another browser (Konqueror - supplied with my Fedora KDE plasma system [fc21]) to access the site without a problem. I have tried clearing Firefox cache and cookies and running in Safe mode with all add-ons disabled but it still brings the 429 error message. I'm stumped. Any advice?

When I try to visit vimeo.com with Firefox (version 37.0) I am receiving a block message from the server titled '429 Too many requests'. I can however then use another browser (Konqueror - supplied with my Fedora KDE plasma system [fc21]) to access the site without a problem. I have tried clearing Firefox cache and cookies and running in Safe mode with all add-ons disabled but it still brings the 429 error message. I'm stumped. Any advice?
Attached screenshots

Chosen solution

You can remove all data stored in Firefox from a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History > Show All History" or "View > Sidebar > History") or via the about:permissions page.

Using "Forget About This Site" will remove all data stored in Firefox from that domain like bookmarks, cookies, passwords, cache, history, and exceptions, so be cautious and if you have a password or other data from that domain that you do not want to lose then make sure to backup this data or make a note.

You can't recover from this 'forget' unless you have a backup of the involved files.

It doesn't have any lasting effect, so if you revisit such a 'forgotten' website then data from that website will be saved once again.


Create a new profile as a test to check if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

Read this answer in context 👍 1

All Replies (4)

more options

Chosen Solution

You can remove all data stored in Firefox from a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History > Show All History" or "View > Sidebar > History") or via the about:permissions page.

Using "Forget About This Site" will remove all data stored in Firefox from that domain like bookmarks, cookies, passwords, cache, history, and exceptions, so be cautious and if you have a password or other data from that domain that you do not want to lose then make sure to backup this data or make a note.

You can't recover from this 'forget' unless you have a backup of the involved files.

It doesn't have any lasting effect, so if you revisit such a 'forgotten' website then data from that website will be saved once again.


Create a new profile as a test to check if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

more options

Thank you cor-el. I will try this tomorrow and report back.

more options

Getting Firefox to forget the site didn't work so I used profile manager to create a new profile and was able to access the vimeo website without problems - Thank you cor-el.

I will now go through the diagnostic steps to either fix my original profile or migrate my data to the new profile as outlined in the links you gave.

more options

Well, that was relatively easy. I backed up my original profile and then only had to delete 'extensions.ini' and 'pluginreg.dat' and the problem with vimeo was fixed :)