Certificates and proxies
If CloudPouch cannot reach AWS from your corporate network while the same profile works at home, your company is probably running TLS inspection. The fix is one line in config.json: point certificatePath at your company’s PEM certificate bundle and restart CloudPouch.
Most users never need this setting. On a normal network, CloudPouch connects to AWS APIs directly and the standard certificate chain just works.
Why this happens
Section titled “Why this happens”Enterprise networks often route outbound HTTPS through a security appliance that decrypts the traffic, scans it, and re-signs it with an internal certificate authority. Common products that do this:
- Zscaler Internet Access
- Blue Coat / Symantec ProxySG
- F5 BIG-IP SSL Orchestrator
Your browser trusts the internal CA because IT installed it in the operating system trust store. Desktop applications that bundle their own trust chain do not, so their HTTPS connections fail with certificate errors. CloudPouch solves this by letting you supply the internal CA certificate explicitly.
Configuration
Section titled “Configuration”Add certificatePath to CloudPouch’s config.json:
{ "certificatePath": "<Path to your .pem certificate file>"}Requirements:
- The value must be an absolute path including the file name, not a relative path or a directory.
- The certificate must be in PEM format. Ask your IT or security team for the CA bundle they use for TLS inspection — it is the same one installed in your browser’s trust store.
- Your user account needs read access to the file.
- Restart CloudPouch after changing the setting; it is read at startup.
Custom certificate support is available in CloudPouch 1.25.0 and later.
Still failing after configuration
Section titled “Still failing after configuration”Check, in order: the path is exactly right, the PEM file opens in a text editor and starts with -----BEGIN CERTIFICATE-----, and the bundle actually contains the CA your network re-signs with. The CloudPouch log file (see Local files) records connection errors that help narrow down which of these it is.
Config file locations
Section titled “Config file locations”| Operating system | Config file |
|---|---|
| macOS | /Users/<YOUR_USER_NAME>/Library/Application Support/CloudPouch/config.json |
| Windows | C:\Users\<YOUR_USER_NAME>\AppData\Roaming\CloudPouch\config.json |
| Linux | ~/.config/CloudPouch/config.json |