tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Database Audit
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Connection and Login

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-02-06 21:08:00

How do I connect to a TencentDB for Redis® instance?

You can connect to a TencentDB for Redis® instance using a client tool, DMC, and SDKs supporting various programing languages. For more information, see Connecting to TencentDB for Redis® Instance.

What should I do if the connection to TencentDB for Redis® failed?

Common causes of connection failure: Network/security group issues, password issues, and connection issues (i.e., the maximum number of connections has been reached). For corresponding solutions, see Redis Instance Connection Failure.

How can TencentDB for Redis® support private network access? How do I view the private network address of my instance?

To support private network access, the CVM and TencentDB instances must be under the same account and in the same VPC in the same region, or both in the classic network.
To view the private network address, log in to the TencentDB for Redis® console and view the address in the instance list, or click an instance ID and view the address on the displayed instance details page.

Can my CVM instance connect to TencentDB for Redis® over private network?

1. The following conditions must be met to use the private network connection: The CVM and TencentDB instances must be under the same account and in the same VPC in the same region, or both in the classic network.
2. You can check whether they are in the same VPC or both in the classic network in the following ways:
You can log in to the CVM console, and view the network information of a CVM instance in the instance list or on the instance details page.
You can log in to the TencentDB for Redis® console, and view the network information of a Redis instance in the instance list or on the instance details page. For more information, see Redis Instance Connection Failure.

What should I do if my CVM and TencentDB for Redis® instances are in different VPCs?

You can connect to instances through CCN. CVM and TencentDB instances in different VPCs (under the same or different accounts in the same or different regions) can be interconnected over the private network through Cloud Connect Network.

My CVM and TencentDB for Redis® instances are in different regions (such as Guangzhou and Shanghai, respectively). Can I use a private network for connection?

If CVM and Redis instances are in different regions, they are in different VPCs, so they cannot interconnect directly over private network. We recommend that you use CCN to connect the VPCs.

My CVM and TencentDB for Redis® instances are in different AZs (such as Shanghai Zone 2 and Shanghai Zone 3, respectively) in the same region. Can I use a private network for connection?

Even if the CVM and TencentDB for Redis® instances are in the same region, they may be in different VPCs.
If they are in different AZs in the same VPC, they can interconnect over private network.
If they are in different VPCs (such as VPC 1 and VPC 2, respectively), they cannot interconnect over the private network. For solutions, see Changing Network.

My CVM and TencentDB for Redis® instances are in different AZs (such as Shanghai Zone 2 and Shanghai Zone 3, respectively) in the same VPC. Can I use a private network for connection?

Yes. Instances in different AZs but in the same VPC interconnect over private network by default.

My CVM and TencentDB for Redis® instances are under different accounts. Can I use a private network for connection?

No. Because instances under different accounts are in different VPCs. We recommend that you use CCN for connection.

How do I enable access to Redis over public network?

For more information, see Configuring Public Network Address.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백