Page MenuHomeFeedback Tracker

1.3.130 - Publishing not possible
Assigned, NormalPublic

Description

The problems we had 3 month ago are back. We updated Experimental in the last 6 Week without any issue.

Now 1.3 is out to public and its not possible to publish big Mods. I m tryed for 6 hours, now im bored.

DEFAULT      : Validating bundle...
DEFAULT      : Validating bundle successful
DEFAULT      : Publishing project to Workshop...
DEFAULT      : Validating bundle...
DEFAULT      : Validating bundle successful
DEFAULT      : Uploading status: 5%
DEFAULT      : Uploading status: 10%
DEFAULT      : Uploading status: 15%
DEFAULT      : Uploading status: 20%
DEFAULT      : Uploading status: 25%
DEFAULT      : Uploading status: 30%
DEFAULT      : Uploading status: 35%
DEFAULT      : Uploading status: 40%
DEFAULT      : Uploading status: 45%
BACKEND   (E): Curl error=Timeout was reached
BACKEND   (E): Http Error (TIMEOUT)
BACKEND   (E): [RestApi] ID:[13] TYPE:[EBREQ_WORKSHOP_UploadAssetFile] Timeout
DEFAULT      : Uploading status: 0%
DEFAULT      : Uploading status: 5%
DEFAULT      : Uploading status: 10%
DEFAULT      : Uploading status: 15%
DEFAULT      : Uploading status: 20%
DEFAULT      : Uploading status: 25%
DEFAULT      : Uploading status: 30%
DEFAULT      : Uploading status: 35%
DEFAULT      : Uploading status: 40%
DEFAULT      : Uploading status: 45%
BACKEND   (E): Curl error=Timeout was reached
BACKEND   (E): Http Error (TIMEOUT)
BACKEND   (E): [RestApi] ID:[14] TYPE:[EBREQ_WORKSHOP_UploadAssetFile] Timeout
DEFAULT      : Uploading status: 0%
DEFAULT      : Uploading status: 5%
DEFAULT      : Uploading status: 10%
DEFAULT      : Uploading status: 15%
DEFAULT      : Uploading status: 20%
DEFAULT      : Uploading status: 25%
DEFAULT      : Uploading status: 30%
DEFAULT      : Uploading status: 35%
DEFAULT      : Uploading status: 40%
DEFAULT      : Uploading status: 45%
BACKEND   (E): Curl error=Timeout was reached
BACKEND   (E): Http Error (TIMEOUT)
BACKEND   (E): [RestApi] ID:[15] TYPE:[EBREQ_WORKSHOP_UploadAssetFile] Timeout
DEFAULT      : Uploading status: 0%
DEFAULT      : Uploading status: 5%
DEFAULT      : Uploading status: 10%
DEFAULT      : Uploading status: 15%
DEFAULT      : Uploading status: 20%
DEFAULT      : Uploading status: 25%
DEFAULT      : Uploading status: 30%
DEFAULT      : Uploading status: 35%
DEFAULT      : Uploading status: 40%
DEFAULT      : Uploading status: 45%
BACKEND   (E): [RestApi] ID:[16] TYPE:[EBREQ_WORKSHOP_UploadAssetFile] Error Code:500 - Internal Server Error, apiCode="remoteRequestFailed", uid="1743108189904-527788", message="Internal Server Error"
DEFAULT   (E): Uploading failed! Reason: ""
BACKEND   (E): [RestApi] ID:[17] TYPE:[EBREQ_WORKSHOP_CancelAssetUpload] Error Code:401 - Unauthorized, apiCode="Unauthorized", uid="1743115632638-914948", message="Unauthorized"
DEFAULT      : Checking pending workshop invites...
DEFAULT      : Pending workshop invites request done (1)

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 11 x64
Category
General

Event Timeline

R34P3R created this task.Thu, Mar 27, 11:50 PM

btw. a few weeks ago, i read that workshop uploads can be resumed. This is not the case. It always starts from zero.

Geez changed the task status from New to Assigned.Fri, Mar 28, 10:46 AM
DarkWolf claimed this task.Fri, Mar 28, 9:03 PM
DarkWolf added a subscriber: DarkWolf.

i read that workshop uploads can be resumed. This is not the case. It always starts from zero.

you probably mean retry which is what happens in this case. it tries to publish file (i guess 2 GB) but fails so it needs to retry upload it which pushes it back to 0% since it needs to upload it again.

How many GB does your addon have and from what locality are you uploading?

@DarkWolf Hi, pack1 = 4.2GB and pack2 = 2.9GB. Im from DE and like written above, i did not have such issue for the last 6 weeks on experimental workshop.

@DarkWolf - Last night i uploaded a small Patch and all worked fine. So, no more Timeout.

For the Future: Each pack is splittet into 1.9GB Pack files. Maybe we can add a resume function like FTP has? So if a timeout reached, we can resume the current pack.