Lluís Ulzurrun de Asanza Sàez

@ZeeshanAhmadKhalil Have you tried running ffprobe directly in Heroku? Looks like an installation issue of ffprobe binaries. You might need to add some [additional buildpack](https://stackoverflow.com/a/52142087 to get ffprobe running there

@mxnuchim @milesyang0220 Have you tried adding `unsafe-perm=true` to your `.npmrc` file? This is a [known issue in `@ffprobe-installer/ffprobe`](https://github.com/kribblo/node-ffmpeg-installer/issues/21), which `get-video-duration` depends on. @atumas-bananamilk Let's keep this thread focused on AWS...

I think this might be related to ffprobe having glibc statically linked and not being able to do DNS resolution. Could you try installing `nscd` through your package manager and...

@danny-does-stuff No idea why Node 20 image would break ffmpeg. It's hard to tell because `node:20` and `node:16` are both ambiguous versions: those tags point to the latest release in...

Try to clone the repo using HTTPS instead of SSH On 29 Nov 2018, 11:57 +0100, uagraw , wrote: > Hi Team, > Upon making sure that all requirements are...

I've upgraded it's devDependencies, try with version `0.0.5`. (Note that production version does not have any dependency)