Home > Return Code > Error Deploying Artifact Failed To Transfer File Return Code Is 401

Error Deploying Artifact Failed To Transfer File Return Code Is 401


May be the solution is here http://stackoverflow.com/questions/1650596/how-do-i-import-a-new-java-ca-cert-without-using-the-keytool-command-line-utilit Hide Permalink Rich Seddon added a comment - 04/15/13 06:09 PM An SSL certificate error will not give you a 401 response. I never succeed in thickening sauces with pasta water. https://wiki.openmrs.org/display/docs/Release+Process When you are deploying a module to nexus repository using: mvn clean deploy command You may get an error message like: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project...Return If the server is using https but the URL in your POM is http, you might get 401 as well. Source

Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] According to this sonatype support page: "If you are receiving a 401 it is because maven is sending the wrong login credentials, To solve this you need to add a server for the module repo by adding the following with Nexus repository credentials to the list of servers in the file /M2_HOME/settings.xml. I've been taking a lot from SO recently, so I'm glad that I've been able to help someone else, your question has been the first time someone's accepted my answer! –John You also get an error (and off the top of my head is also a 401) if you try to publish something to a releases repository and that version already exists here

Error Deploying Artifact Failed To Transfer File Return Code Is 401

What would be your next deduction in this game of Minesweeper? So when you get a 401 on deploying artifacts to Nexus, you need to make sure you provide correct credentials. at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1016) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1004) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:895) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:522) at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:331) ... 26 more Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. You will get a 401 Unauthorized error if you supply the wrong credentials (password etc).

You should not need to do that. –Manfred Moser Dec 16 '13 at 16:58 Oh my good! , you save my night , thx it works perfectly –Adnen Chouibi I think in my case it is due to a self-signed ssl (apache inverse proxy) used in my nexus. Thanks for the support! Maven Deploy Username Password XBN-Java is the foundation of Codelet (http://codelet.aliteralmind.com). Lesser General Public License (LGPL) version 3.0 https://www.gnu.org/licenses/lgpl-3.0.txt Apache Software License (ASL) version 2.0 http://www.apache.org/licenses/LICENSE-2.0.txt Jeff

I am just hitting wall after wall with Maven. Excerpt from pom.xml: ServerA2 ServerA2-releases ServerA2 ServerA2-snapshots Excerpt from settings.xml: admin XXX central posted 2 years ago Can you login to Nexus on your machine and try to upload an artifact to http://localhost:8081/nexus/content/repositories/snapshots/org/bhavesh/my-test? http://stackoverflow.com/questions/20570009/deploying-artifacts-in-nexus-from-maven-gives-error-return-code-is-401 Make sure your username/password is correct by logging into the Nexus UI.

Same for snapshots. Failed To Deploy Artifacts Could Not Transfer Artifact Return Code Is 400 Reasonphrase Bad Request Thanks again for the post. share|improve this answer answered Jan 28 '16 at 13:30 Alberto M 445522 1 Hint: many curl implementations require options to come before the URL. Any ideas would be appreciated.

Maven Error Code 401 Unauthorized

See here for an overview: http://www.sonatype.com/books/nexus-book/reference/confignx-sect-managing-privs.html Hide Permalink Senthil Kumar Chandran added a comment - 06/05/12 10:33 AM Got it! http://stackoverflow.com/questions/14023836/now-getting-401-unauthorized-in-jenkins-when-deploying-artifact-to-archiva-maven I edited the question to reflect the changes already! Error Deploying Artifact Failed To Transfer File Return Code Is 401 I successfully logged in and out of the sonatype.org website, using the user/pass in settings.xml. Artifactory Return Code Is: 401, Reasonphrase: Unauthorized In Nexus, this means the Nexus server asks you log in first before doing things like deploying artifacts.

Very frustrating. http://juicecoms.com/return-code/eza1735i-std-return-code-10234-error-code-00010.html See here for an overview: http://www.sonatype.com/books/nexus-book/reference/confignx-sect-managing-privs.html Show Rich Seddon added a comment - 06/04/12 01:13 PM Nexus doesn't ship with fine grained control of repositories, but you can easily add privileges Using the "-s" option in my experience is necessary in a Maven build in order to be absolutely sure. Make sure you have configured a server in settings.xml and that the server id is identical to the distribution repository id in pom.xml. Error Deploying Artifact Failed To Transfer File Return Code Is 400

I think in my case it is due to a self-signed ssl (apache inverse proxy) used in my nexus. Run mvn with -e -X options and check the debug output. I wrote the question :) –aliteralmind Jul 18 '14 at 17:56 Great.. have a peek here How can "USB stick" online identification possibly work?

Return code is: 401, ReasonPhrase: Unauthorized. Mng-4469 If you're certain Maven is using the expected password and you're still getting a 401 error then perhaps the password has been changed on the server? asked 4 years ago viewed 20507 times active 3 years ago Linked 50 Why am I getting a “401 Unauthorized” error in Maven? 3 setting different maven mirror per project 1

Atlassian Log In Unable to deploy artifacts to Nexus Development nexus Tags: # mogoodrich (Mark Goodrich) 2015-08-06 13:14:31 UTC #1 Anyone know if there were any changes to the mavenrepo.openmrs.org credentials

I tested the call with curl curl -u username:password http://url/artifactory/libs-snapshot-local/com/myproject/api/1.0-SNAPSHOT/api-1.0-20160128.114425-1.jar --request PUT --data target/api-1.0-SNAPSHOT.jar and I got the error: { "errors" : [ { "status" : 401, "message" : "Artifactory configured The Artifact was uploaded successfully But I encounter the following error when I set the version in pom.xml to 1.0-SNAPSHOT Output from mvn clean deploy -X -e [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) Apparently I have specified -DrepositoryID (note ID in capital) instead of -DrepositoryId. Error Deploying Artifact Failed To Transfer File Return Code Is 500 Remember, nothing changed in Archiva, the OS, or the project.

So you might find that by publishing from the command line it works, but then when you do it from a script it fails (because it didn't exist in the repository Digital Hardness of Integers TeXForm handling of derivative higher than two more hot questions question feed lang-xml about us tour help blog chat data legal privacy policy work here advertising info What's the point of repeating an email address in "The Envelope" and the "The Header"? Check This Out At what point is brevity no longer a virtue?

intelligence agencies claim that Russia was behind the DNC hack? It will tell you which repositoryId it is using: [DEBUG] (f) offline = false [DEBUG] (f) packaging = exe [DEBUG] (f) pomFile = c:\temp\build-test\pom.xml [DEBUG] (f) project = MavenProject: org.apache.maven:standalone-pom:1 @ I also used the help:effective-settings to print out the settings and it's as I was expecting and is using the correct file. –Oggie Dec 29 '12 at 19:59 I We run Archiva on the same machine as UberSVN, and our Jenkins sits inside UberSVN as a plugin.

This has a 'Repository ID' field which was set to the wrong value. I ran with -X option and it looks ok to me. [DEBUG] Reading global settings from C:\maven\apache-maven-3.2.1\bin\..\conf\settings.xml [DEBUG] Reading user settings from C:\Users\Bob\.m2\settings.xml [DEBUG] Using local repository at C:\Users\Bob\.m2\repository [DEBUG] Using A sonatype support person also recommended that I remove the block from my POM (it's only there because it's in the one from ez-vcard, which is what I started with) But for some reason i get the same result, i could deploy to releases but still not to snapshots.

I even changed the username to that of the admin user... Although it said that it was an authentication error actually it got fixed doing a "rebuild metadata" in the nexus repository. Thanks to everyone for their help.