I use snowflake and snowsight on windows OS. And, I did the below command but the error happened.
Do you have the answer about this error 250001 (n/a)?
C:\Docs>snowsql -a lvXXXXX.ap-northeast-1.aws -u username -o log_level=DEBUG
Password:
250001 (n/a): Could not connect to Snowflake backend after 0 attempt(s).Aborting
If the error message is unclear, enable logging using -o log_level=DEBUG and see the log to find out the cause. Contact support for further help.
Goodbye!
The error message appears to be an issue with "Failed to check OCSP response cache file."
You can try to connect using insecure mode to bypass the OCSP checks.
Use this:
snowsql -a lvXXXXX.ap-northeast-1.aws -u username -o insecure_mode=True
If the connection is successful, it means there may be a firewall/proxy that is blocking the connection to the OCSP server. Note: OCSP connects via port 80.
Related
I encountered this error when trying to connect to my Snowflake account by SnowSQL. Any suggestion what might be the issue and how to resolve it?
% snowsql -a https://*****.us-east-2.aws.snowflakecomputing.com/ -u *****
Password:
250003 (n/a): Failed to execute request: HTTPSConnectionPool(host='https', port=443): Max retries exceeded with url: //*****.us-east-2.aws.snowflakecomputing.com/.snowflakecomputing.com:443/session/v1/login-request?request_id=6585191e-6947-487e-acae-c2cfc777bd1c (Caused by NewConnectionError('<snowflake.connector.vendored.urllib3.connection.HTTPSConnection object at 0x7f8dc80205f8>: Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known',))
If the error message is unclear, enable logging using -o log_level=DEBUG and see the log to find out the cause. Contact support for further help.
You may try the below syntax:
snowsql -a [accountname].us-east-2.aws -u [username]
Details: https://docs.snowflake.com/en/user-guide/snowsql-start.html#connection-syntax
One thing I always try is to make sure I can login from the console/UI with the username and password - before I tackle snowsql connectivity issues. You might have already tried, lmk.
Also, it appears you left off your account name from the URL... was that on purpose (for confidentiality) or a possible problem with URL?
The correct account for use with the snowsql command appears to be account.region.cloud provider. For example: XXXXXXX.eu-west-2.aws.
The whole command with an example account and username:
snowsql -a ocXXXXX.eu-west-2.aws -u myusername
encountering Error while try to connect using CMD (Admin)
250003 (n/a): Failed to execute request: HTTPSConnectionPool(host='https Failed to establish a new connection.
Snowflake account is on Azure.
Thanks in Advance
Based on your comment, the problem is when using the account option:
>snowsql -a XXXX.west-us-2.azure.snowflakecomputing.com -u username
The account should not include this part .snowflakecomputing.com, so your call should be:
>snowsql -a XXXX.west-us-2.azure -u username
I also faced the same issue while giving the hostname as https://xxxxxxxx.us-east-1.snowflakecomputing.com, then I removed https://. It connected successfully.
First I get this error "connect to address 10.0.0.102 and port 12489: Connection refused", then I made some changes according to forums and I changed nclient.ini file. I adjusted the allowed hosts and password.
Then server side the Status Information is changed. Now I get this error in Nagios Admin Panel:
NSClient - ERROR: Invalid password.
However, at Nagios XI Server I checked password and it's same as in nsclient.ini file on client side.
I used this command to check:
/usr/local/nagios/libexec/check_nt -H 'hostname' -s nagpasswd -p 12489 -v CPULOAD -w 80 -c 90 -l 5,80,90,10,80,9 NSClient
What might be the issue? Any help would be perfect.
after changing the password , you need to restart your nagios service once
I installed on my arch machine mssql-server and mssql-tools via yaourt. I started the server from /opt/mssql/bin/sqlservr and tried to connect with my credentials, but with no luck. I found this article which says to connect with the command sqlcmd -S localhost -U SA -P 'YourPasswordHere', but it didn't work either. The error message says:
2017-07-06 21:57:28.25 Logon Error: 18456, Severity: 14, State:
7.
2017-07-06 21:57:28.25 Logon Login failed for user 'SA'. Reason:
An error occurred while evaluating the password. [CLIENT: 127.0.0.1]
I tried with blank password, with Password123 and with my user's password but the message was the same.
Has anyone managed to connect and if yes what was the default password?
Please let me know if you need any further information.
Thanks.
I found it. I had to run this command sudo /opt/mssql/bin/mssql-conf setup in order to set the password for the SA user. Now I can connect.
I have a postgres database that I created through heroku. I am trying to access it through psql with the command:
cse-190-fortune matanvardi$ psql "dbname=dccemfsa6camml host=ec2-54-235-152-226.compute-1.amazonaws.com \
user=tfmfbqxqjznsbl password=********* port=5432 sslmode=require"
I get this error:
psql: could not connect to server: Operation timed out
Is the server running on host "ec2-54-235-152-226.compute-1.amazonaws.com" and accepting
TCP/IP connections on port 5432?
I've cloned the repository and I'm logged in, I simply cannot figure out what is wrong here. Any help would be greatly appreciated.
To access your Heroku database from the command line use the command:
heroku pg:psql
Edit:
I ran your command from my machine. If course I don't have your password but I got:
$ psql "dbname=dccemfsa6camml host=ec2-54-235-152-226.compute-1.amazonaws.com user=tfmfbqxqjznsbl port=5432 sslmode=require"
Password:
psql: FATAL: password authentication failed for user "tfmfbqxqjznsbl"
Which means I was able to connect, which is farther than you got. It must be a problem with your network setup.