Find your answers here.
This error occurs when the job took 3 times longer than our expected encoding time estimate. If you have submitted a very large or complex encoding task we would suggest you use our turbo encoding option to avoid this error.
The encoding.com system limits API requests per second depending on your plan type, if you receive the error message “421 Request Rate Over Limit” you have exceeded the limit included in your plan type. Please see www.encoding.com/signup for details about how many requests per second are included in your plan type.
The system could not resolve DNS name of the host specified in source of destination URL.
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.
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.
Check and see if the host is reachable. Can you reach another host? Check connection status and retry.
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).
The frame size you specified is too large. Please choose a smaller frame size and resubmit.
This maybe attributed to incorrect parameters such as bit_rate, rate, width or height . The specified parameters such as bitrate, audio sampling rate or audio channels number are not allowed for the specified codec. Also, often this error appears when specified bitrate is too low.
Some audio codecs (e.g. AAC or MPEG-Layer-3) have their own limitation for options values. When you leave these options blank in your API request, encoding.com will get them from the source file, and not always their set will be correct for particular codec. So, it's better to always set audio codec parameters explicitly.