It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

401 Unauthorized packages.atlassian.com while build Jira from source

Jira Build failed when trying to request follow file:

https://packages.atlassian.com/api/npm/atlassian-npm/@atlassian%2feslint-plugin-onready-checks/-/@atlassian%2feslint-plugin-onready-checks-1.0.1.tgz

Request failed \"401 Unauthorized\"

 

Could you help me with it? 

3 answers

I have the same problem.

Has someone a solution?

Try to build jira 8.0.2

I have the same issue any idea how to resolve this?

We're seeing the following warnings in our Nexus logs related to this issue (key parts highlighted):

2020-08-04 10:26:01 INFO [RepositoryStatusChecker-atlassian-public] org.sonatype.nexus.proxy.maven.maven2.M2Repository-atlassian-public - Next attempt to auto-unblock the "Atlassian Public" (id=atlassian-public) repository by checking its remote peer health will occur in 1 minute 20 seconds.
2020-08-04 10:26:03 WARN [proxy-3-thread-48] *UNKNOWN org.sonatype.nexus.proxy.maven.maven2.M2Repository - Remote peer of proxy repository "Atlassian Public" [id=atlassian-public] detected as healthy, un-blocking the proxy repository (it was AutoBlocked by Nexus).
2020-08-04 10:26:14 WARN [qtp1015146962-163] anonymous org.sonatype.nexus.proxy.maven.maven2.M2Repository - Remote peer of proxy repository "Atlassian Public" [id=atlassian-public] threw a org.sonatype.nexus.proxy.RemoteAuthenticationNeededException exception. Please set up authorization information for this repository. Auto-blocking this repository to prevent further connection-leaks and known-to-fail outbound connections until administrator fixes the problems, or Nexus detects remote repository as healthy. - Cause(s): Unauthorized

This appears to be because of the issue described above with some artifacts from this repository service being blocked with a 401 response.

This then triggers this Nexus issue (NEXUS-6515) which results in the Nexus service blocking all access to the Atlassian proxied repo ... which in turn gets unblocked because the top level repo is tested and found to be working ... until an artifact is requested when it gets a 401 response ... and round we go again.

The fix for the Nexus issue is to provide authentication credentials to the repository config.

Does anyone know how I can go about requesting credentials for packages.atlassian.com?

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you