You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,15 +25,15 @@ I cannot connect to my Database Instance through the public network.
25
25
- The Database Instance TLS certificate is outdated
26
26
- Your allowed IPs are not properly configured
27
27
- You have reached the maximum number of connections
28
-
- The Database Instance experiences instabilities due to a high load
28
+
- The Database Instance is experiencing instabilities due to a high load
29
29
30
30
### Solution
31
31
32
32
You can check the following points to identify and act on what might be causing the issue:
33
33
34
-
1. If TLS is enabled on the Database Instance, make sure the certificate is up-to-date, and that your client application is properly configured.
34
+
1. If TLS is enabled on the Database Instance, make sure the certificate is up to date, and that your client application is properly configured.
35
35
2. Make sure your [ACLs](/managed-databases-for-postgresql-and-mysql/concepts/#allowed-ips) are [properly configured](/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses).
36
-
3. Make sure your Database Instance does not reach the maximum number of connections stipulated in the advanced settings of the Database Instance. You can monitor the number of connections on [Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit). You can also [adjust the advances settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) to accept a higher number of connections.
36
+
3. Make sure your Database Instance has not reached the maximum number of connections stipulated in the advanced settings of the Database Instance. You can monitor the number of connections on [Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit). You can also [adjust the advances settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) to accept a higher number of connections.
37
37
4.[Monitor other usage metrics on Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to:
38
38
39
39
- Check if the memory usage is nominal. High memory usage could trigger OOM Kills and cause disconnection
0 commit comments