Navigating to a repository page shows "We couldn't find the page you requested" error pop up

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Navigating to a repository page shows "We couldn't find the page you requested" error popup

The following appears in the the browser developer tools console

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-2uOQtIsVzHr1u4XAN96+tcBOqQIM9wp6kovH43HGcfs='), or a nonce ('nonce-...') is required to enable inline execution.

Also, below in the reponse

{"message":"null for uri: https://URL/rest/api/1.0/projects/<PROJECT KEY>/repos/<reposlug>/undefined/rest/jira-integration/latest/servers","status-code":404}


Environment

  • This issue reproducible in Chrome and not in IE
  • A proxy like F5, nginx, HAproxy  and Apache infront of Bitbucket

We have noticed this when the extra Content Security Policy CSP headers are set in the proxy.

e.g. 

Content-Security-Policy:script-src 'self'; object-src 'self' 
  1. Remove the Content Security Policy settings from proxy
  2. Stop the atlbitbucket service, rename the application-data/plugins/.osgi-cache/felix directory to felix.bkp and then restart the service.



Last modified on Feb 1, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.