In the Google Cloud Platform Console, upon clicking "Activate Cloud Shell," the bar for the command line shows up and displays "Provisioning your Google Cloud Shell Machine" and "Establishing your connection to Google Cloud Shell," but after that the entire box for the command line goes blank. It still has the option bar that displays the project name, option to open the text editor, etc. I tried going to the text editor hoping that the command line would show itself there, but the whole box remained blank.
Even worse, I started one of my virtual machines and used the SSH option from the console to connect to it, and the SSH window similarly went totally blank. Any ideas what's going wrong here? I'm using Firefox on Windows 10 and haven't had any issues using the Cloud Shell for months.
This was a browser compatibility problem between FF64 and the Google Cloud Shell terminal emulator library. The SSH-in-the browser feature inside Cloud Console is using the same terminal emulator, so it was affected as well. Both have now been fixed.
I had a similar issue. Google cloud shell doesn't work with Firefox.
I waited for a whole thirty minutes and nothing happened. Thirty! I switched to Chrome and the issue was sorted out immediately.
Related
In windows terminal (latest version) I am trying to open an Azure Cloud Shell. Functionality is working, however I am unable to read the display as when I set focus to the window, it becomes obscured (foreground shading is applied). When I select a different window, the terminal returns to normal.
Does anyone know how to change the theme to something useful or to turn off this foreground shading?
Regards
In writing out the bug as mentioned above I found I needed to delete my old settings file. Once I did this, and restarted terminal it started working.
I note when the azure shell is started, it briefly becomes transparent before updating itself.
I've been moving step-by-step (as a webdev newbie) through the GatsbyJS installation via the Terminal. All looked great, except the Terminal appears "stuck" and I'm not sure how to resolve (i.e. whether to close Terminal app or let the process continue). It's been over an hour without any change in the Terminal prompt. Please see screenshot for detailed info. Any help would be much appreciated.
screenshot: Current state of Terminal app:
screenshot: Message when trying to close Terminal app:
Your terminal is not stuck. Everything works as it should.
It is listening to code changes which enables hot reloading. This way you can change code and you see the changes almost instantly in your browser. This makes for a pleasant developer experience and is industry standard.
Beware the old times when you had to manually restart your server everytime you made the tiniest code change.
Try opening a browser with url http://localhost:8000. Change some text inside your index.js. You should see it reload in the browser.
Prior to reverting my computer back to factory specs I was able to use the command (⌘) key to copy and paste things from my clip board into the sshed shell when connected to GCP . Now, I am no longer able to use ⌘ things to copy and paste between the terminal and the rest of my laptop.
I have only seen this issue with GCE (Google Compute Engine) and can use the ⌘ command in terminal but not while I am sshed into GCP.
For reference I use the following GCP command to connect:
gcloud beta compute --project "project-name" ssh --zone "zone-name" "instance-name"
I am not sure if this is specific to google cloud or ssh in general but any tips / feedback would be appreciated.
I don't think that this has anything to do with GCP, but more with the Key Configuration on Mac OS itself. Have you tried to contact Mac Support?
From the GCP documentation all I found was: "Keyboard Shortcuts for Google Cloud Platform". Where they have a note stating that:
"Note: Some shortcuts might not work for all languages or keyboard formats, and available shortcuts might differ depending on which console page you are on."
Sorry for the bother, all I had to do was check off "Secure Keyboard Entry" by clicking on the tool bar and everything works as expected now.
I want to stuff remote debugging and other esoteric dev-only only parameters to the Chrome application when it starts but I want it to be always there, including when I click on the app icon.
E.g.:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
How do I pass these command line parameters to the app directly?
I ended up creating an automator application with as shell task. Customized the icon and replaced Chrome.app with the new app in the dock.
I am still looking for a way to change the settings in Chrome so it can connect with remote debugger "on-demand" for specific tasks (not everything as it is set now) but that doesn't seem to be possible at this time. The VSCode folks have apparently solicited the Chrome team to provide this functionality. Stay tuned...
In the AWS Management Console, I select an EC2 instance and then I click "Connect" from the Instance Actions menu. I see the following popup window:
Instead of the fields I should normally see, I get the above message about enabling java in my browser. But java is enabled in my browser. I tested it with this page to confirm. I'm running Java SE 6 Update 24.
I'm using Google Chrome v20.0 on Linux Mint 13 64bit. I also tried with Firefox and the result is the same. I can access Java SSH Client without any problem from my Windows box, so it may be a Linux-specific issue.
Use Firefox or safari, it works fine.
Refer to the link below for more information.
Chrome browser versions 42 and above. Starting with Chrome version 42 (released April 2015), Chrome has disabled the standard way in which browsers support plugins.
https://java.com/en/download/help/browser_activate_plugin.xml
Try option 1, a stand alone ssh and then open terminal use the chmod command to change the permissions then ssh -i.... command(Example is given in the Launch instance box on AWS).
After doing this you will see bitmap on your terminal, that means you are in.
Then use cd apps/parse/htdocs. This will take you to htdocs where most parse server files are stored. Then use vi filename.js which opens a tex editor to edit the file you want.
Hope that was useful.
Try with java 32 bit version.. most browsers don't support 64 bit java..