TEST-INFRA: Git repository is inaccessible due to TLS/SNI error #1629

Closed
opened 2026-04-02 23:18:40 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: bug/v3.8.0-tls-sni-git-inaccessible
  • Commit Message: fix(infra): resolve TLS/SNI error blocking git.cleveragents.com repository access
  • Milestone: v3.8.0
  • Parent Epic: (see orphan note below)

Background and Context

The git repository at git.cleveragents.com is currently inaccessible via HTTPS. This is a blocking infrastructure issue that prevents all development and CI activities from interacting with the repository.

Current Behavior

Both git clone and curl commands fail with a TLS error:

fatal: unable to access 'https://git.cleveragents.com/...': OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to git.cleveragents.com:443
error: tlsv1 unrecognized name

This prevents:

  • Cloning the repository
  • Fetching updates
  • Pushing changes
  • Any CI pipeline step that requires repository access

Expected Behavior

The git.cleveragents.com hostname should be correctly served with a valid TLS certificate that includes the SNI (Server Name Indication) for git.cleveragents.com, allowing all git and curl HTTPS operations to succeed without TLS errors.

Subtasks

  • Investigate the TLS/SNI configuration on the server hosting git.cleveragents.com
  • Verify the SSL certificate includes git.cleveragents.com as a Subject Alternative Name (SAN)
  • Confirm the web server (nginx/caddy/etc.) has a virtual host / server block configured for git.cleveragents.com
  • Test curl -v https://git.cleveragents.com to confirm TLS handshake succeeds post-fix
  • Test git clone https://git.cleveragents.com/<repo> to confirm repository access is restored
  • Verify CI pipelines can clone and push successfully after the fix
  • Run nox (all default sessions), fix any errors
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
  • All nox stages pass.
  • Coverage >= 97%.

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `bug/v3.8.0-tls-sni-git-inaccessible` - **Commit Message**: `fix(infra): resolve TLS/SNI error blocking git.cleveragents.com repository access` - **Milestone**: v3.8.0 - **Parent Epic**: _(see orphan note below)_ ## Background and Context The git repository at `git.cleveragents.com` is currently inaccessible via HTTPS. This is a blocking infrastructure issue that prevents all development and CI activities from interacting with the repository. ## Current Behavior Both `git clone` and `curl` commands fail with a TLS error: ``` fatal: unable to access 'https://git.cleveragents.com/...': OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to git.cleveragents.com:443 error: tlsv1 unrecognized name ``` This prevents: - Cloning the repository - Fetching updates - Pushing changes - Any CI pipeline step that requires repository access ## Expected Behavior The `git.cleveragents.com` hostname should be correctly served with a valid TLS certificate that includes the SNI (Server Name Indication) for `git.cleveragents.com`, allowing all `git` and `curl` HTTPS operations to succeed without TLS errors. ## Subtasks - [ ] Investigate the TLS/SNI configuration on the server hosting `git.cleveragents.com` - [ ] Verify the SSL certificate includes `git.cleveragents.com` as a Subject Alternative Name (SAN) - [ ] Confirm the web server (nginx/caddy/etc.) has a virtual host / server block configured for `git.cleveragents.com` - [ ] Test `curl -v https://git.cleveragents.com` to confirm TLS handshake succeeds post-fix - [ ] Test `git clone https://git.cleveragents.com/<repo>` to confirm repository access is restored - [ ] Verify CI pipelines can clone and push successfully after the fix - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - All nox stages pass. - Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.7.0 milestone 2026-04-02 23:19:01 +00:00
Author
Owner

⚠️ Orphan Issue — Manual Linking Required

No parent Epic with Type/Epic label was found in the open issues for this repository at the time of creation. This issue could not be automatically linked to a parent Epic via Forgejo's dependency system.

Action required: A maintainer must manually link this issue to the appropriate parent Epic (e.g., a TEST-INFRA CI environment Epic) using Forgejo's dependency system so that this issue blocks the parent Epic.

Related existing issues covering the same TLS/SNI problem area:

  • #1607 — TEST-INFRA: [BLOCKER] Unable to clone repository due to TLS/SNI issue
  • #1593 — TEST-INFRA: [BLOCKER] Unable to clone repository due to TLS/SNI issue on git.cleveragents.com
  • #1601 — TEST-INFRA: [ci-environment] Unable to clone repository due to TLS/SSL handshake failure
  • #1543 — fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com (State/Verified)

Please consider whether this issue is a duplicate of any of the above before proceeding.


Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

⚠️ **Orphan Issue — Manual Linking Required** No parent Epic with `Type/Epic` label was found in the open issues for this repository at the time of creation. This issue could not be automatically linked to a parent Epic via Forgejo's dependency system. **Action required**: A maintainer must manually link this issue to the appropriate parent Epic (e.g., a TEST-INFRA CI environment Epic) using Forgejo's dependency system so that this issue **blocks** the parent Epic. Related existing issues covering the same TLS/SNI problem area: - #1607 — TEST-INFRA: [BLOCKER] Unable to clone repository due to TLS/SNI issue - #1593 — TEST-INFRA: [BLOCKER] Unable to clone repository due to TLS/SNI issue on git.cleveragents.com - #1601 — TEST-INFRA: [ci-environment] Unable to clone repository due to TLS/SSL handshake failure - #1543 — fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com (State/Verified) Please consider whether this issue is a duplicate of any of the above before proceeding. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Closing as duplicate of #1543. This TLS/clone failure is already tracked as Priority/Critical, MoSCoW/Must Have.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Closing as duplicate of #1543. This TLS/clone failure is already tracked as Priority/Critical, MoSCoW/Must Have. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo 2026-04-02 23:30:33 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#1629
No description provided.