Strange, now your webhosting provider know what is the correct FFmpeg binary path, i wonder they really got check your question properly or not in earlier when you consult with them at the first time.
Because in your previous reply, you did mentioned they confirm this following path was FFmpeg binary path.
[gist type="php"]
/var/www/clients/client6/web8/web/libraries/joomla/filesystem/file.php
[/gist]
By the way, thanks for getting back to us, so now you already get the correct FFmpeg binary path now confirmed by your webhosting provider and i believe you should notice some warning message when you save this
/usr/bin/ffmpeg path into the Easysocial configuration setting.
Warning: is_file(): open_basedir restriction in effect. File(/usr/bin/ffmpeg) is not within the allowed path(s): (/var/www/clients/client6/web8/web:/var/www/clients/client6/web8/private:/var/www/clients/client6/web8/tmp:/var/www/e-sports.rocks/web:/srv/www/e-sports.rocks/web:/usr/share/php5:/usr/share/php:/tmp:/usr/share/phpmyadmin:/etc/phpmyadmin:/var/lib/phpmyadmin) in /var/www/clients/client6/web8/web/libraries/joomla/filesystem/file.php on line 630
It seems like when the PHP script trying to check this binary path whether exist or not then this PHP
open_basedir restricted access.
Either your current PHP
open_basedir path is not set correctly or the current web user doesn't have permission to access this path through PHP script.
Perhaps you can try consult with your webhosting provider again regarding this, if everything already set correctly but it still show out this warning, can you try request them temporary disable this PHP
open_basedir and see how it goes?