Connection Errors

Thinking of using HTTPS as your source locations? No problemo.

All you need to do is specify the port in which we access your file at. Connections via HTTPS will use port 443 by default. If you'd like to specify a different port, add it to then end of your URL.

Example:

HTTPS://www.xyz.com:[port]/files/input.mov

<-- Hide

This error is returned when our system is not able to send the video to the FTP/SFTP destination you specified.  Please verify the username, password, permissions, and complete directory path in a FTP client prior to adding it to our system.

<-- Hide

For VBScript output to work, you may need to percent-encode the destination path twice. Like this.

Regular FTP path:
ftp://username@yourcompany.com:password@server.com/file.m3u8?passive=yes

Single URL (%) encoded - used for some standard FTP configurations
ftp://username%40yourcompany.com:password@server.com/file.m3u8?passive=yes

Double URL (%) encoded - used for VBScript FTP
ftp%3A%2F%2Fusername%2540yourcompany%3Apassword%40server.com%2Ffile.m3u8%3Fpassive%3Dyes

<-- Hide

We test video playback on a variety of devices, from Mac and Windows PCs, to all the various mobile phone platforms available today. One critical issue that comes up often is that the hosting server has not set the MIME types for the video type. A typical error message for this would be "unknown application/octet-stream". Here is a list of many common formats we encounter.

Video Type	Extension	MIME Type
Flash	.flv	video/x-flv
MPEG-4	.mp4	video/mp4
iPhone Index	.m3u8	application/x-mpegURL
iPhone Segment	.ts	video/MP2T
3GP Mobile	.3gp	video/3gpp
QuickTime	.mov	video/quicktime
A/V Interleave	.avi	video/x-msvideo
Windows Media	.wmv	video/x-ms-wmv

IMPORTANT: You will need to configure your ftp server to these MIME types for them to be properly recognized by their respective playback devices.

<-- Hide

The most common error is specifying incorrect SFTP URLs for files located in your home directory. You must specify full directory path in your URL: sftp://user:password@your-host.com/home/user/video/file.ext Another common issue is missing files! Check the file is there, and the path for encoding.com is correct. If you continue to experience issues, don't hesitate to email helpdesk@encoding.com.

<-- Hide

The Error 425 is most often displayed when you have attempted to provide encoding.com a source FTP location that only supports Passive FTP mode. If you are using a watch folder, check the box that says "Passive FTP Mode" in the ftp watch folder set up If you are adding an individual file through the web interface or API you can append ?passive=yes to the end of your source or destination string: ftp://user:pass@ftphost.tld/path/to/your/file.ext?passive=yes <-- Hide

'Download error: bind(port=0) failed: Cannot assign requested address' is an error which most commonly occurs when you have attempted to provide encoding.com a source FTP location that only supports Passive FTP mode. So, If you are using a watch folder, check the box that says "Passive FTP Mode" in the ftp watch folder set up If you are adding an individual file through the web interface or API you can append ?passive=yes to the end of your source or destination string: Example: ftp://user:pass@ftphost.tld/path/to/your/file.ext?passive=yes <-- Hide

If you've received this error, then the wrong UserID is matched with the wrong UserKey. Please log into your user account to verify that you are using the correct key.

<-- Hide

This error is returned when you are using Amazon S3 as a source media location and the Amazon key you have provided does not exist.  Please see our collection of articles on Amazon ACL permissions with encoding.com as well as Amazon's own article on the topic. <-- Hide

The system could not resolve DNS name of the host specified in source of destination URL. <-- Hide

For the HTTP source – the server returns 404 not found error. This error occurs after communication with the server can be established, but it cannot locate the requested files. Please check your paths and try again. <-- Hide

For the HTTP source: the server returns 401 not authorized error. It may be that the wrong username/password are specified. Please check your credentials and try again. <-- Hide

Check and see if the host is reachable. Can you reach another host? Check connection status and retry. <-- Hide

This error occurs when the task hangs at the encoding stage, and its execution time tops the estimated time by (n) seconds (the value can vary). <-- Hide

Assume you specified some notification URL in your AddMedia API request:

<notify>http://your.server.com/Notify.aspx</notify>

But you see nothing happens. Most often the problem is that your ASP.NET server drops notification HTTP request because it considers the request is 'dangerous'. To fix this you should set validaterequest = false for this page.

<-- Hide