Skip to main content
Here are some common issues you may encounter when working with VOD and steps you can take to troubleshoot them.

​
503 error after transcoding

Possible cause: Upload has been interrupted by closing or reloading the window.
Suggested solution: Try uploading again and be careful not to interrupt the process. If the video is more than 500 MB, the upload will resume where it left off.

​
Video is not uploaded

Possible cause: Upload has been interrupted by closing or reloading the window.
Suggested solution: Try uploading again and be careful not to interrupt the process. If the video is more than 500 MB, the upload will resume where it left off. Possible cause: Not enough storage space to complete the upload.
Suggested solution: Confirm in the Storage statistics that you have used up your storage. Contact our support team to increase the storage space.

​
Upload to the Gcore Customer Portal is interrupted by a session timeout (force logout)

Possible cause: Video is too large to upload through UI.
Suggested solution:
  • Upload during late night or early morning hours when there is less load on the queue.
  • Upload a small batch of videos (e.g., 10 at a time).
  • Upload via API.

​
Upload is stuck in the Processed state for a long time

Possible cause: Processing queue is too long or loaded with large videos.
Suggested solution: Wait a while and then try uploading again.

​
Video is stuck in Error status

Possible cause: The original source file is internally inconsistent. Some videos change technical parameters in the middle of the file, for example pixel format, color range, codec parameters, or stream structure. A known example is a transition from yuv420p to yuvj420p near the end of the source. In such cases, reprocessing the same file usually does not help because the problem is already inside the uploaded source. Suggested solution:
  • Inspect the original file with a media analyzer such as ffprobe.
  • Verify that video parameters stay stable for the full duration of the file.
  • Re-export the file with consistent parameters from start to finish.
  • If the issue happens only at the end of the file, trim the broken segment and upload the corrected file again.
  • If the source was created from a live recording, check whether the source stream changed parameters during the broadcast.

​
Video returns an HTTP 404 error

A 404 error typically indicates that the transcoding process is still in progress (initial segments haven’t been generated yet), or the requested video asset does not exist. For a complete list of 404 error descriptions and other responses, please refer to our HTTP status codes guide.

​
Video segments have high latency or slow time-to-first-byte (TTFB)

Possible cause: Your account has low viewer traffic, so CDN edge servers rarely cache your video segments. Each request results in a cache miss and the edge must pull the segment from the origin server, which adds latency.
Suggested solution: This is expected behavior for accounts with low traffic. See Improve video delivery speed for low-traffic accounts for a full explanation and actionable steps, including enabling origin shielding and verifying cache TTL settings.

​
Source video issues

If your video is blurry, stuttering, or has no audio, first check the original file.
Suggested solution: Play the original source file on your local machine. If the issue is present there, you must correct the source file and re-upload it. Gcore Streaming preserves the quality of the input, so any defects in the source will be visible in the transcoded renditions. Also check that the source file keeps the same technical parameters for the whole duration. Mid-file changes of pixel format, color range, or codec parameters may cause transcoding to fail and place the video into Error status.