Using Little Snitch to monitor network connections I see:
On 30 Oct 2018, curl tried to establish a connection to www.browserstack.com. The request was denied automatically during login.
Anybody know what that could be to do with, or what the purpose of it is? I searched but did not find.
Could you provide some insight into what is the issue you are facing with regards to 'www.browserstack.com' and 'OS X'? Elaborate on which logs you are referring to?
Related
I have signed up for 30 day trial version for snowflake, as part of learning I am trying to run the Snowsql (client) from my windows desktop. I installed client from snowflake client repository (account name, username and password are all correct).
Got the following error:
C:\Users\ugain>snowsql -a vg49826 -u ugainedi
Password:
**250001 (08001): Failed to connect to DB. Verify the account name is correct: vg49826.snowflakecomputing.com:443. HTTP 403: Forbidden
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!**
Appreciate the help. Thank you!
Go to your account using the Snowflake web UI and look at the URL. Since there is no account vg49826.snowflakecomputing.com, that means you're running Snowflake somewhere other than on AWS_US_WEST_2. That's the only region that does not include the region in the account name for connection purposes.
Copy the portion of the URL up to but not including "snowflakecomputing.com". It will be something like vg49826.us-east-1, vg49826.east-us-2.azure, or something similar. Your Snowflake account, for the purposes of connecting to SnowSQL is the portion of the URL after https:// and before snowflakecomputing.com in the web UI URL.
I have a GCP instance which was running successfully until last week. But suddenly I am not able to ssh into it. I am getting the error
Could not connect, retrying (3/3)
When I tried to find the root cause of it. I somehow managed to learn about os-login and configured it in the instance metadata.
Though my os-login setup was successful and was able to ssh through os-login I am not able to access it since it asks for username and password which I don't have any clue on what to give. I tried so many articles but still failed to understand what to give in that.
I can easily delete the instance and set up it from scratch but all I worry is I am not able to find the root cause of it.
Can someone help me what are the ways to find out the logs/cause for why I am not able to ssh into it suddenly?
I tried seeing the instance logs from the options in the console. But it did not have much info.
Exhausted available authentication methods. Please contact your web hosting service provider for assistance.
I continue to receive this error on Cyberduck. I was able to log into the account when I first downloaded Cyberduck. When I was finished with my work I saved/ closed everything, and it was so far so good. I hadn't logged out of the account. But since I have been trying to log back in I have been receiving this error.
Please help.
If you are using Mac, try removing the application password from Keychain. There's a possibility that the old password is corrupted.
For me, my password was set to "$this->request()". So no matter what I type when connecting, Cyberduck used this "old" password.
You use Cyberduck to connect to an FTP server right?
If it's at all possible that anyone else has access to this account and failed to login a magical number of times (usually 3) then the server may have locked your account and needs to be restarted.
Or something is wrong with the server itself.
I hate to say it but contacting whoever is in charge of the server, as it said, is probably best. Without more information there's no way to know what went wrong.
I tried to remove the application password but it kept failing to connect.
The solution was simply to remove and re-install the app.
In my case i was passing the username wrong.
I typed ununtu instead of ubuntu.
Check you server details you entered.
Here in this case, when a client is trying to access a particular URI, they are able to get a SUCCESS response for GET, but for the POST message, they are recieving a 500 error. Which is nothing but INTERNAL SERVER ERROR.
please look at the ERROR below:
Weblogic Bridge Message
Failure of server APACHE bridge:
Cannot open TEMP post file '/tmp/_wl_proxy/_post_1818_8' for POST of 3978 bytes
Weblogic Bridge Message
Failure of server APACHE bridge:
Internal Server failure, APACHE plugin. Cannot continue.
Eventually this was resolved after giving a 777 permission to /tmp/_wl_proxy and the client was able to access the page SUCCESSFULLY.
If this is a permission issue, then apache should throw 403 error, but i dont know why it was throwing 500 error.
if there is a internal server error, then both GET and POST response should be 500, So if anyone can answer this , it would be a great learning experience. Thanks..!!
You many not want to give Write to all (777) permission to /tmp/_wl_proxy directory. Check which userID apache is running under and only give writer permission to that userID.
This could be also with tmp directory full.
Here is what I did to solve this problem:
Go to weblogic management console (http://:7001/console)
Go to the server section, you will probably find one of your servers' status not running. This is what I found in my case;
Some features couldn't be run unless you have administrative privilege, I advice you stop all servers and re-run them as an administrator as you follow your servers status in the administrative console.
If the above doesn't work, something has to do with your either report or form server configuration is hindering the servers from starting up. In all cases you need to monitor the administration console.
Scenario:
If i try to start the server as a window service it gives an error stating that ceradentials are not correct.However on correcting the credentials in boot.properties when i try to start the server again it gives the same error.Any alternative for starting the server.I gave the same username and password in my startup Script and Boot.properties.
Scenario 2: If i start the server remotely through console then will it come up?
Thanks in advance.
Regards,
Preet
If i try to start the server as a window service it gives an error stating that credentials are not correct.
Then they aren't. Maybe provide more details on what you do exactly and the error message.
If i start the server remotely through console then will it come up?
First, if your credentials are not correct, then it won't change anything. Second, if you don't have a node manager configured, this won't be possible. Provide more details.