or Create a profile

Home → Questions →

Nuget size limit using account feed

kwarr's Avatar

kwarr

24 Jan, 2024 05:10 PM

Hi,

We are running AppVeyor self-hosted on Windows. I'm trying to push a NuGet package using the account feed from the command line, but it fails with "500 (Internal Server Error)". I guess the problem is that its a huge package (~255MB), because I can push smaller packages this way.
Is it possible to increase the maximum allowed NuGet package size on self-hosted AppVeyor?

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

  • New Issue

  • Conversation Started

    A conversation has been started with the AppVeyor staff to resolve this discussion.

  • Close the discussion

Private Permissions

This discussion is private. Only you and AppVeyor support staff can see and reply to it.

Public Permissions

This discussion is public. Everyone can see and reply to it.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

14 Jan, 2025 05:24 PM Our Mac jobs are stopped again
09 Jan, 2025 06:59 PM "There was an error while trying to complete the current operation. Please contact AppVeyor Support."
09 Jan, 2025 06:40 AM Python 3.13.1
26 Dec, 2024 12:54 PM Projects quota exceeded for free account
23 Dec, 2024 06:52 PM How to cancel subscription

 

22 Dec, 2024 11:26 AM There was an error while trying to complete the current operation. Please contact AppVeyor support.
18 Dec, 2024 07:12 PM Error on any save
17 Dec, 2024 12:24 AM Cloning mercurial repository
06 Dec, 2024 05:20 PM Mac jobs stuck again
02 Dec, 2024 06:48 PM Cannot build .net9.0 with Visual Studio 2022 Image
02 Dec, 2024 06:46 PM Deployment with Octopus Deploy failing globally.