PostgreSQL: A call to SSPI failed, see internal exception

PostgreSQL: A call to SSPI failed, see internal exception

"A call to SSPI failed, see internal exception" indicates that the security protocol (SSL/TLS) used in your PostgreSQL connector does not match the version supported by your server. To resolve this, we recommend trying different SSL/TLS protocol versions in your connection settings in Skyvia.



You can also contact your database administrator to confirm the SSL/TLS version configured on your PostgreSQL server and ensure the same version is specified in the connector. Additionally, please double-check that all other connection settings are configured correctly.

    • Related Articles

    • MySQL: Resolving "Lost connection to MySQL server during query" Error

      To resolve the "Lost connection to MySQL server during query" error, please follow the steps below: Increase the "Command Timeout" value for your MySQL connection: Go to the Connections page and select your MySQL connection. Click Edit. In the ...

    • Salesforce API errors: TotalRequests Limit Exceeded/ApiBatchItems Limit Exceeded

      The TotalRequests Limit Exceeded and ApiBatchItems Limit Exceeded errors are Salesforce-specific errors indicating that you have reached specific API limits on the Salesforce platform. Please find explanations of each error and relevant documentation ...

    • 🔒Skyvia IPs for Whitelist

      Skyvia will access your server from one of the following IP addresses: 40.118.246.204 13.86.253.112 52.190.252.0 To ensure proper functionality of your connections, all of these IP addresses must be whitelisted.

    • Freshdesk: The Limit of Freshdesk API Calls Per Hour Has Been Reached

      This error occurs on the Freshdesk side, indicating that the API call limit for the hour has been exceeded. For more details on Freshdesk's API limits, refer to their API documentation. Freshdesk enforces a limit on the number of API calls that can ...

    • Tips for Managing Integration Queue Times

      Generally, when integrations start running, they are placed in a queue for execution before processing records begins. Integrations can be queued during server peak loads (such as at the beginning of every hour, e.g., 11:00, 12:00, etc.) when there ...