Is it possible that you guys enable TLS
# 🐶｜generalm
may0r
03/21/2026, 2:53 PMIs it possible that you guys enable TLS 1.2 again? It looks like it was discontinued in January, but my provider (that calls AP) doesn't work with TLS 1.3 :/
may0r
03/21/2026, 2:56 PM> TLS Verification Report
>
> Date tested: March 21, 2026
> Target host: cloud.activepieces.com:443
>
> Result:
>
> TLS 1.3: Supported
> TLS 1.2: Rejected
> TLS 1.1: Rejected
> TLS 1.0: Rejected
> Conclusion:
>
> cloud.activepieces.com is configured as TLS 1.3-only.
> TLS 1.2 is not allowed/supported.
> Commands used (domain shown, full webhook URL hidden):
>
> # Baseline negotiation
> echo | openssl s_client -connect cloud.activepieces.com:443 -servername cloud.activepieces.com 2>/dev/null | rg "Protocol|Cipher" -n
>
> # Force TLS 1.2
> openssl s_client -connect cloud.activepieces.com:443 -servername cloud.activepieces.com -tls1_2
> # Force TLS 1.1
> echo | openssl s_client -connect cloud.activepieces.com:443 -servername cloud.activepieces.com -tls1_1 2>&1 | rg -i "protocol version|Protocol|Cipher|alert" -n
>
> # Force TLS 1.0
> echo | openssl s_client -connect cloud.activepieces.com:443 -servername cloud.activepieces.com -tls1 2>&1 | rg -i "protocol version|Protocol|Cipher|alert" -n
> Observed indicators:
>
> Successful handshake reports Protocol : TLSv1.3.
> Rejected handshakes show alert protocol version and no negotiated cipher (Cipher is (NONE) / Cipher : 0000).
m
Mo
03/21/2026, 6:20 PM@may0r We will have to take look as the security audit might not allow us to do that 🙁