SnowflakeSQLException: JDBC Driver encountered communication error. Message: HTTP status=400

Knowledge Drop

Last tested: Nov 3, 2020
 

HTTPS 400 = Bad Request. See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400

There can be multiple reasons for this, the below are not a full description of all potential root causes but describe some of the reasons for this error:

  • Auth rejection due to SSL: try unchecking SSL
  • Credentials: have customer double confirm credentials inputted in to Looker connection settings
  • Malformed DB hostname or other parameters: are there any whitespaces in the db hostname or in additional params? This will be hard to determine from the UI but the JDBC string or logs should make this more apparent

This content is subject to limited support.                

Comments
creigmalta
New Member

The 400 Bad Request error is an HTTP status code indicates that the request you sent to the webserver was malformed , in other words, the data stream sent by the client to the server didn't follow the rules. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. There are a number of different causes for a 400 Bad Request Error . It might be a malformed request syntax, invalid request message framing, or deceptive request routing . In most cases, the problem is on the website itself, and there's not much you can do about that. To fix a 400 Bad Request error it is best to start diagnosing the issue from the client side itself. Complete the steps outlined in this section to help diagnose and correct the error.

  • Check for errors in the URL.
  • Clear Browser Cache and cookies.
  • Clear DNS Cache.
  • Check your File upload Size.
  • Deactivate Browser Extensions.
  • Contact the site owner to report the 404 error.
Version history
Last update:
‎07-07-2021 12:43 PM
Updated by: