kus
Eugen Rochko@k WELL i cannot find any error or bad http status code in the logs since last restart, so I have no clue
@Gargron it is vertical. ffmpeg -i Qa1a2ef.mp4 -c:v libvpx -b:v 1M -c:a libvorbis lolcat00.webm Press [q] to stop, [?] for help
frame= 901 fps=9.6 q=0.0 Lsize= 2365kB time=00:00:15.01 bitrate=1290.2kbits/s
video:2358kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.291710%
welp encoding as a webm didn't help... the webM is under 2.5MB but still I get the same error https://mastodon.social/media/2004 https://mastodon.social/media/2005
@k I don't know what the issue is, most severe thing in the logs is a 422 status code. Open web inspector, switch to network tab, then try the upload again, and tell me what the actual response looks like
@k That's not helping, you need to look in the network tab - it will list all requests to the website, one of which will go to /api/v1/media, you need to click on that one and then "response" tab
@Gargron not on my computer at the moment. Will do when I get back in the computer. Meanwhile, does this help?
@k Nope. I know what a JSON parse error is, the server does not return correct JSON. However in my logs everything looks normal so I need to know what it is that it returns instead of JSON :P
@Gargron <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.9.3 (Ubuntu)</center>
</body>
</html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.9.3 (Ubuntu)</center>
</body>
</html>
@k Ohhh. I guess nginx times out the request before the encoding finishes.
@Gargron but I thought there was no encoding if 1. the file is webm AND 2. the filesize is under 5M?
@k I think that when I added the ability to upload and convert mp4 into webm it started converting everything into webm, even if it is already
