Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Not able to upload .iso file to asset directory on Proget

    Scheduled Pinned Locked Moved Support
    4 Posts 2 Posters 8 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      Sigve.opedal_6476
      last edited by

      Hi all.

      I'm trying to make a ISO file available through a asset directory, but when trying to upload (using browser), it always fails after 3% upload. The file is 1.3 GB in size. Uploading other files (300 MB .exe file) seems to work OK.

      I was able to work around this by compressing the .iso tile to a .zip file and then using the "Import from zip file" function. But uploading the .iso file directly does not work for me.

      We are on version 2025.18 running in docker on Linux. Here is the error from the log

      Failed to upload Standard_Edtn_2025_64Bit.ISO: Connection reset by peer
      
      Microsoft.AspNetCore.Connections.ConnectionResetException: Connection reset by peer
       ---> System.Net.Sockets.SocketException (104): Connection reset by peer
         --- End of inner exception stack trace ---
         at System.IO.Pipelines.Pipe.GetReadResult(ReadResult& result)
         at System.IO.Pipelines.Pipe.ReadAsync(CancellationToken token)
         at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken)
         at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
         at System.IO.Pipelines.PipeReader.CopyToAsyncCore[TStream](TStream destination, Func`4 writeAsync, CancellationToken cancellationToken)
         at Inedo.ProGet.WebApplication.FeedEndpoints.Assets.AssetContentHandler.UploadPartAsync(AhHttpContext context, WebApiContext apiContext, AssetFeed feed, String url) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E627829\Src\src\ProGet\WebApplication\FeedEndpoints\Assets\AssetContentHandler.cs:line 276
         at Inedo.ProGet.WebApplication.FeedEndpoints.Assets.AssetContentHandler.UploadPartAsync(AhHttpContext context, WebApiContext apiContext, AssetFeed feed, String url) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E627829\Src\src\ProGet\WebApplication\FeedEndpoints\Assets\AssetContentHandler.cs:line 291
         at Inedo.ProGet.WebApplication.FeedEndpoints.Assets.AssetContentHandler.UploadFileAsync(AhHttpContext context, WebApiContext apiContext, AssetFeed feed, String url, PutMode mode, Boolean ignoreContentType) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E627829\Src\src\ProGet\WebApplication\FeedEndpoints\Assets\AssetContentHandler.cs:line 168
         at Inedo.ProGet.WebApplication.FeedEndpoints.Assets.AssetFineUploadHandler.TryProcessRequestAsync(AhHttpContext context, WebApiContext apiContext, AssetFeed feed, String relativeUrl) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E627829\Src\src\ProGet\WebApplication\FeedEndpoints\Assets\AssetFineUploaderHandler.cs:line 29
      
      ::Asset Upload Error on 01/14/2026 11:24:44::
      
      1 Reply Last reply Reply Quote 0
      • Dan_WoolfD Offline
        Dan_Woolf inedo-engineer
        last edited by

        Hi @Sigve-opedal_6476,

        A 104 Socket Exception typically means that a firewall is blocking the upload of the file. Do you have a firewall sitting between your browser and your ProGet server?

        Thanks,
        Dan

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          Sigve.opedal_6476 @Dan_Woolf
          last edited by

          @Dan_Woolf yes, there is a firewall, but I’m able to upload other files from the same workstation, just not isos. My workaround was to zip the iso and then upload.

          1 Reply Last reply Reply Quote 0
          • Dan_WoolfD Offline
            Dan_Woolf inedo-engineer
            last edited by

            Hi @Sigve-opedal_6476,

            I just tested with a 3GB .iso file and could upload without issue. When you tested locally on the same workstation, did you use http://localhost or the normal URL? Chances are the normal URL will still go through the firewall, even when on the same workstation. I would check in with your IT team and see if they are blocking .iso upload files to your ProGet instance.

            Thanks,
            Dan

            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post
            Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation