Home → Problems →

[Self-Hosted] Failed to read artifact stream

• Edit

mikeb

13 Jan, 2026 12:27 AM

Hi guys,

I've setup the self hosted appveyor server as my build times were exceeding 60 minutes. Everything came together well until I tried to deploy a GitHub release:

Uploading "XXXXXX-2.6.19.tar.gz" to release assets...Failed to read artifact stream: An error occurred while sending the request.

The deployment config and build script is the same as on the cloud hosted version of appveyor. Artifacts are added using Push-AppveyorArtifact and contain both a filename and deployment name, and show up as artifacts in the build.

I checked and the artifacts exist on disk, and I even tried setting permissions on the folders to "Full read/write" as well as for the appveyor user but still no go.

Any ideas on what would cause this? I'm still scratching my head.

1. Support Staff 1 Posted by Feodor Fitsner on 13 Jan, 2026 03:27 AM

   

   Hi Mike,

   What version of AppVeyor Server is that?
   Can you download that asset from AppVeyor UI?

   • Edit

2. 2 Posted by mikeb on 14 Jan, 2026 12:42 AM

   

   Hi Feodor - it's 7.0.3212 (It's a fresh installation). Yes, I can download the artifacts from the UI.

   I also tried regenerating the GitHub token to see if it was an access issue, but that didn't do anything. I can't tell if the error indicates it can't read the artifact, or if it can't send it to GitHub. The release gets created, but there are no artifacts present of course.

   Creating "Binner v2.6.20" release for repository "replaysMike/Binner" tag "v2.6.20" commit "fa38c8cff5de351617b5a589bcc6205aec2e69b2"...OK
   Uploading "Binner_linux-arm-2.6.20.tar.gz" to release assets...Failed to read artifact stream: An error occurred while sending the request.
   

   • Edit