August 25, 2020 at 5:26 pm #37471
I have installed Symbiostock Video Diagnostic. I have run the test and no video is showing.
You only see a list of logs starting with: “ffmpeg version 2.8.2-static http://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2015 the FFmpeg developers \ n built with gcc 5.2.1 (Debian 5.2 .1-23) 20151028 \ n configuration: –enable-gpl – (…) ”
What are the specifications required for operation? I have a dedicated server (Ceontos 8, PHP 7.4, Nginx, Webmin-Virtualmin). Thank youAugust 26, 2020 at 6:22 pm #37486
Changing some configurations I was able to view the test image.August 26, 2020 at 8:54 pm #37488
RobinKeymasterAugust 28, 2020 at 3:51 am #37496
After a reboot of the server I tried to do the test again. You don’t see the movie. Do you have any idea what is causing the problem? Thank youAugust 28, 2020 at 7:25 pm #37498
What are the specifications required for operation? I have a dedicated server (Ceontos 8, PHP 7.4, Nginx, Webmin-Virtualmin). Thank youAugust 30, 2020 at 1:21 am #37505
Maybe I solved the problem by setting PHP FCGId threads to 8. (By default the value in Virtualmin is 4). Now I can see the test video. I hope it is the definitive solution.
I see the video with Chrome, while with Firefox I see the still image. What can it depend on?August 30, 2020 at 4:48 pm #37508
Thank you for your answer. In fact the test, after restarting the server, stopped working.
The NGINX server reports me the following error in the log file:
[error] 1820#0: *16 open() “/home/myvideoimage/public_html/wp-content/plugins/symbiostock-video-diagnostic/result.webm” failed (13: Permission denied), client: 220.127.116.11, server: myvideoimage.com, request: “GET /wp-content/plugins/symbiostock-video-diagnostic/result.webm HTTP/1.1”, host: “myvideoimage.com”, referrer: “https://myvideoimage.com/wp-admin/edit.php?post_type=product&page=manage_ss_settings&tab=videodiag”
Do you have any ideas on how to fix the video test problem?
Thank you very much.August 30, 2020 at 6:59 pm #37513
Hi paolo – as you can see within the error:
As previously suggested, it is still a permissions issue with your hosting environment.
Maybe do a search on google and see if anything comes up:
You must be logged in to reply to this topic.