> For the complete documentation index, see [llms.txt](https://ai2sql.gitbook.io/ai2sql/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai2sql.gitbook.io/ai2sql/9.-database-connectors/9.7.-troubleshooting-ai2sql-connector-issues-a-comprehensive-checklist.md). # 9.7. Troubleshooting AI2sql Connector Issues: A Comprehensive Checklist Follow this comprehensive checklist to ensure that your AI2sql connector settings are correctly configured and resolve any issues you may encounter while connecting to your database. ### 1. Verify your database credentials * Ensure that the username, password, and host address are correct and up-to-date. * Confirm that your user account has the necessary privileges to access the database. ### 2. Check your database server * Verify that your database server is up and running. * Ensure that your database server is not experiencing any network issues or undergoing maintenance. ### 3. Confirm the AI2sql connector compatibility * Make sure you are using the correct AI2sql connector that is compatible with your specific database (e.g., MySQL, PostgreSQL, SQL Server.). * Update the connector to the latest version if needed. ### 4. Examine your configuration settings * Revisit your AI2sql configuration settings and ensure that they are correct. * Double-check the connection string or URL for any typos or incorrect values. * Use the IP address instead of the DNS name when entering the host address. ### 5. Inspect your firewall settings * Verify that your firewall is not blocking the AI2sql connector's access to your database server. * Add the AI2sql connector's IPs to your firewall's whitelist, if necessary. (52.151.220.65,52.151.220.76,52.151.220.92,52.151.220.113,52.151.220.203,52.151.220.211,20.119.16.24) ### 6. Check database firewall and reachable address * Ensure that the database firewall settings are not preventing access to the server. * Confirm that the address entered is correct and reachable from the client machine. ### 7. Review your error logs * Carefully review the error logs to identify any specific issues or error codes. * Search for solutions to the specific error codes you find, or reach out to our support team with the error details. If you have gone through the checklist and are still experiencing issues, please contact our support team at with the details of the problem, including any error messages or logs. Our team will be more than happy to assist you in resolving the issue. Note: If the direct connection to your database does not work for you, as an alternative, you can add your DDL (Data Definition Language) script to AI2sql. This way, you can still use our platform to generate SQL queries without directly connecting to your database. Follow the guide below to learn how to add your DDL script to AI2sql: [https://ai2sql.gitbook.io/ai2sql/3.-managing-tables/3.1.-importing-tables-using-ddl](https://ai2sql.gitbook.io/ai2sql/3.-managing-tables/3.1.-importing-tables-using-ddl) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai2sql.gitbook.io/ai2sql/9.-database-connectors/9.7.-troubleshooting-ai2sql-connector-issues-a-comprehensive-checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.