End of Central Directory record could not be found

Getting error: End of Central Directory record could not be found when trying to install a nuget package.

Product: ProGet
Version: 4.8.6

That sounds like what you're downloading isn't in fact a NuGet package, but you will need to supply a lot more context (error message, URLs involved, NuGet client version, etc).

We are seeing the same error.

We have an Azure-hosted Proget instance running version 4.8.2.

It is set up with LDAP Integration, but we authenticate using stored credentials in NuGet.config (sometimes we are prompted for credentials anyway though...).

We use only NuGet and Chocolatey feeds, but we get the same error for all feeds and all packages. The packages are valid NuGet and Chocolatey packages, and they work fine when retrieved from a locally hosted instance of Proget (4.7.11).

Through some experimentation, we've discovered that this works if we enable "Anonymous" access to "View and Download Packages", but not if only the actual users have this permission. So it smells like authorization issues, but it's not really an option for us to leave this open to "Anonymous" users. The credentials set up with LDAP work just fine when logging in to the Web UI.

We are not doing anything special with the requests, just regular

nuget install <packageid> -source https://<hostname>/nuget/<feed>

We run various versions of the NuGet client, for example 4.4.1.4656.

The complete error message is:

WARNING: Error downloading '<packageid>' from 'https://<hostname>/nuget/<feed>/package/<packageid>/<version>'
End of Central Directory record could not be found.

The values in brackets are of course just placeholders, like i mentioned this happens with all packages across all feeds.

It's probably worth mentioning that we also struggle with pushing packages to this Proget instance, unless we allow "Anonymous" access.

The error message we see with nuget push is simply

Response status code does not indicate success: 403 (Forbidden)

It does not seem to make any difference whether we require an API key for pushing packages or not.

We have tried the various solutions suggested in this thread, without luck:
https://inedo.com/support/questions/2319