Error "Request Timed Out" when connecting to Jira Align Enterprise Insights via DBeaver

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Users attempting to connect to Enterprise Insights (EI) via DBeaver may encounter connectivity issues, receiving a "Request Timed Out" error during the test connection phase. This problem typically arises due to misconfigured encryption settings or network restrictions. The error message displayed to users is:

This message indicates that DBeaver is unable to establish a secure connection with the Enterprise Insights database, which can be attributed to incorrect connection properties or firewall settings blocking the necessary network traffic.

This error suggests that the application is unable to receive a response from the database server within the expected timeframe, often due to:

  • Incorrect encryption settings in the connection configuration.

  • Network firewall rules preventing communication with the database server.

  • Outdated ODBC drivers not supporting the required TLS version.

Solution

To resolve the connectivity issue, follow these detailed steps to adjust your connection settings in DBeaver:

  1. Open DBeaver:

    • Launch the DBeaver application on your machine.

  2. Edit Connection Settings:

    • Navigate to the connection you have set up for Enterprise Insights.

    • Right-click on the connection and select "Edit Connection."

  3. Configure Connection Properties:

    • Go to the "Driver Properties" tab.

    • Ensure that the following properties are set:

      • Encrypt: Set this property to true to enable encryption.

      • TrustServerCertificate: Set this property to true if your network configuration requires it, allowing the connection to proceed even if the server certificate cannot be fully validated.

  4. Test the Connection:

    • Click on the "Test Connection" button to verify that the connection settings are correct.

    • If the connection is successful,

      click "OK" to save the changes and establish the connection.

      1. Firewall and Network Configuration:

        • Ensure that your network allows outbound connections to the IP addresses and ports used by Azure SQL Database:

          • IPs: It is recommended to confirm it with the Jira Align Support Team.

          • Port: 1433 (default for SQL Server)

        • Contact your network administrator to verify that these IPs are allowlisted in your firewall settings, ensuring that your application can communicate with the database server.

      2. Verify TLS Version:

        • Ensure that your ODBC driver supports TLS 1.2 or higher, as required by Azure SQL Database. If necessary, update your driver to the latest version to comply with security protocols.

Additional Troubleshooting

  • If the connection still fails, check the network connectivity to the database server (EI-ADDRESS.database.windows.net) to ensure it is reachable from your environment.

  • Confirm that your database credentials (username and password) are correct and have the necessary permissions to access the database.

  • Consider using SQL Management Studio or Azure Data Studio to test the connection separately, which can help isolate whether the issue is specific to DBeaver.

Updated on April 14, 2025

Still need help?

The Atlassian Community is here for you.