Feedback Technical Grievances

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Just wanted to bring this minor issue with the Quattrocento font back up:
Doppelmonger said:
For some reason, I can not use the "ñ" character with the updated font and it defaults to the "n" in both uppercase and lowercase, I have to use another one for it to show up properly.
Click to expand...
 
  • Agree
Reactions: Overly Serious
LanceHaver said:
Trying to upload a 138MB MP4 (youtube mirror) and it uploads to 100% then gets stuck and doesn't load into the post. Is there any way for me to fix that?
EDIT: Just saw Null's reply above, I'll try firefox.
EDIT2: Tried Firefox with CTRL+F5 and fresh login, upload drops/fails at 10-15%.
Click to expand...

Null said:
yeah uploads are broken. tor and firefox can sometimes work better. i don't know what you want me to say. the issue is that the reverse proxy i've built for some reason chokes huge uploads. i've spent probably 100+ hours fiddling with config to try and get it working better but you're talking about TCP-NGINX-NGINX-PHPFPM as a pipeline. I don't know where it's breaking, nobody I've spoken to can figure it out, and I can't really let random people look at the config or access the servers. I can't help you. Try Tor or FireFox.
Click to expand...

So I tried Chrome, Firefox and Edge, didn't work. Thought I'd try a non-Chromium browser, so I tried Pale Moon, which is a fork of Firefox that uses Goanna, a fork of the Firefox Gecko engine before it was rewritten. It worked!
Here is the post with the MP4 uploaded for reference.
 
Last edited:
  • Like
  • Informative
Reactions: Fuck It We'll Do It Live and Overly Serious
I am probably not adding anything useful to the conversation about the formats not working correctly. Could it be a device issue instead of browser issues? Maybe people have issues with tablets or smartphones working with the sites instead of traditional computers?
 
  • Thunk-Provoking
Reactions: Mr. 0
Battlefield2142EU said:
Maybe people have issues with tablets or smartphones working with the sites instead of traditional computers?
Click to expand...
at last, history repeats
SA furries get gassed, KFphonefags get glassed
chris shits his pants
null gets arrested mid-stream and becomes a drone operator in yugoslav wars 2
everything comes full circle
 
  • Thunk-Provoking
Reactions: Dr. Jaime Reyes and Battlefield2142EU
LanceHaver said:
So I tried Chrome, Firefox and Edge, didn't work.
Click to expand...
My personal experience is it'll appear the upload has failed but it actually succeeded in the background and failed to receive the response. In that case duplicate your tab (by middle clicking the refresh button) and check if you can insert it from the draft in the other tab. I had this happen earlier when uploading a Bossman clip and I tested uploading an attachment to this thread and the same behavior occurred, timed out after 100 seconds on the client but the backend did receive it.

Searched the thread and came across this
Null said:
MIDDLE (CN ONLY)
Click to expand...
I know this post is old and you've already tried a lot of shit but here's my 2c anyway which may also be useful to others in the thread who work with nginx. I've commented the modified settings with their previous values.
Code: 
    location = /attachments/upload {
        proxy_cache off;
        proxy_buffering on;
        proxy_request_buffering off; # was on
        proxy_buffer_size 128k;
        proxy_buffers 128 128k;
        proxy_send_timeout 30s; # was 600s
        client_max_body_size 0;
        proxy_http_version 1.1;
        client_body_timeout 30s; # was 600s
        send_timeout 600s;
    }
Rationale for disabling request buffering is nginx's behavior is to wait until the client has sent the entire body before forwarding it on which causes the fast climb to 100% then stall as you're waiting for the buffered content to send to the backend. With request buffering, uploads may appear faster but actually end up taking longer with the user stuck at 100% not knowing the true progress.

The reason for reducing proxy_send_timeout and client_body_timeout is because they're not based on the life of the connection but instead based on time since last send or read operation respectively. Having super high values for client_body_timeout opens up the possibility of slow POST attacks that stall the frontend proxy with many long-lived idle connections eating up worker connections (see goloris). With request buffering off, it's even more important to tighten up these timeouts as they can stall the backend server too. High proxy_send_timeout is in my opinion unnecessary since if you're 30 seconds without sending anything, the backend has 41%'d and there's no point tying up resources on a dud upload attempt.

As for the actual connection to the backend, if you've encapsulated it within wireguard then make sure the MTU is set right if your tunnel is established over IPv6. The default of 1420 bytes is acceptable if your tunnel is established over IPv4 and carrying v4/v6 traffic, but IPv6 inside and outside will cause fragmentation which leads to a lot of weird performance issues if PMTUD is not working.

At work we're replacing an antiquated HTTP load balancing appliance and nginx was picked initially as it's popular, but I ended up steering the project to haproxy as nginx is such a pain in the ass for load balancing. Monitoring is basically non existent with the FOSS version of nginx, stub_status is a joke.
 
Flaming Dumpster said:
At work we're replacing an antiquated HTTP load balancing appliance and nginx was picked initially as it's popular, but I ended up steering the project to haproxy as nginx is such a pain in the ass for load balancing. Monitoring is basically non existent with the FOSS version of nginx, stub_status is a joke.
Click to expand...
Checked out Tengine?
 
Battlefield2142EU said:
I am probably not adding anything useful to the conversation about the formats not working correctly. Could it be a device issue instead of browser issues? Maybe people have issues with tablets or smartphones working with the sites instead of traditional computers?
Click to expand...
At the time it was the PC version that was fucked up, phone was fine. You'll have to keep the haha phonefag shitposts for another day...
 
  • Horrifying
Reactions: Mr. 0
Dumb question: after I get the second factor email code, I check the 30 day box but I’m logged out and need to MFA again after 7 days (looking at the KF dedicated email it’s sometimes 8 but that’s just because I didn’t try to login within the same calendar day I believe). Is that intentional? I don’t care if it is, just maybe reword the 30 day box to 7?
 
Strange bug, I've found if I just let Firefox sit on the homepage for long enough it chugs the browser and freezes it badly. Doesn't happen in threads, wondering if it's a chat issue.
 
Video uploads are still completely fucked up. I know the limit is 200 mb but anything over 10 mb turns into a tedious game of hit or miss, as 9 out of 10 times I'll get the "sorry failed lel contact janny" message. I'm trying out pale moon as someone suggested above, will update if it works.

Update: First couple of tries failed. This probably won't work better than Chrome. I'll try Firefox and Edge while I'm at it.
 
Last edited:
  • Informative
  • Autistic
Reactions: NoReturn and Gorton Colu
GenociderSyo said:
I've noticed that if you are uploading a 10 meg or so file and open a 2nd tab while doing so that tab fails to connect to KF at all while the file is trying to upload. The minute the file fails the other tab will instantly load in. This only happens when uploads are being temperamental.
Click to expand...
Firefox worked with 1 tab open (I was trying to upload a 50 mb mp4 video).

Pale moon and Chrome didn't work even with just 1 tab.
 
  • Like
  • Autistic
  • Thunk-Provoking
Reactions: AFAB, Gorton Colu and GenociderSyo
Battlefield2142EU said:
From what I hear. Phonefags can’t even post pictures or use the buttons anymore. But it depends on what kind of phone is used. It is usually apple crap screwing up. Something awful lost half its users because iPhones can't use the site.
Click to expand...
I'm not on phone; On (a shitty, old) laptop, with both Chrome and Brave I've had repeated issues with KF last week or two; It goes into this weird state where links don't work, right-click doesn't do anything, and if left too long it won't even let me switch tabs, and basically freezes up the whole browser.

The wierd/suspect thing is, it only seems to ever happen on KF front page; In threads or any other page, I've never had the issue.
 
  • Thunk-Provoking
Reactions: Battlefield2142EU
keep fucking getting "Parsing response failed" when trying to upload any copied image, and downloaded images turn grey and dont allow me to insert
 
  • Like
Reactions: NoReturn
Snuckening2 said:
The wierd/suspect thing is, it only seems to ever happen on KF front page; In threads or any other page, I've never had the issue.
Click to expand...
If you have no interest in using chat, you can block it. Add to ublock origin in the My Filters section.
clipartfan92 said:
Code: 
||kiwifarms.st/chat.ws$1p
||kiwifarms.st/assets/chat.js$1p
||kiwifarms.st/test-chat$1p
kiwifarms.st##.hb-chat--passive.hb-chat--widget.block--hb-chat.block
kiwifarms.st##.hb-chat--widget.block--hb-chat.block
Click to expand...
edit:
For the upload issues, it's hit and miss. I've had good luck using the stock Mullvad Browser (firefox fork) and on the occasion the uploads fail, just trying again in 30 minutes or so. File size and type doesn't seem to make a difference when they fail, it could be a 5MB mp4 or a 90MB mp3.
 
Last edited:
  • Informative
Reactions: AFAB and Snuckening2
You must log in or register to reply here.
Back