What happens when my episode fails to import?

If an episode fails to import, it may be for one of a few reasons:

• The file is not a supported type. Pinecast only accepts MP3, AAC, and M4A files during import.

• The file was served with a bad Content-Type. The Content-Type of a file is the file type of a file on the internet, similar to a file extension (like .mp3). Content-Types are necessary because URLs do not always have file extensions. If a server does not send a Content-Type or the Content-Type of a file is ambiguous, the file will not be imported.

• The server responded with too many redirects. The importer will follow up to three redirects. Any 3XX status code with a Location header will be treated as a redirect.

• The server responded with a non-200 status code. If your server does not respond with a 200 Okay response, Pinecast will consider the download a failure. The includes interrupted requests, which may not have status codes.

• The server's response was interrupted. If the connection to the remote server is interrupted, the import will fail.

• The server took too long to respond. We expect that your server can send your file in less than a few minutes. If it takes longer than two minutes to send an MP3 file, the episode may fail to import.

• The file is larger than 256MB. Files larger than 256MB cannot be imported.

• There was a problem transferring the file. DNS issues, TCP/UDP connection issues, HTTPS connection and certificate issues, and other problems sending files from the source server to Pinecast can cause the import to fail.

Other problems may lie on the other end:

• The remote server may throttle Pinecast for requesting too many files too quickly.

• The remote server may have blocked Pinecast from importing content.

If your episode has failed to import, please get in touch so we can investigate what might have happened.