Hello, Thank you for your message.
I have switched off SSL( 443 port ) and commented the lines below in httpd .conf in my invenio server, restart httpd. But I still got the same error. Include /opt/invenio/etc/apache/invenio-apache-vhost.conf #Include /opt/invenio/etc/apache/invenio-apache-vhost-ssl.conf TraceEnable off #SSLProtocol all -SSLv2 It seems the flash plugin used to upload the file have not aware of uploading file. There is a message in apache.log tail -f /opt/invenio/var/log/apache.log 202.122.32.43 - - [05/Feb/2013:11:24:49 +0800] "POST /submit/upload_video HTTP/1.1" 403 8434 "-" "Shockwave Flash" 4708858 I really do not know what cause the problem. I have no idea. Any other clue? Thanks a lot, Regards, Lanxin ________________________________________ From: Jerome Caffaro Sent: 01 February 2013 11:51 To: Lanxin Ma Cc: Samuele Kaplun; project-invenio-general (Invenio users) Subject: Re: vedio upload Dear Lanxin, On 01/22/2013 03:26 PM, Lanxin Ma wrote: > However, when I do demo video submission, it still give the error > > Your video could not be processed. The file might be corrupted or its > codec(s) might not be supported by Invenio. Please verify your video or see > the video submission guidelines. > > In order to debug the error, I would see log messsage in invenio.log. But I > do not find any messeges about this error in log file. If there is no trace of error in any log file then it might mean that the upload tool has not even considered sending the file. This can happen for eg. when using a self-signed or invalid SSL certificate, typically on a test/development server. In these cases although you have instructed your browser to trust the certificate (after passing all the safety dialogs "This certificate is not valid"->"Are you sure, or not?"->"Really?"->"This is not recommended, continue anyway", etc.) in order to login, the Flash plugin used to upload the file to the server might not have been made aware of that choice. To solve this you would have to trust the self-signed certificate at the level of your session/system (on the client, not the server). The procedure varies based on the operating system. You could also alternatively switch off SSL in your Invenio installation (provided that this is a test machine on which no confidential information will transit, including real passwords). The best would be to have a certificate signed by a real authority (and trusted by your system). Once your video will be uploaded you will get into the real hard-core BibEncode and ffmpeg stuff ;-) I also wanted to bring to your attention the following additional doc on BibEncode: <https://indico.cern.ch/contributionDisplay.py?contribId=9&confId=183318> Best regards -- Jerome Caffaro ** CERN Document Server ** <http://cds.cern.ch/>
