none
Path to publish FFMPEG video files to Azure Blob Storage?

    Question

  • Hello there folks.

    Please kindly help me get out of a bad situation with a very very unhappy client. I am using FFMPEG based app to publish video files to Azure Blob storage, but the files are not going through the network. FFMPEG app has full access to firewall ports. FFMPEG communication shell show files are published without errors. A look at TCP connections shows the app is making connection with Azure account remote address 104.208.XXX.XX and remote port 443. However, it drops the connection and starts repeating attempts over and over. It will then time out after countless attempts and crash the app. Here is my publish point. Is this the correct publish point for this kind of connection? What is the proper connection string?:

    >>https://<account-name>.blob.core.windows.net/video/video.flv /DestKey:<account-storage-key>

    I have also tried <http://> without success. Same thing happens. It attempts connecting to remote address and port 80. Again, after several attempts it will timeout and crash. System is a Server 2008 R2 unit on-site, not VM. Your help is much appreciated. Thanks a lot!


    • Edited by CG-Guy Monday, January 25, 2016 1:05 AM
    Monday, January 25, 2016 1:02 AM

Answers

  • I would recommend that you test with the command line tools or powershell to ensure you can connect to and upload to Azure Blob storage first from the location. Here are links to use both, I prefer powershell myself but either should do the trick of proving/disproving a connection issue.

    PowerShell Method

    https://msdn.microsoft.com/en-us/library/dn749825.aspx

    AzCopy

    http://blogs.msdn.com/b/windowsazurestorage/archive/2012/12/03/azcopy-uploading-downloading-files-for-windows-azure-blobs.aspx

    Monday, January 25, 2016 9:08 PM

All replies

  • Hello CG-Guy,

    Thank you for contacting us. It looks like you are able to make connections with the Azure blob storage. If this is an intermittent issue, I would suspect there is some network issue at your end which is causing disconnections to both https and https connections. Did you check it from some other site?

    Please let me know if you have any queries.

    Regards,

    Dipin Mathew.

    Monday, January 25, 2016 6:16 PM
  • Thanks Mathew for the response!

    Yes I tried all other sites and networks and everything checked out. What surprises me is that TCP connections confirms that IT IS contacting the blob endpoint. I can see the stream populate to the top of TCP connections list in server resource monitor and then die off, only to resume again.  At this point, I can only conclude it comes down to my address path/structure becasue I am able to upload files from the ffmpeg app to FTP using this path:

    ftp://[user:password]@server[:port]/MyFolder/video/video.flv

    How do I achieve the same addressing structure in targeting Azure Blob storage?

    Thanks again!



    • Edited by CG-Guy Monday, January 25, 2016 8:58 PM
    Monday, January 25, 2016 8:45 PM
  • I would recommend that you test with the command line tools or powershell to ensure you can connect to and upload to Azure Blob storage first from the location. Here are links to use both, I prefer powershell myself but either should do the trick of proving/disproving a connection issue.

    PowerShell Method

    https://msdn.microsoft.com/en-us/library/dn749825.aspx

    AzCopy

    http://blogs.msdn.com/b/windowsazurestorage/archive/2012/12/03/azcopy-uploading-downloading-files-for-windows-azure-blobs.aspx

    Monday, January 25, 2016 9:08 PM
  • Awesome! Thanks a  lot Theo!!
    • Edited by CG-Guy Monday, January 25, 2016 10:06 PM
    Monday, January 25, 2016 9:28 PM