Enhancement => More detail on: "The package was not found with the source(s) listed."

I am debugging Chocolatey failures under:

=> An AWS Windows instance (with instance role)
=> Running Teamcity
=> Calling Packer
=> against another AWS instance
=> Using a feed from another AWS instance

I'm sure there are others that could point to even deeper / more complex call stacks.

It would be amazingly helpful to know if:
*) The server exists / can be reached (very first part of URL)
*) The feed exists / can be reached (the entire url)
*) The credentials work or do not work
*) The package exists or does not exist
*) If a specific version was requested, it exists or does not

I am thinking maybe these could be checked in a catch block to give a better message - not necessarily checked and logged for each transaction.

So just try the package download, if it fails then attempt to get an idea of what parts of the above are good and where it most likely is broken.

I know it's not necessarily Chocolatey's job to validate the feed to this level - I'm just saying that when chocolatey is the last caller in a big management stack, it would be sublime if it told me where I screwed up or my environment failed :)

The issue names no files, tests, or entry points. Start by tracing the package-download failure path and compare the requested checks for server, feed, credentials, package, and version. Done means failed downloads report which part most likely caused the failure, with coverage for the relevant failure cases.

Written by the indexing model from the issue text.