Connection via Cloud Identity-Aware Proxy Failed Code: 6001 Reason [BLANK] - google-cloud-platform

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?

Related

How do I resolve a connectivity issue to Google Cloud using SSH?

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.

red5 streaming server on GCP vm using red5pro-installer app not working with "sample" stream

I have tried installing the red5pro streaming service on a vm with a trial account in google cloud platform. I have used the red5pro-installer repo from github to do the "automatic" installation as well as tried installing everything manually.
When I use the installer, the web page works for me when I browse to my vm. I am able to see my webcam's image on the "sample" stream page from the "broadcast" page of the vm. I then enter a stream name and hit the "start broadcast" button and it starts to spin up then throws an error indicating "Publisher.Connection.Closed" (see attached image).
In looking at the logs on the VM, these two errors stand out:
2021-08-05 22:19:35,142 [https-jsse-nio2-0.0.0.0-443-exec-7] WARN c.r.webrtc.stream.RTCSourceStream - ICE sockets not starting for: stream1
2021-08-05 22:19:35,141 [https-jsse-nio2-0.0.0.0-443-exec-7] INFO com.red5pro.override.ProStream - Connection was null so cleanup is skipped
I have verified that all of the necessary ports are open for the correct traffic type on the GCP firewall to the VM.
I have also tried browsing to the vm via port 5080, and when I attempt to start a broadcast there, my webcam image is not showing and I see an error in the output window that says "no suitable publisher found".
Not sure where to turn next.
TIA

Connecting an ESP8266 to AWS IoT Core - getting "WiFiClientSecure SSL error: Unknown error code."

I am trying my first ever IoT project with an ESP8266 connecting to AWS IoT core. I've checked all my certificates, setup etc and they appear to be correct. However, when I run my code to publish a simple "Hello World" message to AWS IoT, I get:
Attempting MQTT connection...pm open,type:2 0
failed, rc=-4 try again in 5 seconds
WiFiClientSecure SSL error: Unknown error code.
Any help would be greatly appreciated. If you need any more detail, I'd be happy to provide it.
Thanx,
ramesh.
I ran into a similar issue and what I ended up finding is that you have to set your certificates BEFORE you connect to the WiFi.
So try and make sure that you are setting those before calling WiFi.begin(ssid, password)

After SSH tunneling into localhost:6688 I get "site can`t be reached - ERR_CONNECTION_RESET"?

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.

AWS Workspaces client on Ubuntu give display error

Im trying to connect to my Amazon Workspace using the Workspace client on Ubuntu. I keep getting this. I can connect no problem from my windows machine at work, but keep getting Display Error at home on my linux machine. .
I had same trouble but solved the problem. Please try following process.
Uninstalled AWS.
Re-start PC and installed AWS again.
Wait for couple of hours. while you waiting, try to keep pushing Refresh button or re-start AWS again and again untill the windows shows log in screen.Because it may take some time to clear old registration information and refresh it in the host side according my IT dept says.
Anyway, I've sent the log files to the AWS help desk and are waiting for their reply.
good luck!
Here we can not assume that it is not working because of so and so reasons, instead we should exactly get to know the root cause for this error. So in order to get the RCA, check the log files present in this directory:
C:\Users\yourname\AppData\Local\Amazon Web Services\Amazon WorkSpaces\logs
So, for me, it was showing the AWS URL access was forbidden.