![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
How are cookies getting blocked without any input from me?
I have a recurring problem with site specific cookies. The OS is Ubuntu 12.04 with Firefox 14, although I had this problem with 13 too. I have Firefox set to delete almost all cookies on close, with the exception of 4 or 5 sites that I allow. However, occasionally, I will find that I can't stay logged into a site (usually Metafilter) and I will find that site in the blocked cookies list, even though I did not add it to the list. Sometimes it will stop working 10 minutes after I removed the block, and I'll find the site in the blocked list again. Usually several sites that I recently visited will be in the blocked list, but Metafilter is the only one where I log in so it is the only one where this actually presents a problem.
I tried adding Metafilter as an always accept cookies exception, but it doesn't make a difference. If a site is listed as both always accept and block, block apparently takes precedence.
Any ideas on how / why this is happening?
Modified
All Replies (2)
Hi,
You can consider the Reset Firefox feature via Help (Alt + H) > Troubleshooting Information and check before installing add-ons. If you are using any privacy software on the PC you can also try to adjust its settings/filters.
(To revert to the previous profile you were using, close the new profile (i.e. exit Firefox), start Firefox and choose the Default User profile. While the Profile Manager is open, you can also delete the newly reset profile (the one containing random numbers), or the former profile, as the case may be). If the reset is okay, it would be a good idea to delete the old profile as otherwise it would be left intact with the previous data until deleted.
I found some info that indicated that the Priv3 extension could be the cause here. It's sporadic enough that I feel like I need to give it a week or so before I call it - but if you are using Priv3 disabling it might be a good idea.