Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 无法用公网IP连接TIDB Dashboard
|
username: TiDBer_q94Ko9tU
[Test Environment for TiDB] Testing
[TiDB Version]
[Reproduction Path] Error when trying to access TiDB Dashboard via public address
First, install TiDB according to the quick start guide
Then, access via public address fails
Is the IP you are accessing the PD? Is this IP a public address? Can you ping it?
Have you opened the security group? Try using telnet to check if the local connection to the public address of PD on port 2379 is accessible.
It seems to be the firewall. For cloud servers, you need to open the ports in the cloud management console.
The firewall is not enabled, and ports 4000 and 2379 are open.
The 2379 port might not be open. You can test it with telnet.
Try using telnet with the public IP and port 2379 to see the response.
The firewall of the cloud server is not the firewall of CentOS. The firewall of the cloud service should not be turned off.
Additionally, I think the configuration file should not contain 127.0.0.1, but the actual IP instead.
Telnet is refusing connections from external networks, but it works with 127.0.0.1. The firewall and security group ports are all open.
Checking the port number, I found that only 127.0.0.1 can access it, not all IPs.
For MySQL, you can perform this operation. How can it be done for TiDB?
When deploying the cluster, should we use the specified --host? By default, it is 127.0.0.1, which is intended for deployment on a local computer. Our scenario involves connecting to Alibaba Cloud servers via the public network.
The public network is inaccessible; you need to use Nginx for reverse proxy.
I used FRP to perform intranet penetration on my Tencent Cloud.
You are using TiUP Playground to generate the test environment. TiUP Playground listens on 127.0.0.1 by default, making the service accessible only locally. If you need the service to be accessible externally, you can use the --host parameter to specify the network interface binding to an externally accessible IP.
–host should also be the internal network, I am using the public network and cannot access it at all.
Using the environment generated by Playground, that makes sense. I previously set one up on Alibaba Cloud following the standard procedure, and it was just a matter of opening the port in the cloud management console. With this method, you probably really need to specify --host as the external IP.
–host directly specifying 0.0.0.0 will listen to all network interfaces, and then using public network access will naturally map over.
I’ll give it a try when I get the chance. My previous cloud server has expired.
Using telnet with the public IP and port will let you know if the connection is successful.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: