I had to file two reports this week and neither actually reached NCMEC. Both hung on the actual image upload. It does submit at least *some* data to NCMEC, since we get a seemingly valid case number from them, but it just bounces back from their system as an incomplete report.
As an aside, NCMEC's own CyberTip system is much easier to use than it perhaps used to be, so using this instead may actually be a viable option now.
This is the two most-recent submissions on the tool, btw (numbers 157 and 158). I haven't yet received a bounceback from 158, but since the upload box glowed an ominous red I'd be surprised if it actually submitted.
I’m not sure exactly but 158 was a pretty large file for sure. The files are obviously not very easily accessible now to check.
I tested a large (6.2 MB) file (locally) and got this error in the logs:
ingress_1 | 2019/01/21 17:07:14 [error] 6#6: *8 client intended to send too large body: 5228609 bytes, client: 172.19.0.1, server: localhost, request: "POST /api/takedown/15/ncmec/file/8 HTTP/1.1", host: "127.0.0.1:8888", referrer: "http://127.0.0.1:8888/takedown/create"
I increased the upload limit from 2MB to 64MB and then I was able to upload the large file.
This hasn't been merged / deployed yet (I wont be able to until the VPN starts working again).
Just got access to the VPN, and sure enough:
ingress_1 | 2019-01-15T22:46:56.628586891Z 2019/01/15 22:46:56 [error] 6#6: *137 client intended to send too large body: 1863932 bytes, client: 172.21.0.4, server: localhost, request: "POST /api/takedown/158/ncmec/file/51 HTTP/1.1", host: "lcatools.corp.wikimedia.org", referrer: "https://lcatools.corp.wikimedia.org/takedown/create"
$ docker-compose exec api php -i | grep 'post_max_size' post_max_size => 64M => 64M $ docker-compose exec api php -i | grep 'upload_max_filesize' upload_max_filesize => 64M => 64M
@jrbs I'm going to close this issue for now, but please reopen if you experience the same problem again.