just2me wrote:A new filter...?
Just a guess because the owners of the site are investing literally tons of money atm. (Rumours say it’s East German Mark banknotes. They use them as eco-friendly insulation for the cavities in the walls of their houses...)
Like I said before: check the data flow.
To see where the upload is actually getting stuck, you can check the browser's Developer Tools:
- Open the DevTools (F12 or Ctrl + Shift + I on Windows/Linux, Cmd + Option + I on Mac).
- Switch to the Network tab at the top.
- Start the upload. You will see a new request appear in the list (usually a POST or PUT request).
- Click on that upload request and open the Timing sub-tab (on the right side).
Look at the breakdown there to pinpoint the bottleneck:
- Request sent: This is the actual upload phase where your browser pushes the file data to the server. If it gets stuck or takes forever here, the bottleneck is your upload speed, a bad connection, or a file that's too large.
- Waiting (TTFB): Once the file has completely reached the server, this phase begins. The server is now processing the file (e.g., virus scan, resizing, saving to database). If it hangs here (or stays pending for a long time after uploading), it's a server-side issue.
- Content Download: The server just sends back a tiny confirmation (like "Upload successful"). For uploads, this usually takes just a few milliseconds.
Also, check the Status column for that request—if it turns red and shows an error code (like 413 Payload Too Large, 500, or 504 Gateway Timeout), that will tell you exactly why the server rejected or dropped the upload.