Hi @jyip_5228,

I just verified and the fix is still in place. We have seen connection issues in the past with the Mono framework due to how connection sharing is implemented in the mono framework. How often does this issue happen? If you restart the ProGet image, how long before you see the connection pool error?

Just to let you know, as part of ProGet 5.3.10 release, we shipped the ProGetCore container image as well.

You can follow the normal steps in the Linux and Docker Installation Guide to install/upgrade, but just use progetcore for the container instead of proget.

Aside from support for the Lucene-based Maven feed indexing (in progress), it seems to be feature complete. And of course, if there are problems, you can switch back to proget:5.3.10 or downgrade as needed (no database schema changes).

For example, docker pull proget.inedo.com/productimages/inedo/progetcore:5.3.10

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

I just wanted to let you know that this was released in 5.3.10. Please let us know if there are still any issues with this.

Thanks,
Rich

Hi @philippe-camelio_3885,

For an Ensure-PSModule command, here is what I'm thinking.

Ensure-PSModule {
   ModuleName: ...
   Version: ...
   MinVersion:...
   MaxVersion:...
   Force: false
   AllowClobber: false
   Repository: ... 
   Credential: ...(I expect this to be a ResourceCredential)
   Scope:...
   Properties: ... (any other additional properties to pass to Install-Module)
}

Where it just ensures that version (or within the min/max) is installed.

Am I understanding your request correctly?

Thanks,
Rich

Hi @viceice,

Thanks for the clarification on your environment! I see what is going on now. I have created a ticket, PG-1809, to track the fix for this. We expect this to be released in ProGet 5.3.11 which we are expecting to be released in September 11, 2020. Basically in that instance, we are not respecting the values within the X-Forwarded-* headers. I'll let you know if anything changes on the timeline.

Thanks,
Rich

Hi @viceice,

Can you please confirm your connector URL contains the https? How is ProGet setup? Is it installed on windows? Are you using IIS? It might be easier to add an SSL binding in IIS for this as well.

Thanks,
Rich

Hi @viceice,

Is your proxy passing X-Forwarded-Proto also? That should be passing https. You could try hard coding that in the proxy.

Thanks,
Rich

Hi @scroak_6473,

I just wanted to send over a few screenshots so you can see what is releasing tomorrow:

When you click on the layer digest on the Vulnerabilities, Repository Vulnerabilities, and Image Vulnerabilities pages, it now will show this modal dialog:

The List Repositories page now looks like this:

The All Tags for a Repository now looks like this:

The All Images for a Repository looks like this:

Thanks,
Rich

Hi @philippe-camelio_3885,

I wanted to let you know that this feature has been fixed and will be released in BuildMaster 6.2.17 which is due out tomorrow! I'll reply back if there are any changes to this schedule!

Thanks,
Rich

Hi @ludovic_2596,

Can you please give me your entire ProGet version? Also, what feed type are you having trouble deleteing packages from?

Thanks,
Rich

Hi @viceice,

You should be able to use http://localhost or http://<PROGET_IP_ADDRESS> in your connector without issue. Please give that a try and let me know if you run into any issues.

Thanks,
Rich

Hi @viceice,

ProGet free edition only supports self-connectors when they connect directly to ProGet. If you bypass the proxy, that should resolve the license violations for you.

Thanks,
Rich

Hi @jyip_5228,

That may be your issue. NuGet is currently on version 5.7. Could you please try upgrading your NuGet.exe and see if that fixes the issue?

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

We have finally been able to recreate this issue in our sandbox. We are currently looking into a fix, but we expect to have one in the next version of ProGet, 5.3.10. This looks to be an issue with the mono framework. We use mono runtime in our Docker images for ProGet. We are also going to be releasing a .Net Core based technical preview of ProGet Docker in version 5.3.10. This will be in addition to our standard mono based version. Our internal testing is going very well and it looks to have removed a lot of the gotchas that mono has.

Thanks,
Rich

Hi @jyip_5228,

For the v2/v3 thing. If the connector is using v3, there is potential to fall back to v2 if you have issues connecting over teh v3 API. That may be why we are seeing the v2 error.

To follow up on Alana's comment. You may need to use a tool like Wireshark, Fiddler, or Burp to catch the request and response traffic between nuget.exe and ProGet. That would be the only way to see the full response from ProGet and determine if it does attempt v3 before the v2 request.

One last question, what version of the nuget.exe are you using? Is it the latest version?

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

This is the first time we have heard any issues with this. We also have not been able to recreate this issue internally. Is there anything unique in your ProGet setup?

Thanks,
Rich

Hi @gravufo,

Thanks for following up. Glad to hear it is working!

Thanks,
Rich

Hi @jyip_5228,

Looking at your last connector error stack trace, it looks like your connector is using the NuGet v2 URL. Would you be able to send a screenshot of your NuGet connector configuration? NuGet has added limiting to their V2 API and I'm wondering if that is causing your issue.

Thanks,
Rich

Hi @gravufo,

After you enabled the Close Database Connections Early have you tried restarting your web server? You shouldn't have to restart it, but I have seen some issues when there were too many connections open prior to enabling the setting. Coudl you run the following SQL next time you have the issue?

SELECT DB_NAME(dbid) as DBName, COUNT(dbid) as NumberOfConnections, loginame as LoginName
FROM sys.sysprocesses
WHERE dbid > 0 AND DB_NAME(dbid) = 'ProGet'
GROUP BY dbid, loginame 

Thanks,
Rich

Hi @john-b_3261 ,

Can you please verify that your ProGet windows service is running and that the account the service is running under has access to those folders? Our nightly cleanup scheduled jobs typically clean up these folders./

Thanks,
Rich

Hi @jyip_5228,

Does this only happen with remote packages? Or do you see this with packages in ProGet as well? When this happens, if you run nuget locals all -clear on the same account that your build agent is running under, will it work then? I have seen some similar issues like this in the past, but typically they are caused by an issue with local caching in NuGet.

Thanks,
Rich