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

yes I am in the right instance (we have only one proget) so we found out our proget had some issues with the db and can't show all package in the ui now we delete from proget and reinstall everything and reindexing all packages I think this will work

This certainly used to work. It looks like nothing has changed on our end. I did some quick testing here with the latest NuGet client and can't seem to get it to send credentials with a push no matter what I do. Based on the error message you've pasted above, it looks like you're having the same issue (that message is only displayed if no auth credentials are present). You can double-check that this is happening in Fiddler, of course, but it looks like this is due to a change in behavior of NuGet.exe.

Nice read, I just passed this onto a friend who was doing some research on that. And he actually bought me lunch as I found it for him smile Thus let me rephrase that Thanks for lunch! bagkeecdckkdedbb

If you go to Admin->All Settings and change IntegratedAuthenticationEnabled to False and click Save, then it should use forms/basic authentication with LDAP as the user directory source. Note that if you are hosting the web site with IIS, you'll also have to enable Forms authentication and disable Windows authentication in there for the site. If you're using the integrated web server, it should just work. Once configured like this, you can supply the username and password in the url for the client. There is an example of this available if you click on the configuring Bower link visible on the page for any Bower package in ProGet. As far as I know, this is the only way to get it to work.

Under that error message, is a button [Assign Privileges]. So, if you click that button, a dialog will appear that allows you to assign which LDAP users and groups can use ProGet, once you switch to LDAP integration. So, just assign yourself as an administrator.

I believe the publish bug was fixed in the latest npm; you may want to update. Or, maybe it was broken in the latest npm (v2.5.0). In that case, you will want to downgrade. I believe we tested last against v2.2.0. I would also suggest to post this on the npm issue tracker, as will help raise the priority/importance of fixing and maintaining tests to work with repositories other than npmjs.org -