Code change didn't trigger the CodePipeline automatically for Self managed GitLab server

How to Use GitLab Self-managed
1

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

I’m experiencing issues with AWS CodePipeline integration with our self-managed GitLab server. While the initial setup of CodeConnection and CodePipeline was successful, automatic triggers aren’t working when code changes are made. The webhook events are failing with the following error:

Internal error occurred while delivering this webhook.
Error: Connection reset by peer - SSL_connect

Steps to reproduce

  1. Set up AWS CodeConnection and CodePipeline with self-managed GitLab server
  2. Make code changes and commit to the repository
  3. Check webhook events in GitLab, which shows the SSL connection error
  4. Pipeline does not trigger automatically despite successful initial setup

Configuration

Versions

Please add an x whether options apply, and add the version information.

  • Self-managed

Versions

  • GitLab (Web: /help or self-managed system information sudo gitlab-rake gitlab:env:info):

Helpful resources

  1. Check the FAQ for helpful documentation, issues/bugs/feature proposals, and troubleshooting tips.
  2. Before opening a new topic, make sure to search for keywords in the forum search
  3. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  4. Review existing troubleshooting docs.

Thanks for taking the time to be thorough in your request, it really helps! :blush:

2

Hi team, anyone know what does that mean for Error: Connection reset by peer - SSL_connect for the webhook, thanks.