Firefox blocked Kiwifarms?

[Do Not Touch Me Pls]

I am now unable to browse Kiwfarms on firefox since today in all of a sudden. Just "the connection has timed out". Yesterday, it is working perfectly. For some reasom it works on Chromium even on the same device and comnection. Anyone else?

 

[rel=alternate]

Works fine for me, I think that's on your end.

 

[The Skeksis Emperor]

I'm on Firefox and it works fine for me.

 

[Mr.Miyagi]

Null put a message on telegram regarding this.

You'll need to go to Settings>Privacy and Security>Clear Data if you want to clear your cache. That and a Ctrl+F5 worked for me.

 

[Do Not Touch Me Pls]

Null put a message on telegram regarding this.
Ver archivo adjunto 6002459
You'll need to go to Settings>Privacy and Security>Clear Data if you want to clear your cache. That and a Ctrl+F5 worked for me.

Got back in thanks!

 

[i440BX]

Null put a message on telegram regarding this.
Ver archivo adjunto 6002459
You'll need to go to Settings>Privacy and Security>Clear Data if you want to clear your cache. That and a Ctrl+F5 worked for me.

Oh this sucks...
Lets pray Null will not remain without options for providers...

 

[vomitusdeux]

Firefox works fine for me.

 

[IDanceonTrannyGraves]

Anyone else?

Just tried it, it worked for me.

 

[Power Ranger Monster]

Null put a message on telegram regarding this.
Ver archivo adjunto 6002459
You'll need to go to Settings>Privacy and Security>Clear Data if you want to clear your cache. That and a Ctrl+F5 worked for me.

Cache clearing also works for Pale Moon. Thanks!

 

[NaggotFigger]

Firefox still works fine with me. Like Mr. Miyagi said, clean your caches by CTRL+F5 or by settings manually like this: Settings > Privacy & Security > Clear Data and it should do its job. I typically use Brave or Floorp on Windows, and they still work smoothly.

edit: too late

 

[gagabobo1997]

clearing cache on firefox isn't working for me

posted from my Chromium™ web browser

 

[Faceless Whore]

I browse KF in a container and I had to create a new container to get it to work again. Clearing cache wasn't enough for me.

 

[Josephine Knezevic]

clearing cache on firefox isn't working for me

Same. I did what Null said, but doesn't work. Use Brave : )

 

[Moths]

Ctrl+F5 worked for me.

This, after clearing the cache it wouldn't work until a ctrl-f5 to force download new files on Waterfox

 

[ToroidalBoat]

same here: works after cache clear

 

[SPCC Archivist]

Firefoxchad here.
Just in case people are reading this from their phone (I was able to browse on the phone during the momentary downtime), everything the users said here is correct, Firefox still works just fine.
However, I would like to provide an even more surgical solution to this, in case you need to retain your cache for your workflow:

Right click on a Kiwi Farms URL from your History tab, then click "Forget about this site", with the option to clear the cache too.
Make sure you target all the domains you have used before (.net, .us, .st, .tw, .ru, or even sneed.today if you were around for that).
After this, just CTRL+F5, it will work like a charm, and you will not be forced to wipe your entire browser cache for something very minimal.

 

[エボラちゃん]

clearing cache on firefox isn't working for me

posted from my Chromium™ web browser

I browse KF in a container and I had to create a new container to get it to work again. Clearing cache wasn't enough for me.

I couldn't reach the site despite clearing the cache in Firefox settings, doing CTRL+F5 on the KF page worked for me.

 

[vomitusdeux]

I only use tor and firefox and I'm doing just fine.

 

[._.]

I just wanted to report in and let you guys know that Im using firefox and Im posting while riding a literal fox and its working just fine.

 

[y a t s]

For future reference, temporarily disabling the HTTP cache under the network tab of the developer tools and refreshing the page normally will fix most issues like this if a normal cache clear doesn't. Make sure you enable it after you get things working again, or you might run into some issues along with longer load times.

Modern browsers like Firefox have multiple caches for different purposes. They primarily differ in how they store data, what types of data is stored, when such data is stored, and how long it is stored. From what I can tell, this was an issue of old header data that pointed to the now dead SharkTech server, hence needing to deal with the HTTP cache.