That error will occur if the Amazon extension is not loaded. If you haven't already, you can download the extension form Admin > Extensions, or just follow the manual installation instructions (i.e. put it in the Extensions folder on the disk).

Hello Aris, If you click on the release number (the leftmost column) the user that created the release is displayed in the Details section.

Hello Mario, I've added resetadminpassword to ProGet.Service.exe for the next minor release (4.7.10) - PG-1009 For now, you can reset the password in the database to Admin by setting the Salt_Bytes and Password_Bytes to 0x26CF0B87A338C08CA30F and 0x5868049613BC1ED1E4E3C2E404D8B85684B53263 respectively.

Ok, I noticed that in your log, npm isn't authenticating. Is the anonymous user allowed to access the feed in ProGet?

If you upgrade to the latest v5.6 (currently 5.6.11), then it should work OK!

Hello Michael, NPM feeds don't currently support an API key, but you can share a single ProGet user between all of the users who need to upload to the feed to simulate the same thing. The Publish Packages task group on the NPM feed is all you need to upload a package. If you want to replace an already-uploaded package, you need the Overwrite Package task, which is available on the Administer and Manage Feed task groups by default, but you can create a new task group with just Overwrite Package on the Customize Tasks page (/administration/security/customize-tasks).

Hello Matt, It looks like the PostgreSQL version of Feeds_SetLastSyncDate was not updated when the MSSQL version was. I've logged this as PG-1006 and it will be fixed in the next version of ProGet.

This must be it, redownload solved it. I downloaded 5.6.11 sometime on Apr 4.

This means that your computer cannot connect to My.Inedo for alicense key. Please request one by logging into my.inedo.com.

A vulnerability version range can be: the literal string (any) empty string (equivalent to (any)) single single, single single, single, single single, single, single, single etc. A single vulnerability version range can be: version >version >=version <version <=version >version <version >=version <version >version <=version >=version <=version The format of version is defined by the feed type.

Version 1.1.0 of the upack command line tool is now available from http://inedo.com/support/documentation/proget/reference/upack. The chocolatey version has been submitted and will be available once it's approved.

There's a bug we haven't been able to figure out where the Linux version of ProGet doesn't respond to requests for URLs with colons in them.

I see you also opened a ticket, so it's going to be best to collaborate on that instead. But I will respond here as well in case anyone finds this... Unless you're entirely distributing third-party, vendor-provided packages (i.e. you don't move them through a pipeline like Dev > Test > Prod), then BuildMaster is quite important to manage this pipeline , especially in regulated environments. Regarding HA, it's best to first come up with a list of questions you'd like us to help with, and then we can research and figure out how best to help. For example, we can't really help on selecting or configuring a particular brand of load balancer; that's something generally done by your IT/NetOps folks, but we could point you to Microsoft's NLB documentation (which has step-by-step instructions on how to set it up).

Configuration file versions and database change scripts must be tied to a specific release number, so we create 0.0.0 to associate those. It might be best just to purge that release if you don't really use it.

Perfect. Now it works as expected :-)

That is good news, i was able to bypass this though by setting the service to run as an outgoing trust user which then allowed me set the LDAP to the other domain.

This appears to be an internal Java error, indicating that the package cannot be bufered due to low process memory. So, I would increase the memory of your Java/Jenkin instance. You can use the -Xmx1024m option to give 1GB of memory to your application. This will increase the amount of data you can store in memory.

That fixed it, argh! Been messing with this for hours! Thanks!

It's cool, I switched to global template to be called. It works fine. Thanks!

I agree that it is a poor solution, but we do not have very many good solutions for this. Docker itself does not support prefixing private repositories; everything is assumed to be hosted in the same manner as the public registry (ie, absolute URL path from the server root), and assuming all /v2/ requests are Docker without some other declaration of intent in the request didn't seem good either. That said, if there's no collisions with anything else using that URL, we can change the default behavior.