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:
Determine which services have started successfully, and which have failed.
Review the configuration of any failed services. Cross-check your configuration with our documentation.
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.
If the issues persist, please see below!
When requesting support for your self-hosted instance of Cobrowse Enterprise, please provide us the following information:
Which type of deployment are you using? (i.e. AWS, GCP, Azure, Helm, Docker-compose, Openshift, etc)
How long has the issue occurred? Has it ever worked? If so, has anything changed on your side?
Are all the services up and running? Please share with us the current status of the services.
Please send us the container logs for the problematic services. If you are not sure, please share the container logs for all services.