Creating a plan in Bamboo fails with Could not check if existing access key is valid: An error occurred while processing the request

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。

問題

When creating a new plan in Bamboo and selecting Bitbucket Server as the source repository it fails with below error:

 "Could not check if existing access key is valid: An error occurred while processing the request. Check the server logs for more information."

The following appears in Bitbucket Server's atlassian-bitbucket.log

2017-09-08 07:34:16,376 ERROR [http-nio-7990-exec-68] @1WEI6YBx454x4378x0 172.19.0.4 "POST /rest/ssh/1.0/keys HTTP/1.1" c.a.s.i.r.e.DefaultUnhandledExceptionMapperHelper Unhandled exception while processing REST request: "POST /rest/ssh/1.0/keys HTTP/1.1"
java.lang.NullPointerException: username
	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:226)
	at com.atlassian.bitbucket.user.NoSuchUserException.<init>(NoSuchUserException.java:20)
	at com.atlassian.bitbucket.internal.ssh.rest.SshKeysResource.getUser(SshKeysResource.java:207)
	at com.atlassian.bitbucket.internal.ssh.rest.SshKeysResource.addSshKey(SshKeysResource.java:131)

診断

環境

  • Bitbucket Server is running behind reverse-proxy such as Nginx

原因

The reverse proxy is forcing the HTTP Header for Authorization to an empty value, e.g. ""

proxy_set_header Authorization "";


ソリューション

Remove the Nginx configuration that sets the Authorization header for any proxied requests to " "


説明When a new plan in Bamboo is created by selecting the Bitbucket server as the source it fails with the error: "Could not check if existing access key is valid: An error occurred while processing the request. Check the server logs for more information." 
製品Bamboo,Bitbucket Server
最終更新日 2018 年 8 月 16 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.