-
Notifications
You must be signed in to change notification settings - Fork 16
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
connection error #29
Comments
👋 the The regular pattern of the account is: If you're connecting to snowflake not via the listed account locators but through an internally managed proxy then it's currently not supported by this sql client. btw, a new version (0.4.2) of the sql client is published to VSCode Marketplace with some more information on the connection form. Can you please upgrade, try again and let me know how is it going? |
Thank you for your response. My apology for a late reply. With regards to the example Thanks you very much in advance. |
I'm presuming yo fixed it. If not I suggest installing snowsql https://docs.snowflake.com/en/user-guide/snowsql-start.html and then on linux/mac login via |
Hi anujghai, I haven't found a fix yet. I was able to get it work on Python through the snowflake-connector-python but once I copy and paste the same credentials (account name and password) to this connector, the connection didn't go through. |
Okay, I tested with the python connector using a script like below (Replace with yours). Once tested I used the Snowflake Driver with the same user account,user, password as my test and included the database warehouse and schema and warehouse with OOSCP Fail-Open ticked and get a connection. uname = input('Enter Username: ') |
@fishstoryyy - did you ever find a solution here? My account name is companyname.eu-west-1 and I receive the same error. Again, it works just fine with the python connector. |
Hi everyone, I am getting the following network error when testing a connection.
Not sure if it is caused by my account name. My account name (the part left to .snowflakecomputing.com) follows a format like this:
letters_only.us-east-1.companyname
If the account name is not the cause, could it be a proxy issue?
Can someone please help? Really looking forward to making use of this extension.
The text was updated successfully, but these errors were encountered: