Cobrowse.io Docs
  • Getting started
  • SDK Installation
    • Web
    • iOS
    • Android
    • React Native
    • Flutter
    • .NET Mobile
    • macOS
    • Windows
  • SDK Features
    • Account config
    • Identify your devices
    • Use 6-digit codes
    • Redact sensitive data
    • Viewing PDFs
    • Universal Cobrowse
    • Customize the interface
      • Active session controls
      • 6-digit code screen
      • User consent dialog
      • Remote control consent dialog
      • Full device consent dialog
      • Localization / translation
    • Initiate sessions with push
    • Listening for events
    • Full device capabilities
      • Full device screen sharing
      • Full device remote control
      • Managing full device mode
    • Advanced configuration
      • Starting and stopping the SDK
      • Declaring capabilities
      • Intercepting mobile SDK network requests
      • Web
        • IFrames support
        • IE 11 polyfills
        • Cross-domain session support
        • Ignore Views
      • iOS
        • Alternate render method
        • Custom touch handling
      • Android
        • Backporting TLS to older Android versions
  • Agent-side integrations
    • Agent-side overview
    • Platform integrations
      • Zendesk
      • Salesforce
        • Migrating from legacy to v2
        • Salesforce (Legacy)
      • Genesys
        • Genesys Cloud
        • Engage Workspace Web Edition (WWE)
        • Engage Workspace Desktop Edition (WDE)
      • Intercom
      • Freshworks
      • Talkdesk
      • NICE
    • Custom integrations
    • Agent SDK
      • API Reference
      • Sample code snippets
    • Authentication (JWTs)
      • JWT Policies
    • Authentication (SAML 2.0)
    • IFrame embeds
  • Enterprise self-hosting
    • Self-hosting overview
    • Docker Compose
    • Helm chart
      • Image Pull Secret
      • Environment Variables
      • Optional recording components
      • Pod Annotations
    • AWS terraform
      • AWS metrics configuration
    • Azure terraform
      • Azure metrics configuration
    • GCP terraform
      • GCP metrics configuration
    • Sizing guidelines
    • Running your instance
      • Adding a superuser
      • Limiting account creation
      • Limiting magic link recipients
      • Configuring SMTP
      • Managing your deployment
    • Monitoring your instance
      • Available metrics
      • Self-Hosted Prometheus
    • Advanced configuration
      • Air gap configuration
      • Pin web SDK version
      • L7 firewall configuration
      • Docker proxy configuration
    • Troubleshooting
Powered by GitBook
On this page
  • Initial deployment
  • Requesting support

Was this helpful?

  1. Enterprise self-hosting

Troubleshooting

Troubleshooting your self-hosted deployment.

PreviousDocker proxy configuration

Last updated 1 year ago

Was this helpful?

Initial deployment

If issues arise during the initial deployment of your self-hosted Cobrowse Enterprise, it is often related to the pods/containers not being able to start, or attempting to start but failing to start up successfully.

Often, there is an underlying configuration issue, such as specifying an invalid MongoDB URL. Other times, a corporate proxy might be blocking access to the Docker image repository.

Here are the high-level steps to help diagnose the problem:

  1. Determine which services have started successfully, and which have failed.

  2. Review the configuration of any failed services. Cross-check your configuration with our documentation.

  3. Analyze the container logs, starting with the failed services if logs are available, and then the running services. The error messages should provide helpful hints on what has gone wrong.

  4. If the issues persist, please see below!

Requesting support

Please provide the following information to :

  1. Which type of deployment are you using? (i.e. AWS, GCP, Azure, Helm, Docker-compose, Openshift, etc)

  2. Which version of Cobrowse Enterprise and/or service containers are you using?

  3. How long has the issue occurred? Has it ever worked? If so, has anything changed on your side?

  4. Are all the services up and running? Please share with us the current status of the services.

  5. Please send us the container logs for the problematic services. If you are not sure, please share the container logs for all services.

hello@cobrowse.io