TLS Compatibility Issue Between Self-Managed GitLab Server and Seqera Connection

Ask for help
1

We are currently experiencing a connection issue between our self-managed GitLab server and Seqera. It looks like the connection might be failing because Seqera is attempting to use TLS 1.3, while our server only supports TLS 1.2. However, I am not fully certain of this.

Could you please confirm if Seqera requires TLS 1.3 for the connection, or if there is a way to configure it to use TLS 1.2? If the session drops are related to this TLS mismatch, any insight on how to resolve it would be appreciated.

2

Welcome to the forum, @Nikunj_P.

You’re using a self-managed Seqera Platform Enterprise instance or Seqera Cloud?

Can you give us more detail about what you’re refering to as connection issue? Any logs? What’s the error message?

According to the documentation, TLS v1.2 can be explicitly enabled by default using JDK environment variables:

_JAVA_OPTIONS="-Dmail.smtp.ssl.protocols=TLSv1.2"