Self Sign Certificate Issue Octopus

[sbindra]

Hi Dear

I am encountering a very strange error while running the build and at the step pushing packages to Octopus Server.

Full Error:-

Starting: Package

==============================================================================

Task : Package Application

Description : Package your application into a NuPkg or Zip file.

Version : 3.0.222

Author : Octopus Deploy

Help : Version: 3.0.222. More Information

==============================================================================

Attempting to contact https://g.octopushq.com to find latest CLI tools

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

(node:18852) Warning: Use Cipheriv for counter mode of aes-256-ctr

##[error]Error: self signed certificate in certificate chain

##[error]Failed to execute octo pack command. self signed certificate in certificate chain

We areusing Azure DevOps Server 2020 (on Priem) and have self hosted windows build agents on them. It fails when we push the packages to Octopus, Re-running it again works fine 6 out of 10 times.

Also tried downgrading version of Push Pacakge step to “2” from 3 and 4. that works as well.

Any suggestion to fix this.

Thanks
Sunil Bindra

[Justin_Walsh]

Hi Sunil,

Thanks for reaching out, and sorry to hear you’re having issues here. When this fails, is it always on a single build agent? If it works on retry, are you getting the same agent or a different one?

If it’s isolated to a single build agent from the pool, I would perhaps look at the configuration there, compared to your other agents - is it using a proxy where the others are not?

I hope this helps in your investigation!

[sbindra]

This fails on all build agents and as i said its not always. It works fine 8 out of 10 times.

[adam.hollow]

Hi @sbindra,

Thanks for getting back to us.

Would you be able to send over some build logs from failed and successful deployments?
This way, we could potentially narrow down a common denominator to assist in your investigation.
You can upload these logs via our secure support files upload site.

Unfortunately, this is likely an issue to do with networking and the certificates being supplied.
I would recommend discussing with your networking/infrastructure team to see if they can perform an investigation on the root cause.

Apologies that I don’t have a better answer for you, but please don’t hesitate to get back in touch if you have any further questions/concerns.

Kind Regards,
Adam