I have two windows machines, one running Nexus OSS 3 and the other running ProGet.
Now I would like to create a nuget proxy repository in Nexus that points to one of the feeds/repositories I have in ProGet. I have followed this guide: nuget proxy repository where I basically copied the nuget.org-proxy proxy configuration that comes by default when you install Nexus OSS 3.
But I keep getting this error from command line
GET http://mynexus:8082/repository/tools-proxy/Packages(Id='x',Version='1.1.1')
GET http://mynexus:8082/repository/tools-proxy/Packages(Id='x',Version='1.1.1.0')
System.InvalidOperationException: Unable to find version '1.1.1' of package 'x'.
at NuGet.PackageHelper.ResolvePackage(IPackageRepository repository, String packageId, SemanticVersion version)
And the Nexus web log:
2016-05-25 20:13:28,252+0200 INFO [qtp1305498137-264] admin org.sonatype.nexus.rapture.internal.security.SessionServlet - Deleting session for user: admin
2016-05-25 20:13:32,971+0200 ERROR [qtp1305498137-282] *UNKNOWN org.sonatype.nexus.extdirect.internal.ExtDirectServlet - Failed to invoke action method: coreui_Repository.coreui_Repository_readStatus, java-method: org.sonatype.nexus.coreui.RepositoryComponent.readStatus
org.apache.shiro.authz.UnauthenticatedException: The current Subject is not authenticated. Access denied.
at org.apache.shiro.authz.aop.AuthenticatedAnnotationHandler.assertAuthorized(AuthenticatedAnnotationHandler.java:53) [na:na]
at org.a
When I run nuget install on a package X specifying the proxy repository URL as source:
nuget install x -Version 1.1.1 -Source http://mynexus:8082/repository/tools-proxy -Pre -NoCache -Verbosity detailed
That package indeed exists in the original ProGet feed and if I specify the direct/non-proxy feed instead the install works fine:
nuget install x -Version 1.1.1 -Source http://myproget:8181/repository/tools -Pre -NoCache -Verbosity detailed
GET http://myproget:8181/nuget/Tools/Packages(Id='x',Version='1.1.1')
GET http://myproget:8181/nuget/Tools/package/x/1.1.1
Installing 'x 1.1.1'.
Successfully installed 'x 1.1.1'.
I have tried with nuget version 2.8 and 3.4.
My ProGet server is configured with Built-In authentication:
Anonymous have download access:
Why do I get this access error when Anonymous have download access on my ProGet server?
Related
I have multiple SPM packages hosted on a private repo that only supports HTTP/2. The packages will clone to my local machine fine, but when trying to add them as a dependency to a project, the package will not resolve. Either it will spin forever, or I will receive an error that says.
An unknown error occurred.
SecureTransport error: connection closed via error (-1)
Any help is appreciated
Our .NET framework builds started failing after upgrading to VS2022 17.1.1 on Windows 10 (previously 17.0.6)
C:\Program Files\dotnet\sdk\6.0.201\NuGet.targets(130,5): error : Password decryption is not supported on .NET Core for this platform. The following feed uses an encrypted password: '<our repository>'. You can use a clear text password as a workaround.
The error is nuget password related yet we can run nuget restore commands fine.
It fails against our self hosted nuget repository that is password protected even though all our packages are already restored.
The fix is to remove and re-add the nuget repository with a clear text password
dotnet nuget remove source <repository-name>
dotnet nuget add source "https://<repository-url>/nuget" --name "<repository-name>" --password iloveponies --store-password-in-clear-text --username mylittlepony
I met the same error, but the most inner exception in the stack trace was: Windows Data Protection API (DPAPI) is not supported on this platform.
And due to update to new version, for me it looks like known issue: https://github.com/dotnet/sdk/issues/23498#issuecomment-1046937978
I've gone through almost everything related to installing sbt on Window on stackoverflow (there are quite a few people having the same problem with me). However, the answer seems unclear/unreproducible on my machine.
Here is what I did:
Download sbt-0.13.13 on this site
Install it successfully and set the PATH
Try sbt version to see if it is installed successfully. Error
returned (as at the end of this post)
A few things we should know:
I already have JDK
I don't use Proxy on my computer (tested with netsh winhttp show
proxy)
Someone said it is because sbt doesn't support ASCII character - but
the solution wasn't clear
problems summary
WARNINGS
module not found: org.fusesource.jansi#jansi;1.11
local: tried
C:\Users\buidu\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy.xml
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
C:\Users\buidu\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jansi.jar
==== Maven Central: tried
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
==== typesafe-ivy-releases: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
==== sbt-ivy-snapshots: tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
UNRESOLVED DEPENDENCIES
org.fusesource.jansi#jansi;1.11: not found
Server access Error: Permission denied: connect url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
Server access Error: Permission denied: connect url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
Server access Error: Permission denied: connect url=https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
Server access Error: Permission denied: connect url=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
You could try to configure the use of IPV4 (not IPV6), as described in the accepted answer for this question:
Error while importing sbt project , Server Access error, unresolved dependencies
setx _JAVA_OPTIONS -Djava.net.preferIPv4Stack=true
I was struggling with the same for a week. The only thing, that helped, was to uninstall sbt from the default location (c:\Program Files(x86)\sbt) and reinstall it to some location without spaces (I've installed it to d:\sbt).
Did you try taking a look in your sbt repositories file (likely to be c:\users\.sbt\repositories, and specifying http:// instead of https:// ?
I'm setting NuGet for deploy my projects in Nexus, when I execute the command 'nuget install ' i got this message:
Name User:INFO: An error occurred while loading packages from 'MyRepository' Could Not Ask for an entry in Interactive Mode NO. Provide the credentials for 'MyRepository'
How should I configure proxy, userLogin and password network, to make it work?
Recently I uninstalled SVN 1.7 from mac osx and installed SVN 1.6.23 following the instructions on this page: How do I uninstall subversion on OS X
'svn --version' runs well and says 1.6.23 is installed.
but when I run:
svn info http://www.domainname.com/svn/path_to_folder
it gives me following error:
http://www.domainname.com/svn/path_to_folder: (Not a valid URL)
svn: A problem occurred; see other errors for details
The command works fine on another mac which had SVN 1.6.18 preinstalled. So there is no problem with the server or the commands. Does anyone know what it could be?
You don't have any repository access module (RA) that can communicate with repositories using the HTTP protocol. If you only have ra_svn and ra_local you can only use svn: or file: URLs:
* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
- handles 'http' scheme
- handles 'https' scheme
You've apparently compiled your own binaries. The INSTALL file mentions this:
b. Serf library 0.3.0 or newer (http://code.google.com/p/serf/)
serf is a library for HTTP and WebDAV which is an alternative to
Neon for accessing Subversion repositories over http:// and https://
URLs. serf is designed as an asynchronous library which can take
advantage of HTTP pipelining, so ra_serf may be more efficient than
ra_neon and better for HTTP proxy caches. The serf library can be
found at:
http://code.google.com/p/serf/
In order to use ra_serf instead of ra_neon, you must install serf,
and run Subversion's ./configure with the argument --with-serf. (To
only use ra_serf and not ra_neon, you should also use
--without-neon.) If serf is installed in a non-standard place, you should use
--with-serf=/path/to/serf/install
instead. If you build with both ra_neon and ra_serf, Subversion
will use ra_neon by default; add "http-library = serf" to the
[global] section of your ~/.subversion/servers file to use ra_serf
instead.
For more information on serf and Subversion's ra_serf, see the file
subversion/libsvn_ra_serf/README.