章鱼部署构建服务器似乎认为它需要与最初指示的不同的指纹

Question

我在尝试连接到部署目标上的侦听代理时遇到以下错误（混淆的指纹和服务器名称，别名涉及 AAAAA 和 BBBBB 的 2 个指纹）：

An error occurred when sending a request to 'https://TARGETSERVER:10933/', after the request began: The server at https://TARGETSERVER:10933/ presented an unexpected security certificate. We expected the server to present a certificate with the thumbprint 'AAAAA'. Instead, it presented a certificate with a thumbprint of 'BBBBB' and subject 'CN=Octopus Tentacle'. This usually happens when the client has been configured to expect the server to have the wrong certificate, or when the certificate on the server has been regenerated and the client has not been updated. It may also happen if someone is performing a man-in-the-middle attack on the remote machine, or if a proxy server is intercepting requests. Please check the certificate used on the server, and verify that the client has been configured correctly.

我检查了 Tentacle 配置，它显示如下：

{"Octopus": {
"Home": "/etc/octopus/Tentacle",
"Watchdog": {
  "Enabled": false,
  "Instances": "*",
  "Interval": 0
}
},
"Tentacle": {
"CertificateThumbprint": "BBBBB",
"Communication": {
  "TrustedOctopusServers": [
    {
      "Thumbprint": "AAAAA",
      "CommunicationStyle": 1,
      "Address": null,
      "Squid": null,
      "SubscriptionId": null
    }
  ]
},
"Deployment": {
  "ApplicationDirectory": "/home/Octopus/Applications"
},
"Services": {
  "ListenIP": null,
  "NoListen": false,
  "PortNumber": 10933
}
}
}

所以触手的指纹显示为 BBBBB，但错误响应似乎表明构建服务器期望 AAAAA 来自服务器，我应该怎么做才能使构建服务器（我没有易于访问）和目标服务器了解要交换的正确指纹？

Answer 1

We expected the server to present a certificate with the thumbprint 'AAAAA'. Instead, it presented a certificate with a thumbprint of 'BBBBB' and subject 'CN=Octopus Tentacle'.

如果指纹一直使用别名，这条消息让我觉得错误的值被添加到八达通目标页面上的指纹字段。

Target 页面（下面的屏幕截图）上通信部分的 Thumbprint 值应与 Tentacle 配置文件中的 BBBBB 值匹配。 AAAAA 值是八达通服务器证书指纹，Tentacle 需要知道它才能接受来自已知服务器的通信。 BBBBB 值是服务器需要知道的 Octopus Tentacle 证书指纹，以便它与已知目标进行通信。

章鱼部署构建服务器似乎认为它需要与最初指示的不同的指纹

Octopus-deploy build server seems to think that it needs different thumbprint than originally indicated

octopus-deploy