Dev.to

Resolving SSL Certificate Issues with Zscaler

When working in environments where HTTPS traffic is intercepted and proxied by tools like Zscaler , you may encounter SSL certificate validation errors when making HTTPS requests (e.g., curl, wget, or Kubernetes API calls). This article outlines the root cause of the issue, troubleshooting steps, and solutions to resolve it. Problem Description When using tools like curl or Kubernetes resources (e.g., ConfigMap, kubectl), you may encounter errors such as: curl: (60) SSL certificate problem: self-signed certificate in certificate chain This happens because: Zscaler intercepts HTTPS traffic and replaces the original server certificate with its own. The system does not trust the Zscaler root certificate, leading to SSL validation failures. Root Cause Corporate proxies like Zscaler acts as a man-in-the-middle (MITM) for HTTPS traffic: Zscaler decrypts outgoing HTTPS traffic from your machine. It re-encrypts the traffic using its own certificate before forwarding it to the destination server. If the Zscaler root certificate is not trusted by your system, SSL validation fails. Solution Approaches 1. Add the Zscaler Root Certificate to Your Trusted Store To resolve the issue, you need to add the Zscaler root certificate to your system's trusted certificate store. Follow these steps: Step 1: Export the Zscaler Root Certificate You can export the Zscaler root certificate using one of the following methods: Option A: From Your Browser Open your browser and navigate to any HTTPS website (e.g., https://dl.k8s.io). Click the lock icon in the address bar to view the site's security information. Select "Certificate" or "Connection is secure" > "Certificate is valid" . In the certificate window, go to the "Certification Path" tab. Select the topmost certificate in the chain (usually the Zscaler root certificate). Click "Export" and save the certificate as a .cer file (DER or PEM format). Option B: Using OpenSSL Run the following command to inspect the certificate chain and extract the root certificate: openssl s_client -showcerts -connect dl.k8s.io:443 Import Items and select the .cer file. Trust the certificate: Double-click the imported certificate. Expand the "Trust" section and set "When using this certificate" to "Always Trust" . Step 3: Verify the Certificate Installation Test the connection again to ensure the certificate is trusted: curl https://dl.k8s.io/release/stable.txt If successful, you should see the content of the file without SSL errors. Troubleshooting Tips 1. Verify Certificate Chain Use openssl to inspect the certificate chain: openssl s_client -showcerts -connect dl.k8s.io:443

May 11, 2025 - 15:03
 0
Resolving SSL Certificate Issues with Zscaler

When working in environments where HTTPS traffic is intercepted and proxied by tools like Zscaler , you may encounter SSL certificate validation errors when making HTTPS requests (e.g., curl, wget, or Kubernetes API calls). This article outlines the root cause of the issue, troubleshooting steps, and solutions to resolve it.

Problem Description

When using tools like curl or Kubernetes resources (e.g., ConfigMap, kubectl), you may encounter errors such as:

curl: (60) SSL certificate problem: self-signed certificate in certificate chain

This happens because:

  • Zscaler intercepts HTTPS traffic and replaces the original server certificate with its own.
  • The system does not trust the Zscaler root certificate, leading to SSL validation failures.

Root Cause

Corporate proxies like Zscaler acts as a man-in-the-middle (MITM) for HTTPS traffic:

  • Zscaler decrypts outgoing HTTPS traffic from your machine.
  • It re-encrypts the traffic using its own certificate before forwarding it to the destination server.
  • If the Zscaler root certificate is not trusted by your system, SSL validation fails.

Solution Approaches

1. Add the Zscaler Root Certificate to Your Trusted Store

To resolve the issue, you need to add the Zscaler root certificate to your system's trusted certificate store. Follow these steps:

Step 1: Export the Zscaler Root Certificate

You can export the Zscaler root certificate using one of the following methods:

Option A: From Your Browser

  1. Open your browser and navigate to any HTTPS website (e.g., https://dl.k8s.io).
  2. Click the lock icon in the address bar to view the site's security information.
  3. Select "Certificate" or "Connection is secure" > "Certificate is valid" .
  4. In the certificate window, go to the "Certification Path" tab.
  5. Select the topmost certificate in the chain (usually the Zscaler root certificate).
  6. Click "Export" and save the certificate as a .cer file (DER or PEM format).

Option B: Using OpenSSL

Run the following command to inspect the certificate chain and extract the root certificate:

openssl s_client -showcerts -connect dl.k8s.io:443

Look for the root certificate in the output (issued by Zscaler).
Copy the base64-encoded block of the root certificate into a file (e.g., zscaler-root-ca.crt).

Step 2: Add the Certificate to Your Trusted Store

Follow these steps based on your operating system:

For Linux

  1. Copy the certificate to the trusted certificates directory: 
sudo cp zscaler-root-ca.crt /usr/local/share/ca-certificates/
  1. Update the CA certificates: 
sudo update-ca-certificates

For macOS

  1. Open the Keychain Access application.
  2. Import the certificate:
  3. Go to File > Import Items and select the .cer file.
  4. Trust the certificate:
  5. Double-click the imported certificate.
  6. Expand the "Trust" section and set "When using this certificate" to "Always Trust" .

Step 3: Verify the Certificate Installation

Test the connection again to ensure the certificate is trusted:

curl https://dl.k8s.io/release/stable.txt

If successful, you should see the content of the file without SSL errors.

Troubleshooting Tips

1. Verify Certificate Chain

Use openssl to inspect the certificate chain:

openssl s_client -showcerts -connect dl.k8s.io:443

Ensure the chain includes the Zscaler root certificate.

2. Check Proxy Settings

Verify that no additional proxies are interfering with the connection. For example:

  • Check environment variables like HTTP_PROXY and HTTPS_PROXY.
  • Ensure your network configuration allows direct access to external domains if needed.

3. Test with Different Networks

If possible, test your setup on a network where Zscaler is not active (e.g., personal Wi-Fi). This helps confirm whether the issue is specific to Zscaler.

Conclusion

By adding the Zscaler root certificate to your trusted store, you can resolve SSL certificate validation issues in environments where Zscaler intercepts HTTPS traffic. Use the steps outlined above to ensure secure and uninterrupted communication with external services.

If you encounter further issues, consult your IT department for assistance with Zscaler configurations or certificate management.

Read More

Tags:

Previous Article

LegoGPT: Build Amazing LEGO Creations with AI!

Next Article

PS4 Game Going Offline After 4 Years, Free PS5 Upgrade Offered

Related Posts

How to Fix Jittery Performance in a Nintendo 3DS Snake Game?

How to Fix Jittery Performance in a Nintendo 3DS Snake ...

May 11, 2025  0

May 9, 2025  0

How to Resolve Undefined Reference Errors with Kvaser CanLib in C

How to Resolve Undefined Reference Errors with Kvaser C...

May 12, 2025  0