@pariv_0352 oh interesting - for some reason I thought NuGet was used for C++ packages... I just did a quick look, and it doesn't look like vcpkg supports private registries; it only looks for package files on disk (share drive?) or in a Git repository: https://learn.microsoft.com/en-us/vcpkg/maintainers/registries So I guess the first step would be to ask the vcpkg team to create a package registry :)

Hi @pariv_0352, Thanks for clarifying; looking closer, ProGet requires that X-Forwarded-Host is simply a hostname. You're right, there is no "standard" for this, but that's what ProGet does for the time being.. and if the input is invalid, then you get the error you'll see. I would change your reverse-proxy header configuration to: X-Forwarded-Host: www.testdomain.com X-Forwarded-Port: 82 Hope that helps, Steve

Hi @pariv_0352 We've updated ProGet 2022.6 to be more permissive and allow the . in non-semver2 NuGet versions. v2022.6 will be released on Friday. Thank you!

Hi @pariv_0352, I was able to fix the issue, PG-2160, and it will be released next week on ProGet 2022.2. If you would like to use the fix earlier, you can install a pre-release version of PrGet by installing ProGet 2022.0.2-CI.7 or higher. We have a walk-through on how to install prerelease products in our documentation. Please let me know if you have any questions. Thanks, Rich