Help Center/
ROMA Connect/
User Guide (ME-Abu Dhabi Region)/
Troubleshooting/
Data Sources/
Troubleshooting a Data Source Connection Test Failure
Updated on 2024-07-10 GMT+08:00
Troubleshooting a Data Source Connection Test Failure
- Check whether the data source configuration is correct. For example, check whether the database name and password are correct.
- Check whether the data source IP address and FDI are in the same VPC. If no, create a VPC peering connection.
For details about how to create a VPC peering connection, see .
- Check whether the connection port is enabled on the firewall of the data source server.
- Check whether the IP address of the FDI data plane is added to the IP address whitelist of the data source server.
- Check whether the data source IP address is the IP address of the customer's data center or private network. If yes, establish a VPN connection first.
- Check whether the route from FDI to the data source is correct.
If the IP address is a private network address and is not in the 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 network segment, add a route on the Instances page.
- Log in to the ROMA Connect console. On the Instances page, click View Console next to a specific instance.
- In the Routes area, click Edit, click Add Address, add a route, and click Save.
- Check whether the security group is bypassed.
- Log in to the ROMA Connect console. On the Instances page, click View Console next to a specific instance.
- In the Security Group area, click the security group name, for example, default, to access the security group console.
- On the Outbound Rules tab page, check whether the IP address configured for the data source is in the destination list.
If the destination IP address is 0.0.0.0/0, all IP addresses are reachable. If no rule is available, click Add Rule and add the configured IP address to the outbound rule.
Parent topic: Data Sources
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot