Feedback Technical Grievances

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Able to post fine from the west coast of the US in the autistic thunderdome. loading this thread took like 5 minutes, and loading the homepage also hung, but as a north american user directly connecting through a major broadband ISP, working fine
 
Able to post, but sometimes a post doesn't appear properly after pressing "Post Reply" and when I refresh the page I magically double-post.
 
Getting random white screens here. Usually works OK again after refreshing a couple of times.
 
Search seems to not work. Clicking on "postings" or "your content" similarly doesn't work
 
Testing... Testing...

Posting and post preview works for me despite being in the affected areas, I wonder if it's a browser-related issue.
 
I really wish people would stop posting if they can post. It doesn't help.

The issue is that we use multicast so individual ISPs cannot completely disrupt service by dropping.
The server for multicast in North America is having issues. It is returning errors and dropping requests for no reason. There's something broken with it. I am pretty sure it is a novel issue because I can find precisely zero technical details about the problem online.

The issues with no post box appearing ARE NOT RELATED TO THE FOLLOWING:
  • Your ISP.
  • Your connection.
  • Your country.
The issue with that is you are not getting the JavaScript file required to use the postbox, or your browser has cached an error page for that file, which does not provide that functionality. This issue can be fixed by simply clearing your cache, using a different browser, changing VPN to Europe, etc. I don't know why this is happening.

The other issue people are having is a 408 error when trying to post. This is what causes the "Oops" error. This is something wrong with the webserver.


The issue with the postbox is some shit I do not understand and haven't seen before a week ago. Saying "I can post!!!" does not help. I need someone experiencing the issue who understands how to diagnose website problems to tell me specifics about the error.
 
This is what the browser console said to me when it would not let me post a second ago in Firefox 108.0.2 64-bit. It went to a white screen instead of posting.

"Failed to register/update a ServiceWorker for scope ‘https://kiwifarms.net/’: Load failed with status 429 for script ‘https://kiwifarms.net/service_worker.js’."
 
That's not an issue. server_worker.js is just what you see when the site's down and the page is grey with a refresh button. It never updates and has no functional value to the site when it's up.
 
So I’m in North America and can post on the site from my iPhone…but ONLY if I’m connected to a WiFi signal. On phone data, it won’t allow the post to fully process. Can read the site done, just not post.

Just info that.I hope helps.
 
2023-01-09 15_45_37.png
2023-01-09 15_48_05.png

Yes, that is a real name.
2023-01-09 15_48_39.png 2023-01-09 15_54_11.png
I thought it's a troll.

Edit: No, I'm not contacting people on your behalf, Null. I have a meme account and tweeted about your poast and this guy came into the replies. I didn't ask anyone for help, only tweeted that you poasted about issues with haproxy.
 
Last edited:
Eurofag here, also can't search or view people's postings on their profile, I get the generic oops error message.
 
Well, I have no idea.
My iOS device is fine.
My Windows device is fine.
My Android device is not.
My Linux device is not, except when setting net.ipv4.tcp_mtu_probing=1 or reducing the MTU on the path.

It certainly seems like a lower MTU in the path and something blocking ICMP responses that's usually used in PTMU discovery.

Or something that hates large packets, but only some of them.
 
I'm posting from the Pacific NW on a Windows laptop, no problems here
 
Does anyone have the raw URL of the javascript file that is fucking out

because if so you can browse to that directly in a "broken" browser and force a refresh to get it into cache - or look at the headers on the "dead" page as it may have "cache broken responses" or some shit set.
 
You must log in or register to reply here.
Back
Top Bottom