I'm facing a problem whith Lens access to eks around 2 months ago.
I think I tried a lot of solutions but nothing is working for me.
I'm accessing to eks fine on wsl Ubuntu with AWS credentials.
I Installed the last version of Lens
put the kubeconfig file to add eks clusters
change the terminal to "wsl.exe" on Lens
And I have this error:
Starting connection ...
Authentication proxy started
Refreshing connection status ...
Unknown error has occurred
Have you faced this issue before? how did you solve it ?
Thanks in advance for your help.
Related
I am doing my first project on Google Cloud, accessing SSH using the SSH dropdown on my VM instance and was going through the steps to set up the environment to use FileZilla to copy my project, apparently, I waited too long as I was setting up FileZilla and my SSH session timed out. Since then every time I try to access SSH, I get the following error message:
Code: 1006
Please ensure you can make a proper https connection to the IAP for TCP hostname: https://tunnel.cloudproxy.app
You may be able to connect without using the Cloud Identity-Aware Proxy.
This started happening around midnight last night and still going on this morning. I have searched and followed all the instructions pointed out on this link:
https://cloud.google.com/iap/docs/using-tcp-forwarding
and the problem persists. I have even stopped, started, and reset the VM instance which did not resolve the issue. I am hoping someone has any other suggestions I can follow beyond what can be found on this site already.
Thank you in advance for any help and suggestions.
UPDATE:. I still haven't found the solution, but I have found a way to access my instance through my local terminal on my MacBook using the gcloud command from the Google Cloud SDK.
UPDATE: I did some research and I found that I had to delete my access keys and create new ones and it solved the problem.
I'm getting the following message in my VM Ubuntu using GCP when I need to download a big snap shot (100GB). The message keeps coming up after about an hour of uploading. Notice there is no Reason given.
Can anyone suggest a solution?
I have Azure devops pipeline which deploys in Amazon k8s, the pipeline is working very fine and with no issue and it is deploying in k8s.
Mine is a Spring Boot application, when starting the application it makes a connection to Oracle db. And I get the below error.
[nio-8203-exec-3] com.zaxxer.hikari.util.DriverDataSource : Registered driver with driverClassName=oracle.jdbc.driver.OracleDriver was not found, trying direct instantiation.
Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descripto
I suspect this is not the issue , because the same code, the same pipeline, the same k8s is working absolutely fine in different namespace.
The above oracle issue is happening only when the pipeline try to deploy in default namespace.
I tried to telnet to the Oracle server, I get the response just it is that it is not able to connect from default namespace and I don't know why.
Also I have 2 Oracle database one in one prem and other in RDS, both have the same issue in default name space and it was able to connect with no issue from other namespace.
I don't know what is different in default namespace and what to check there.
I finally decided to run a chainlink node on kovan, so I followed this link https://www.youtube.com/watch?v=t9Uknfw27IU&list=LL&index=8&t=555s on how to set up the node and after a few hours of work I made it happen. So after SSH tunneling into localhost:6688 I got the GUI for the chainlink operator and wrote in the password and got in.
So the next day I decided to program some jobs on the node and did the same thing as last day and got the
site can`t be reached - ERR_CONNECTION_RESET when SSH tunneling in localhost:6688 and I can see that the CL node is running in the linux box with no errors and note I dont own a router.
What I tried so far:
-switching browsers
-temporarily disabled the windows firewall
-manually opening up the port 6688
-deleting the VM instance on Google cloud platform and creating a new one
-double checking the .env file if database and other info from GCP and infuras
WSS were correct
-check the proxy settings
-cleared browser history and cookies
-deleted Winsock catalog entries
None of this has helped to resolve this issue, any help or suggestions would really be appreciated...
Managed to fix the issue myself, If anyone has the same error try this: go to your GCP and go to VM istances - firewall and add an exception for port 6688, then copy the externalIP , add it as your localhost= externalIP :6688...worked for me.
I've been running tomcat on my Amazon EC2 instance for a few weeks just fine but all of a sudden, I became unable to connect to it. When I use putty I can connect to it fine but when I try to connect with my browser by using ip:8080 , I can't connect anymore. I've tried restarting the instance (and of course, adjusting my input ip accordingly), restarting the tomcat server within the instance, and checking the security groups. Nothing seems to work. I have no idea why it stopped working out of the blue. How should I proceed?
There are many reasons to why you cannot connect. The best way to solve this is to follow Amazons troubleshooting tips, found here.
I had the same issue. The amazon troubleshooting did not help. Then I remembered that I ad a line in my system32/driver/etc host file when I did some site migration.
Deleted that line and I was back in business again.
Hope that helped