By Shannon Bryant on Wednesday, 08 November 2017
Posted in General
Likes 0
Views 1.8K
Votes 0
Hello - I am getting error message trying to post videos through EasySocial. The video is uploading, then error message: "Encoding your video... null%." I have error message in back end under "settings: "The path you specified is invalid. Please enter a different path to FFMpeg." I contacted host and they weren't able to help much. I do have FFMpeg in my CPanel files. I entered this path: /public_html/administrator/components/com_easysocial/includes/ffmpeg - and still receiving error when trying to upload videos. Thank You, Shannon
Hey Shannon,

Hm, you can't just put this path /public_html/administrator/components/com_easysocial/includes/ffmpeg from the Easysocial setting, because this FFmpeg is one of the open source library/tool that can decode and encode any video format to all the standard browser also can load this video.

So you have to consult with your webhosting provider whether your server did installed FFmpeg on your server? If installed, then consult with your webhosting provider what is the FFmpeg correct binary path from your server.

Once you get your server FFmpeg path, then you can enter into Easysocial setting.
·
Wednesday, 08 November 2017 11:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank You. I was able to open and find the correct binary path. I still need some help. Should I set the encoding or not? I had set the encoding to on and the video still did not load. I then turned the encoding to off, and videos are pending with this message: "Video listed under this section are queued to be encoded by the encoding library. Once these videos are processed, the system will send you a notification and it will be moved to the appropriate section." One of the videos pending has been pending for a couple hours now.
·
Thursday, 09 November 2017 12:07
·
0 Likes
·
0 Votes
·
0 Comments
·
You're welcome.

It seems like you already enter the correct FFmpeg path into Easysocial setting, can you check with your webhosting provider again and see whether your FFmpeg version using 2.8.x and above? Because our minimum requirement have to use FFmpeg version using 2.8.x and above.

If your server FFmpeg already using that higher version now, perhaps you can update your FTP user password at your first post so I can able to troubleshoot this issue? Because when i try to connect with your FTP account, i hitting this :

Command: PASS ************
Response: 530 Login authentication failed
Error: Critical error: Could not connect to server
·
Thursday, 09 November 2017 12:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank You. I was able to open and find the correct binary path. I still need some help. Should I set the encoding or not? I had set the encoding to on and the video still did not load. I then turned the encoding to off, and videos are pending with this message: "Video listed under this section are queued to be encoded by the encoding library. Once these videos are processed, the system will send you a notification and it will be moved to the appropriate section." One of the videos pending has been pending for a couple hours now.

What Path you put up
·
Tuesday, 20 April 2021 19:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey arustu,

What Path you put up

It doesn't have a consistent FFmpeg binary path, it depends on which directory path you install FFMpeg on your server.

It would be best if you can consult with the person who helps you set up FFmpeg on your server.

By the way, it looks like your account isn't tied up with any subscriptions on our site. Is there any mistake on our end? Would it be possible for you to contact us at https://crm.stackideas.com and provide us with the order reference and your username so that we can fix this up for you?

For now, I will be locked and marked this thread as resolved to avoid confusion in the future. Please start a new thread if you have any other issues in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.
·
Wednesday, 21 April 2021 11:27
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post