I am new to nexus and have installed my nexus manager on Linux box. I have added the remote proxy certificate from the Repositories->Settings page and have also setup the proxy settings, but still I am gettin gthe status in the repositories list as Online - Remote Connection Pending Is there anything else I need to do to access the remote maven-central repository?
Current Nexus 3 builds don't do the automatic connection test that Nexus 2 does. The status will change to online when the first outbound request is made to central. Try running a build against the server, that should do it.
If it doesn't, then you have a network problem, check the logs for details.
Related
So I currently am trying to get artifacts from repo.osegeo.org, which is a Nexus V3. I am having issues getting the artifacts to populate into my virtual repo that i created which holds the remote osegeo repo, libs release, libs snapshot and also my local repos. I have tried following the work around that is stated in this link below:
https://community.sonatype.com/t/maven-nexus-v3-remote-repository-integration-with-artifactory/2149
But I still have trouble actually getting the artifacts in my repo. Any ideas on what to do?
I suggest checking the following:
Connectivity - Is Artifactory able to reach the Nexus repository and vice versa?
The URL which is configured and if it is configured correctly.
Enable Bypass HEAD requests on the remote repository - Nexus can block HEAD requests and by default, Artifactory will create HEAD requests first before the GET requests to check if the artifact exists before attempting to resolve it.
If the Nexus repository requires authentication - Do not forget to put username and password under the advanced tab.
If there is also a reverse proxy in front of Nexus, you can try to bypass it and check if this works, if it does, the problem is probably the RP.
Check if the Maven client is configured correctly to work against the virtual repository (You didn't mention if you are able to publish or fetch from the local repository).
being behind a Nexus Repository Manager (3.4.x) I'm trying to setup a connection to the Confluent repository / Maven. I tried several steps, the most complete instructions I tried can be found here: Confluent Maven repository not working?
My workstation connects to a Nexus Repository Nexus. I have admin privileges on this Nexus.
Remote repository settings -- Nexus (1)
Further settings -- Nexus (2)
Using these settings I cannot connect to the Confluent repository. The Nexus works fine with other third party repositories.
I tried using the health check, but it just leaves me with 'Insufficient trend data' as shown here:
Insufficient trend Data -- Nexus (3)
I currently spend 1.5 days on this. I locally embedded some of the needed jars, but for production this is obviously not feasible.
What am I missing here? Is there a way to check availability of third party repositories from Nexus except Health Check? If you already have this setup running, I'm looking forward to your replies.
Manually added: kafka-avro-serializer, kafka-schema-registry-client
Currently unresolable: common-config
It looks like the URL you're pointing to packages.confluent.io/maven is returning a 404.
My guess is that this is causing Nexus to think that the downstream repository isn't working properly.
I'd contact the people who operate the confluent server and let them know the configuration in the documentation isn't working properly.
I work with an external company on a large project with hundreds of their own artifacts and plugins. Every developer can download them from remote repository only with per-user personal VPN.
I want to set up an intranet Nexus repository that mirrors remote repository for use with Jenkins. Problem is that there is no chance to have a VPN account for Nexus (neither Jenkins). So while every developer has these artifacts in a local repository, we need to manually update Jenkins' m2 repostiory, which is troublesome.
We've came to few ideas, bot none of these sound great:
Manually rsync my local repository to Jenkins' local repository
Mount Jenkins' local repository with sshfs to my .m2/repository so it gets updated on builds I do (so I don't have a real local repository on my disk, it's mounted)
Set up Nexus, create a user nexus on my machine and let him use my VPN connection as a proxy to remote repository (it creates a loop: my maven - Nexus - my VPN - remote)
How would you recommend to set up Nexus for Jenkins in that situation?
Ultimately you would save the external company a lot of traffic and money if you can proxy their Nexus repo with your own Nexus repo. This should provide enough reasons to set up a VPN user for Nexus. It can be very limited and have only access to the Nexus instance there and even be secured with a specific account in Nexus as well.
Every other workaround will ultimately be a hack. Worst case I would set up Nexus in your company and get it to access the external network with your user account, but a reasonable organization would understand the benefits of setting this up properly.
And if you are both using Nexus Professional you could use Smart Proxy for even better trusted connections and immediate updates of available components.
I have the latest version of Nexus installed and every time I add a new proxy repository that is https e.g. https://maven.atlassian.com/repository/public/ it marks it as Remote Automatically Blocked and Unavailable and Untrusted Remote. The problem is that it doesn't always work to re-specify the remote repository as http instead of https.
How can I fix/troubleshoot this?
You have to configure the trust store in the JVM running Nexus. In Nexus Pro this can be done via the user interface. In open source you have to do it manually on the command line. Its all documented in the book chapter about SSL.
Our project requires Nexus Professional to store and manage artefacts in a centralized repository hosted on Windows server. We were able to install Sonatype Nexus Professional in Windows workstation. However, I got stuck with Nexus' proxy configuration. A repository of type proxy is not able connect to the proxy server (i.e Proxy Blocked ).
Can some one help with configuration of proxy settings in Sonatype Nexus Professional in Windows?
Regs, Syam
This is HTTP error 407, indicating that your corporate http proxy server requires credentials but either none were supplied or incorrect ones were supplied.
Go to "administration/server" in the Nexus web UI, and configure both "default http proxy settings (optional)", and within that "authentication (optional)".
Most like your server is blocked to connect to the remote server via a proxy server or firewall.
Log into the server as the user running Nexus and confirm that you can ping the remote server first. Most likely that does not work.
Once you have fixed that it will either work or if required you will have to configure Nexus to connect via a proxy. This can be done on a Nexus global level as well as per repository.
I could ping to the https proxy server. We have configured the Proxy settings - Override the HTTP proxy setting of proxy repository configurations.
IAS server requires proxy authentication with error message "Access to the Web Proxy filter is denied". Hope this is due to proxy server configuration.
Error Message says:
Unexpected response code while executing GET method [repositoryId="central", requestPath="/.meta/prefixes.txt", remoteUrl="http://repo1.maven.org/maven2/.meta/prefixes.txt"].
Expected: "SUCCESS (200)". Received: 407 : Proxy Authentication Required
( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. )
Regards,
Syam
We have made the configuration updates as per your suggestion.
Some how my user credentials is getting locked out due to fact that login attempt failes multiple times at proxy server...
So will have to check with our manager & see if some thing can be done at the proxy server lever to over come the proxy authentication issue.
We will keep you updated. Ultimarly we are plaing for cenralies nexus server