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 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.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.