-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNOW-704218: OperationalError: 250001: Could not connect to Snowflake backend after 0 attempt(s).Aborting #1364
Comments
Hi @KevnBlack , looks like the client is unable to connect to Snowflake due to mismatched certificate hostname:
Could you please double check if you are specifying the correct account? |
@sfc-gh-stan I believe so, when copying the account identifier from app.snowflake.com, it pastes "VQFSBGN.KE53115" |
You locator is |
Using that as the account returns the same 250001 error unfortunately. |
Hi @KevnBlack , 250001 is a general error code, is the underlying error still |
@sfc-gh-stan Hey that worked! Turns out you needed a "-" instead of a "." like what some people have suggested online. Thanks Sophie, successfully returned 6.39.0. |
Hello @sfc-gh-stan I am facing the same error and I am using the correct orgname-accountname in my conf file. I read that it might be an OCSP issue and so I used -o insecure_mode=True to surpass that but I still get "250003: 250003: Failed to get the response" , which is followed by "250001: 250001: Could not connect to Snowflake backend after 0 attempt(s)". I really need to get past this, please help. |
same issue with me ZahraMalwi . got any solution??? |
@sfc-gh-stan thanks for the answer! It's funny that the |
Sorry not clear @sfc-gh-stan , Can you please give steps to find copy identifier on Snowflake UI . I am also getting same issue |
hi folks, so a little recap. This is not really helpful in itself :) that's why we frequently recommend to enable debug level logs, repeat the connection attempt, then look into the debug logs. It usually provides vast amount of details to at least start the investigation. If you're not comfortable doing to yourself, and of course sharing it here for the public to see, you can always open a Snowflake Support case to work with a support engineer 1:1. You can do so from the GUI without logging into anywhere. Also there's no guarantee anyone will look at a Closed issue from two years back, i'm afraid. So if you have an issue which you feel it's coming from the PythonConnector (this library), and not some network connectivity or misconfiguration issue, please open a new Issue. Thank you ! What is your account identifier: go to GUI -> click on your username bottom-left -> click Account -> mouseover your account name, another frame opens -> in this new frame, click on 'Copy account identifier' -> Example: it will copy Read more about how Snowflake account identifiers are constructed. Hope this helps. |
Same as above. I got the same stacktrace and same error with ssl certificate verify failed. For me it was nothing related to SSL. When you copy your account from snowflake it introduces a dot (e.g., FDA3FS.AFDSA), I had to insert a dash instead (e.g., FDA3FS-AFDSA). Afterwards, we use private links in our org so we literally had to add privatelink so at the end, this is what worked for me (e.g., FDA3FS-AFDSA.privatelink) |
What version of Python are you using?
Python 3.9.12 (main, Apr 4 2022, 05:22:27) [MSC v.1916 64 bit (AMD64)]
What operating system and processor architecture are you using?
Windows-10-10.0.22621-SP0 AMD64
What are the component versions in the environment (
pip freeze
)?What did you expect to see?
A successful query execution that returns the current version of Snowflake, which should be 6.39.0.
Can you set logging to DEBUG and collect the logs?
Log attached due to GitHub character limit.
snowflake_log.txt
The text was updated successfully, but these errors were encountered: