Thanks for the investigation- we'll see if we can get this configurable in the next release, and possibly look into seeing if we can avoid clobbering web.config on upgrades.

We need to add that.. but to back-up ProGet, you just need to Back-up the Database and the Packages directory (the path is listed on each feed, and is in the All Settings under Admin). Then restore the database, and the files on a new server.

Yes - that worked for me. Thank you.

Sorry yes, I meant ProGet (though the implementations are actually the same :)) Anyway, the way that it's currently implemented does require the machine to be a part of the domain. We are aware that this is not ideal and will likely change the way LDAP is queried to make more settings configurable in a future version.

Yes, http://localhost:81/bower/bower/packages/croc.webClient returns a good json: {"name":"croc.webClient","url":"http://myrepo/webclient-dist.git","hits":0}

Regarding the first error – that sort of thing should only happen if the connector returns invalid data. What is the URL of the bower connector? For the registration, it looks like it’s just an HTTP 401. See this article for info about Bower & authentication in ProGet: http://inedo.com/support/kb/1095/introducing-bower-support-for-proget

i will try to submit this to avira. maybe it would be nice to report it to them too since it is your product that gets blocked! this could lead to misunderstandings.

Answering my own question using this solution. Hope anyone else who has to do this with Ruby will find this helpful: require 'rubygems' require 'httpclient' #latest, with rubyntlm also installed http_client = HTTPClient.new http_client.set_auth(nil, '<domain>\<username>', '<password>') local_file = File.new("C:\\temp\\<package>.<version>.nupkg", "wb") local_file.write( http_client.get_content("https://<server>/nuget/<feed>/package/<package>/<version>") ) -/- flagellum

Do you have any connector filters? If so, try removing those to see if it works. Also, try using the non-SSL URL, i.e. http://www.nuget.org/api/v2 and see if that works. I would also double-check the proxy configuration if you have one set up. If so, see what the message when “Test Proxy Connection” is clicked.

Thanks- we'll try to expose these properties in the next release.

Note: we have now scheduled this feature for v3.6

I can see how to add named groups, but "Domain Users", "Everyone", "Authentication Users" don't seem to be recognized by the add users window. I think we are just going to use a large organizational group that covers most everyone so true anonymous access isn't needed anymore. Thanks!

Activation invalidates when the MachineUUID (MAC Address + CPU-ID) changes; in some virtual hosts (VM Ware), we've seen the MAC change randomly... but it's a setting that you can control.

Because Chocolatey uses nuget.exe behind the scenes, you can just specify your authentication in the same manner., in the configuration file.

Upgrading isn't a practical nor helpful suggestion. I guess I'll be looking elsewhere for a feed server.

Looks great. Thanks!

Ah, I see; please note that we do not support v1 feeds (they were already obsolete when we build ProGet in 2012) and we have no intention to. Suggest you push packages from TeamCity to ProGet instead.

I like the web page solution better than my SQL solution. :) Let's go with that.

The installed express database by default is at localhost\PROGET (i.e. machine_name\instance_name). To switch, simply backup and restore the database into the new instance, and update the connection string in web_appSettings.config under the web installation path, and ProGet.Service.exe.config under the service install path.

Ok thanks for the Info