Navigating to a repository page shows "We couldn't find the page you requested" error pop up
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および 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}
診断
環境
- 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'
ソリューション
- Remove the Content Security Policy settings from proxy
- Stop the atlbitbucket service, rename the
application-data/plugins/.osgi-cache/felix
directory tofelix.bkp
and then restart the service.
最終更新日: 2024 年 2 月 1 日
Powered by Confluence and Scroll Viewport.