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.
Related
After setting up my lightsail instance I tried to follow the instructions at bitnami
I used the ssh -N -L 8888:127.0.0.1:80 -i file.pem bitnami#ip to connect.
I get the expected result with nothing returned in the terminal. Now when I try to visit 127.0.0.1:8888/phpmyadmin I get an error from FF saying unable to connect. I have also tried switching the port to 433 incase that was the issue and visited 127.0.0.1:8443/phpmyadmin and still no luck.
another post suggested I add a slash at the end, that didnt work either. I have turned of my local apache server on my ubuntu machine as I felt that would help yet no show.
I have also ensured I didnt accidentally close the terminal
Any ideas ?
The issue seemed to be that the key file didnt have the right permissions.Once I corrected the permissions as specified in the docs I was able to connect but so far have got the https connection to work and just use http which is less than ideal
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
I've been running an instance EC2 through Laravel forge for about 2000 hours and this morning got this error while trying to reach it:
SQLSTATE[08006] [7] could not connect to server: Connection refused Is
the server running on host "172...***" and accepting TCP/IP
connections on port 5432?
After SSHing into the server I've getting a similar error when trying to run a command. I've dug through AWS but don't see any errors being throw. I double checked the ip address for the instance to make sure the IP hadn't changed for any reason. Of course I'm a little behind on my backups for the application so I'm hoping someone might have some ideas why else I can do to try and access this data. I haven't made any changes to the app in about 10 days, but found the error while I was pushing an update. I have six other instances of the same app that weren't affected (thankfully) but makes me even more confused with the cause of the issue.
In case anyone comes across a similar issue, here's what had happened. I had an error running in the background which had filled up the EC2 harddrive's log. Since the default Larvel/Forge image has a DB running within in the EC2 instance, once it ran out of room everything stopped working. I was able to SSH in and delete the log though, and everything started working again.
To prevent the issue from happening again I then created an amazon RDS and used that rather than the EC2 instance. It's about three or four times the price of just an EC2 instance, but still not that much and the confidence I now have in the system is well worth it.
After installing VMware Server I get the following error when I try to access the VMware web-based server manager:
The VMware Infrastructure Web Service
at "http://localhost:8222/sdk" is not
responding
Go into the services manager and check that the 'VMware Host Agent' service is running. If not, then start it and then try browsing to the site again.
Vmware Hostd was not working for me either.
However, in trying to start the service it stopped automatically. Typically when this happens it is because there is an error in your config.xml.
C:\ProgramData\VMware\VMware Server\hostd\config.xml
In my case, checking the logs at:
C:\ProgramData\VMware\VMware Server
showed it erroring out after "Trying hostsvc".
Searching the config.xml for hostsvc showed references to several things, the first thing was the datastore. In checking my datastores.xml file:
C:\ProgramData\VMware\VMware Server\hostd\datastores.xml .
I found it full of all sorts of random characters instead of a properly formed XML document.
Renaming datastores.xml to datastorex.xml.bad allowed me to start the service. At which point I had to add back my datastores through the GUI.
Hopefully this will help someone else out. I did not find any other references in Google to this issue.
Try accessing via "http://localhost:8222" without the /sdk. You can also try the secure site via "https://localhost:8333".