CI HUB Drive for Mac: No Folders or Assets Showing — Fixing HTTPS Inspection Issues

Overview

If a customer opens CI HUB Drive for Mac and no folders or assets appear, the issue is often not with the application itself. In most cases, the application is running correctly, but it cannot establish a secure connection to CI HUB services.

This is typically caused by HTTPS/SSL inspection performed by a corporate proxy or security solution.

Why This Happens

CI HUB Drive relies on secure HTTPS communication to connect to its backend services.

In some environments, IT/security tools intercept HTTPS traffic and replace the original SSL certificate chain with their own (for inspection purposes).

CI HUB Drive does not accept modified certificate chains, so when this happens:

• The connection is blocked
• No assets or folders are displayed
• The app appears empty or disconnected

👉 Important:
This is not a bug in CI HUB Drive, and no SSL/TLS weakening or changes are required on the application side.

Required Solution

To resolve this issue, the customer’s IT or security team must configure their proxy/security tools to exclude CI HUB traffic from HTTPS inspection.

What IT Teams Need to Do

1. Exclude CI HUB Endpoints from HTTPS Inspection

Ensure the following endpoints are bypassed from SSL/TLS inspection:

• live.ci-hub.com:443
• stage.ci-hub.com:443 (if used)
• dev.ci-hub.com:443 (if used)

2. Exclude DAM / Provider Hostnames

If CI HUB Drive is connected to external DAM systems (e.g., Brandfolder, Bynder, etc.), those provider domains must also be excluded from HTTPS inspection.

3. Allow Required Executables

Make sure the following CI HUB Drive executables are allowed by endpoint security tools:

 /Applications/CI HUB Drive.app/Contents/MacOS/CI HUB Drive

/Applications/CI HUB Drive.app/Contents/Resources/CIHubASGI.app/Contents/MacOS/CIHubASGI

/Applications/CI HUB Drive.app/Contents/Resources/CIHubFlask.app/Contents/MacOS/CIHubFlask