tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary
DocumentationTencentDB for MySQLTroubleshootingConnectionsOverview

Overview

PDF
Focus Mode
Font Size
Last updated: 2023-12-27 17:17:06
This section introduces potential causes and processing for TencentDB for MySQL instance connection failures, helping you quickly locate the root cause of such failures.

I. Utilizing the One-Click Connection Check Tool to Locate the Cause and Implementing Corresponding Actions

When encountering connection issues related to either private network or public network connection to TencentDB for MySQL instances, it is advisable to prioritize the One-Click Connection Check Tool to locate the underlying cause.
In the event of a private network connection failure, please refer to Using the One-Click Connection Check Tool to Locate the Cause.
In the event of a public network connection failure, please refer to Using the One-Click Connection Check Tool to Locate the Cause.

II. Self-Check and Processing

If the One-Click Connection Check Tool fails to locate the cause and resolve the issue, you can conduct a self-check and process according to the following scenarios.
Scenario
Possible Causes
Processing
The password is incorrect.
The CVM and MySQL instances are in the same region but belong to different VPC networks.
The CVM and MySQL instances are in different regions and belong to separate VPC networks.
The configuration for CVM security group is incorrect.
The configuration of MySQL security group is incorrect.
The database account has restricted the access to specific host addresses.
The connection command is incorrect.
The IP and port in the command line or configuration file are incorrect.
The MySQL instance's disk is full; maximum connections have been reached; the timeout parameter setting is incorrect; a master/slave switch is undergoing, or other possible issues.
The MySQL instance is in isolation. It can be restored from the Recycle Bin.
-
The CVM instance is in isolation or shut down. It can be restored or powered on through the Console.
-
The password is incorrect.
The configuration for CVM security group is incorrect.
The configuration of MySQL security group is incorrect.
The database account has restricted the access to specific host addresses.
The connection command is incorrect.
The IP and port in the command line or configuration file are incorrect.
The MySQL instance's disk is full; maximum connections have been reached; the timeout parameter setting is incorrect; a master/slave switch is undergoing, or other possible issues.
The MySQL instance is in isolation. It can be restored from the Recycle Bin.
-
The CVM instance is in isolation or shut down. It can be restored or powered on through the Console.
-
The password is incorrect.
The database account has restricted the access to specific host addresses.
The connection command is incorrect.
The IP and port in the command line or configuration file are incorrect.
The route table is not enabled.
The MySQL instance's disk is full; maximum connections have been reached; the timeout parameter setting is incorrect; a master/slave switch is undergoing, or other possible issues.
The MySQL instance is in isolation. It can be restored from the Recycle Bin.
-
The CVM instance is in isolation or shut down. It can be restored or powered on through the Console.
-
The LIGHTHOUSE instance is in isolation or shut down. It can be restored or powered on through the Console.
-
The database account has restricted the access to specific host addresses.
The password is incorrect.


Previous Topic: Data Disaster RecoveryNext Topic: Private Network Connection Failure

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback