gistfile1.txt

If the git config --global http.sslCAInfo command produced an empty output, it implies that git has not been explicitly configured with a specific Certificate Authority (CA) bundle file, and so it is falling back to the system's CA bundle file.

The fact that you see in the strace output that it's opening /etc/ssl/certs/ca-certificates.crt confirms that it is indeed using the system's CA bundle file. It means that git is using the correct file for SSL certificate verification.

Given that the certificate is valid, the issuer is Let's Encrypt (which is widely trusted), and the system is correctly referring to the CA bundle file, the issue is likely not with the SSL certificate itself or with the CA bundle file.

You may want to consider the following possibilities:

    Network issues: Are you possibly behind a proxy or firewall that could be interfering with git's connection? Try cloning the repository from a different network environment, if possible.

    Older version of Git or OpenSSL: There might be a bug in the version of Git or OpenSSL you are using. Updating Git and OpenSSL to the latest versions might resolve the issue.

    Misconfigured ~/.gitconfig or .gitconfig in your repo: There might be some misconfiguration in these files. Look for any http or https related settings that might be causing the issue.

    Issue with the Codeberg server: It's also possible (though less likely if you're not having issues with any other repositories on the same server) that the issue is on the server side. If none of the above solutions work, you might want to contact Codeberg's support.