dChan
Anonymous ID: 91d178 Sept. 30, 2021, 1 a.m. No.97020   🗄️.is 🔗kun   >>7023 >>7037

@Jim

 

When I upload larger files like movies 10 megs or more I get an error message saying "took too long, your post may still go through".

 

It seems there is a timeout, and it's not high enough for 128ducks. Is there a way to extend it so that this message doesn't happen anymore? Not only does it break (you), but it also breaks automatic posting too.

Anonymous ID: 91d178 Sept. 30, 2021, 1:20 a.m. No.97025   🗄️.is 🔗kun   >>7026

>>97023

For me it happened at the start back then, but never anymore since 128ducks and it sucks, except when reuploading data.

 

It really seems to be some timeout, like it now has to send the file to 128ducks, takes too long and aborts.

Anonymous ID: 91d178 Sept. 30, 2021, 1:20 a.m. No.97026   🗄️.is 🔗kun   >>7029

>>97025

>since 128ducks and it sucks, except when reuploading data.

Sleepy, I mean since 128ducks it happens all the time for larger files. Doesn't happen for small files of a few megs.

Anonymous ID: 91d178 Sept. 30, 2021, 1:39 a.m. No.97032   🗄️.is 🔗kun

>>97029

I'm currently uploading the Rusty videos again, so that they work.

I see that upload goes to 100%, and then it almost immediately gives me the "server took too long" message. It doesn't even wait.

Anonymous ID: 91d178 Sept. 30, 2021, 1:54 a.m. No.97037   🗄️.is 🔗kun

>>97020

I see, what I'm getting is a 504 reply from the server.

 

HTTP/2.0 504 Gateway Timeout

server: nginx

date: Thu, 30 Sep 2021 08:53:32 GMT

content-type: text/html

content-length: 1482

etag: "6000aaf5-5ca"

X-Firefox-Spdy: h2

Anonymous ID: 91d178 Sept. 30, 2021, 4:18 a.m. No.97069   🗄️.is 🔗kun

https://www.youtube.com/watch?v=FAVdQHlcrQI

>QQ

 

Task Force Green | "America's Finest"

 

Looks like lots of footage from DTLA 2019