Kameleo in Restricted Network Environments
In this article, we'll outline the network requirements for Kameleo to function correctly in environments with restricted network access, given that Kameleo requires access to specific domains and ports to operate properly. If you're working in an environment with a restrictive firewall or network policy, you'll need to whitelist certain domains and ports to ensure Kameleo can create and start profiles successfully.
Common Error Messages
If you encounter network-related issues, you may see error messages like:
Network error during communication: TrustFailureUnable to perform revocation check of the server certificate
If your profiles are stuck in "STARTING" status and no Chroma instance window opens, it's likely due to network restrictions.
These typically indicate that Kameleo cannot access required network resources.
Required Domains and Ports
The following domains and ports must be accessible for Kameleo to function properly:
*.kameleo.io:443- Required for authentication and API accessapp.kameleo.io:8080- Required for browser profile management
Be advised that you cannot simply whitelist specific IP addresses as our services are behind CDNs with dynamic IP addresses.
Certificate Verification
The following domains are used for certificate verification and must be accessible:
ocsp.comodoca.comocsp.sectigo.comcrl.comodoca.comcrl.sectigo.comc.pki.googo.pki.goog
Workaround for Proxy Issues
As Kameleo is determining the external IP address, it needs to make a request through the proxy. If you're using a proxy and experiencing issues starting profiles, you can:
- Request your proxy provider to whitelist
*.kameleo.io - Attempt to start the profile without the proxy.
- Manually configure spoofing settings, such as:
- WebRTC
- Geolocation
- Timezone
- Test with a different proxy provider
If you continue to experience network-related issues after implementing these suggestions, please contact us .