Docs/self hosted misc (#1266)

Author: bruno-espino

docs/reference/self-hosted/installation.md

@@ -20,7 +20,7 @@ You will require image pull secrets to pull down the docker images from our priv
 
 The Helm chart does not include a production-ready Postgres Database (only a development instance).  You will be required to connect to, and create databases on a Postgres instance.
 
-You will need to create 3 databases, that are used for different things.
+You will need to create 3 databases, that are used for different things. It's ok to have them all on the same instance.
 
 While we are currently working on running **Logfire** on one database, for now they *must* be separated.
 

docs/reference/self-hosted/troubleshooting.md

@@ -2,14 +2,6 @@
 
 There are occasions when you need to troubleshoot the installation.  Since Logfire sends its own internal logs to the `logfire-meta` organisation, this is a good place to start.
 
-## ErrImagePull / ImagePullBackOff
-
-If you are seeing Image pull issues on your logfire pods, make sure you have:
-
-* Created the required Image Pull Secret as described at the [Installation](./installation.md#image-pull-secrets_1) section
-* You set the right secret name at `Values.imagePullSecrets`
-* Both secret and the release are installed on the same namespace
-
 ## Accessing the Meta Organization
 
 Logfire will send internal traces to a meta organisation that is created upon first install.   This meta organisation is helpful in troubleshooting any issues that might arise when running Logfire.
@@ -59,3 +51,37 @@ One quick thing to check is the console logs involved in those services.  Here a
  ```
  kubectl logs -n logfire deployments/logfire-ff-query-api
  ```
+
+## ErrImagePull / ImagePullBackOff
+
+If you are seeing Image pull issues on your logfire pods, make sure you have:
+
+* Created the required Image Pull Secret as described at the [Installation](./installation.md#image-pull-secrets_1) section
+* You set the right secret name at `Values.imagePullSecrets`
+* Both secret and the release are installed on the same namespace
+
+## ff-conhash-cache errors
+
+If you see errors on your conhash-cache pods that look like ```ERROR panic: Failed to build listeners``` or some message like ```Address family not supported by protocol```
+
+This might be due to your hosts having IPv6 disabled.
+To fix this, you can add the following to your values file
+```
+logfire-ff-conhash-cache:
+  env:
+    - name: HOST
+      value: "0.0.0.0"
+```
+
+Which will make the cache pod bind only to the IPv4 interface and fix the issue.
+
+## Troubleshooting and support
+
+If this page didn't help, please open a detailed issue on [Github](https://github.com/pydantic/logfire-helm-chart/issues), including:
+
+* Chart version
+* Kubernetes version
+* A sanitized copy of your ```values.yaml```
+* Relevant logs or error messages
+
+For commercial or enterprise support, contact [our sales team](mailto:[email protected]).