Bitbucket Pipelines failure with SSL Certificate Problem

[Peter Boling]

x Build failed in 22.89s

error during build:

63

Error: [sentry-debug-id-upload-plugin] Command failed: /opt/atlassian/pipelines/agent/build/node_modules/.pnpm/@sentry+cli-linux-x64@2.31.2/node_modules/@sentry/cli-linux-x64/bin/sentry-cli releases new 1cefc835e6a8472f914a3f2bda9bcbc0

64

DEBUG 2024-05-19 08:00:24.578579713 +00:00 sentry-cli version: 2.31.2, platform: "linux", architecture: "x86_64"

65

INFO 2024-05-19 08:00:24.578655948 +00:00 sentry-cli was invoked with the following command line: "/opt/atlassian/pipelines/agent/build/node_modules/.pnpm/@sentry+cli-linux-x64@2.31.2/node_modules/@sentry/cli-linux-x64/bin/sentry-cli" "releases" "new" "1cefc835e6a8472f914a3f2bda9bcbc0"

66

DEBUG 2024-05-19 08:00:24.579110707 +00:00 request POST https://sentry.io/api/0/projects/fisecal-vk/fisecal-monolith/releases/

67

DEBUG 2024-05-19 08:00:24.579135805 +00:00 pipeline: vite-plugin/2.14.2

68

DEBUG 2024-05-19 08:00:24.579147845 +00:00 using token authentication

69

DEBUG 2024-05-19 08:00:24.579171582 +00:00 json body: {"version":"1cefc835e6a8472f914a3f2bda9bcbc0","projects":["fisecal-monolith"],"dateStarted":"2024-05-19T08:00:24.579086786Z"}

70

DEBUG 2024-05-19 08:00:24.579181540 +00:00 retry number 0, max retries: 0

71

error: API request failed

72

caused by: [60] SSL peer certificate or SSH remote key was not OK (SSL certificate problem: unable to get local issuer certificate)

I don't think I can fix this on my own. :(

[Patrik S]

Hello @Peter Boling ,

thank you for reaching out to the Community!

I would recommend trying to troubleshoot your pipeline build locally following the instructions in the article below:

• Troubleshoot failed Bitbucket Pipelines locally with Docker 

This will remove pipeline infrastructure from the equation, so we can rule out whether the issue is related to the pipeline itself, your build config, and/or the external server you are connecting to.

If you are able to reproduce the same error locally, you can try debugging via the command line. Once you get the command working, you can update your YML to match.

Thank you, @Peter Boling !

Patrik S

[Peter Boling]

From my research it appears that causes of the error can be:

1. Date / Time being incorrect on the server
2. Self-signed certificates can cause this depending on the requirements of the connection
3. COMMON NAME(CN) of your server certificate needs to match with the Server IP
   
4. Attempting an IPv6 request when server doesn't support IPv6 yet