tencent cloud

Feedback

Overview

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.
    
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support