SSH browser doesn't work in Compute Engine GCP












0















When i click the SSH button in the Complete Engine page, the shell window pops up and it shows that the ssh keys are being migrated. After that dialog disappears, nothing happens. I get a blank page without any prompt.



Loading SSH



Blank shell










share|improve this question

























  • cloud.google.com/compute/docs/instances/…

    – Martin Zeitler
    Jan 1 at 16:20











  • Which browser? Lately there have been reports of issues with Firefox and Edge. For GCP I would use Chrome.

    – John Hanley
    Jan 1 at 17:55











  • Are you on the default network?

    – night-gold
    Jan 1 at 21:29
















0















When i click the SSH button in the Complete Engine page, the shell window pops up and it shows that the ssh keys are being migrated. After that dialog disappears, nothing happens. I get a blank page without any prompt.



Loading SSH



Blank shell










share|improve this question

























  • cloud.google.com/compute/docs/instances/…

    – Martin Zeitler
    Jan 1 at 16:20











  • Which browser? Lately there have been reports of issues with Firefox and Edge. For GCP I would use Chrome.

    – John Hanley
    Jan 1 at 17:55











  • Are you on the default network?

    – night-gold
    Jan 1 at 21:29














0












0








0








When i click the SSH button in the Complete Engine page, the shell window pops up and it shows that the ssh keys are being migrated. After that dialog disappears, nothing happens. I get a blank page without any prompt.



Loading SSH



Blank shell










share|improve this question
















When i click the SSH button in the Complete Engine page, the shell window pops up and it shows that the ssh keys are being migrated. After that dialog disappears, nothing happens. I get a blank page without any prompt.



Loading SSH



Blank shell







google-cloud-platform google-compute-engine






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 3 at 14:48









Joan Grau

1,318214




1,318214










asked Jan 1 at 16:18









Depanshu DhimanDepanshu Dhiman

966




966













  • cloud.google.com/compute/docs/instances/…

    – Martin Zeitler
    Jan 1 at 16:20











  • Which browser? Lately there have been reports of issues with Firefox and Edge. For GCP I would use Chrome.

    – John Hanley
    Jan 1 at 17:55











  • Are you on the default network?

    – night-gold
    Jan 1 at 21:29



















  • cloud.google.com/compute/docs/instances/…

    – Martin Zeitler
    Jan 1 at 16:20











  • Which browser? Lately there have been reports of issues with Firefox and Edge. For GCP I would use Chrome.

    – John Hanley
    Jan 1 at 17:55











  • Are you on the default network?

    – night-gold
    Jan 1 at 21:29

















cloud.google.com/compute/docs/instances/…

– Martin Zeitler
Jan 1 at 16:20





cloud.google.com/compute/docs/instances/…

– Martin Zeitler
Jan 1 at 16:20













Which browser? Lately there have been reports of issues with Firefox and Edge. For GCP I would use Chrome.

– John Hanley
Jan 1 at 17:55





Which browser? Lately there have been reports of issues with Firefox and Edge. For GCP I would use Chrome.

– John Hanley
Jan 1 at 17:55













Are you on the default network?

– night-gold
Jan 1 at 21:29





Are you on the default network?

– night-gold
Jan 1 at 21:29












4 Answers
4






active

oldest

votes


















0














To use the browser to SSH to a GCE instance, you need to be a compute instance admin. Also, if you run that instance with a Service Account, your account need to be a Service Account user. Check this link for more information: https://cloud.google.com/compute/docs/ssh-in-browser






share|improve this answer































    0














    In addition, did you check that your firewall allows connections to SSH port (22) from Google IP ranges ?



    You can find them by using these commands (see https://support.google.com/a/answer/60764)



    nslookup -q=TXT _netblocks.google.com 8.8.8.8
    nslookup -q=TXT _netblocks2.google.com 8.8.8.8
    nslookup -q=TXT _netblocks3.google.com 8.8.8.8





    share|improve this answer































      0














      You can try different methods of connecting an instance to see if the issue is underlying at SSH or somewhere else.



      There are several ways to connect a Linux instance via the SSH. You can connect to an instance via the terminal. You can connect via the Cloud Console Web UI which is in general the most convenient way to connect to an instance. Also, you can use Google Cloud SDK and run below command to connect to an instance via SSH:



      $ gcloud compute ssh [INSTANCE_NAME]


      You can also use Cloud Shell to connect your instance from the Cloud Console web UI by using the same command as above. You can connect via the serial console using the Google Cloud Platform Console, the gcloud command-line tool, or a third-party SSH client. The serial console authenticates users with SSH keys. Specifically, you must add your public SSH key to the project or instance metadata, and store your private key on the local machine from which you want to connect. There are other advanced methods to connect to an instance.



      I would also recommend to check if you have firewall rule for port 22 which is required for SSH. You can go to the VPC Network from Cloud Console and then Firewall Rules tab, check if you have firewall rule for port 22 and that rule applied to affected instance or not. If there no firewall rule for port 22, create firewall rule and apply to the affected instance.



      You can also follow this SSH troubleshooting steps mentioned at this link.






      share|improve this answer































        0














        I have the same problem and after recreating 4 instances and going thru every possible ssh key scenario I decided to try chrome and it worked fine whereas in firefox i get the blank black screen after the key handshake. I watched thru the serial port and the sys log showed all of the same entries for my broken web ssh session in firefox as it did for the working chrome web ssh session which means it has to be a problem with firefox.






        share|improve this answer























          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997002%2fssh-browser-doesnt-work-in-compute-engine-gcp%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          4 Answers
          4






          active

          oldest

          votes








          4 Answers
          4






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          To use the browser to SSH to a GCE instance, you need to be a compute instance admin. Also, if you run that instance with a Service Account, your account need to be a Service Account user. Check this link for more information: https://cloud.google.com/compute/docs/ssh-in-browser






          share|improve this answer




























            0














            To use the browser to SSH to a GCE instance, you need to be a compute instance admin. Also, if you run that instance with a Service Account, your account need to be a Service Account user. Check this link for more information: https://cloud.google.com/compute/docs/ssh-in-browser






            share|improve this answer


























              0












              0








              0







              To use the browser to SSH to a GCE instance, you need to be a compute instance admin. Also, if you run that instance with a Service Account, your account need to be a Service Account user. Check this link for more information: https://cloud.google.com/compute/docs/ssh-in-browser






              share|improve this answer













              To use the browser to SSH to a GCE instance, you need to be a compute instance admin. Also, if you run that instance with a Service Account, your account need to be a Service Account user. Check this link for more information: https://cloud.google.com/compute/docs/ssh-in-browser







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jan 1 at 18:24









              pogaopogao

              12




              12

























                  0














                  In addition, did you check that your firewall allows connections to SSH port (22) from Google IP ranges ?



                  You can find them by using these commands (see https://support.google.com/a/answer/60764)



                  nslookup -q=TXT _netblocks.google.com 8.8.8.8
                  nslookup -q=TXT _netblocks2.google.com 8.8.8.8
                  nslookup -q=TXT _netblocks3.google.com 8.8.8.8





                  share|improve this answer




























                    0














                    In addition, did you check that your firewall allows connections to SSH port (22) from Google IP ranges ?



                    You can find them by using these commands (see https://support.google.com/a/answer/60764)



                    nslookup -q=TXT _netblocks.google.com 8.8.8.8
                    nslookup -q=TXT _netblocks2.google.com 8.8.8.8
                    nslookup -q=TXT _netblocks3.google.com 8.8.8.8





                    share|improve this answer


























                      0












                      0








                      0







                      In addition, did you check that your firewall allows connections to SSH port (22) from Google IP ranges ?



                      You can find them by using these commands (see https://support.google.com/a/answer/60764)



                      nslookup -q=TXT _netblocks.google.com 8.8.8.8
                      nslookup -q=TXT _netblocks2.google.com 8.8.8.8
                      nslookup -q=TXT _netblocks3.google.com 8.8.8.8





                      share|improve this answer













                      In addition, did you check that your firewall allows connections to SSH port (22) from Google IP ranges ?



                      You can find them by using these commands (see https://support.google.com/a/answer/60764)



                      nslookup -q=TXT _netblocks.google.com 8.8.8.8
                      nslookup -q=TXT _netblocks2.google.com 8.8.8.8
                      nslookup -q=TXT _netblocks3.google.com 8.8.8.8






                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jan 2 at 13:19









                      Mikael GibertMikael Gibert

                      9515




                      9515























                          0














                          You can try different methods of connecting an instance to see if the issue is underlying at SSH or somewhere else.



                          There are several ways to connect a Linux instance via the SSH. You can connect to an instance via the terminal. You can connect via the Cloud Console Web UI which is in general the most convenient way to connect to an instance. Also, you can use Google Cloud SDK and run below command to connect to an instance via SSH:



                          $ gcloud compute ssh [INSTANCE_NAME]


                          You can also use Cloud Shell to connect your instance from the Cloud Console web UI by using the same command as above. You can connect via the serial console using the Google Cloud Platform Console, the gcloud command-line tool, or a third-party SSH client. The serial console authenticates users with SSH keys. Specifically, you must add your public SSH key to the project or instance metadata, and store your private key on the local machine from which you want to connect. There are other advanced methods to connect to an instance.



                          I would also recommend to check if you have firewall rule for port 22 which is required for SSH. You can go to the VPC Network from Cloud Console and then Firewall Rules tab, check if you have firewall rule for port 22 and that rule applied to affected instance or not. If there no firewall rule for port 22, create firewall rule and apply to the affected instance.



                          You can also follow this SSH troubleshooting steps mentioned at this link.






                          share|improve this answer




























                            0














                            You can try different methods of connecting an instance to see if the issue is underlying at SSH or somewhere else.



                            There are several ways to connect a Linux instance via the SSH. You can connect to an instance via the terminal. You can connect via the Cloud Console Web UI which is in general the most convenient way to connect to an instance. Also, you can use Google Cloud SDK and run below command to connect to an instance via SSH:



                            $ gcloud compute ssh [INSTANCE_NAME]


                            You can also use Cloud Shell to connect your instance from the Cloud Console web UI by using the same command as above. You can connect via the serial console using the Google Cloud Platform Console, the gcloud command-line tool, or a third-party SSH client. The serial console authenticates users with SSH keys. Specifically, you must add your public SSH key to the project or instance metadata, and store your private key on the local machine from which you want to connect. There are other advanced methods to connect to an instance.



                            I would also recommend to check if you have firewall rule for port 22 which is required for SSH. You can go to the VPC Network from Cloud Console and then Firewall Rules tab, check if you have firewall rule for port 22 and that rule applied to affected instance or not. If there no firewall rule for port 22, create firewall rule and apply to the affected instance.



                            You can also follow this SSH troubleshooting steps mentioned at this link.






                            share|improve this answer


























                              0












                              0








                              0







                              You can try different methods of connecting an instance to see if the issue is underlying at SSH or somewhere else.



                              There are several ways to connect a Linux instance via the SSH. You can connect to an instance via the terminal. You can connect via the Cloud Console Web UI which is in general the most convenient way to connect to an instance. Also, you can use Google Cloud SDK and run below command to connect to an instance via SSH:



                              $ gcloud compute ssh [INSTANCE_NAME]


                              You can also use Cloud Shell to connect your instance from the Cloud Console web UI by using the same command as above. You can connect via the serial console using the Google Cloud Platform Console, the gcloud command-line tool, or a third-party SSH client. The serial console authenticates users with SSH keys. Specifically, you must add your public SSH key to the project or instance metadata, and store your private key on the local machine from which you want to connect. There are other advanced methods to connect to an instance.



                              I would also recommend to check if you have firewall rule for port 22 which is required for SSH. You can go to the VPC Network from Cloud Console and then Firewall Rules tab, check if you have firewall rule for port 22 and that rule applied to affected instance or not. If there no firewall rule for port 22, create firewall rule and apply to the affected instance.



                              You can also follow this SSH troubleshooting steps mentioned at this link.






                              share|improve this answer













                              You can try different methods of connecting an instance to see if the issue is underlying at SSH or somewhere else.



                              There are several ways to connect a Linux instance via the SSH. You can connect to an instance via the terminal. You can connect via the Cloud Console Web UI which is in general the most convenient way to connect to an instance. Also, you can use Google Cloud SDK and run below command to connect to an instance via SSH:



                              $ gcloud compute ssh [INSTANCE_NAME]


                              You can also use Cloud Shell to connect your instance from the Cloud Console web UI by using the same command as above. You can connect via the serial console using the Google Cloud Platform Console, the gcloud command-line tool, or a third-party SSH client. The serial console authenticates users with SSH keys. Specifically, you must add your public SSH key to the project or instance metadata, and store your private key on the local machine from which you want to connect. There are other advanced methods to connect to an instance.



                              I would also recommend to check if you have firewall rule for port 22 which is required for SSH. You can go to the VPC Network from Cloud Console and then Firewall Rules tab, check if you have firewall rule for port 22 and that rule applied to affected instance or not. If there no firewall rule for port 22, create firewall rule and apply to the affected instance.



                              You can also follow this SSH troubleshooting steps mentioned at this link.







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Jan 3 at 2:04









                              Rahi RRahi R

                              434110




                              434110























                                  0














                                  I have the same problem and after recreating 4 instances and going thru every possible ssh key scenario I decided to try chrome and it worked fine whereas in firefox i get the blank black screen after the key handshake. I watched thru the serial port and the sys log showed all of the same entries for my broken web ssh session in firefox as it did for the working chrome web ssh session which means it has to be a problem with firefox.






                                  share|improve this answer




























                                    0














                                    I have the same problem and after recreating 4 instances and going thru every possible ssh key scenario I decided to try chrome and it worked fine whereas in firefox i get the blank black screen after the key handshake. I watched thru the serial port and the sys log showed all of the same entries for my broken web ssh session in firefox as it did for the working chrome web ssh session which means it has to be a problem with firefox.






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      I have the same problem and after recreating 4 instances and going thru every possible ssh key scenario I decided to try chrome and it worked fine whereas in firefox i get the blank black screen after the key handshake. I watched thru the serial port and the sys log showed all of the same entries for my broken web ssh session in firefox as it did for the working chrome web ssh session which means it has to be a problem with firefox.






                                      share|improve this answer













                                      I have the same problem and after recreating 4 instances and going thru every possible ssh key scenario I decided to try chrome and it worked fine whereas in firefox i get the blank black screen after the key handshake. I watched thru the serial port and the sys log showed all of the same entries for my broken web ssh session in firefox as it did for the working chrome web ssh session which means it has to be a problem with firefox.







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Jan 4 at 18:01









                                      Kevin NadingKevin Nading

                                      11




                                      11






























                                          draft saved

                                          draft discarded




















































                                          Thanks for contributing an answer to Stack Overflow!


                                          • Please be sure to answer the question. Provide details and share your research!

                                          But avoid



                                          • Asking for help, clarification, or responding to other answers.

                                          • Making statements based on opinion; back them up with references or personal experience.


                                          To learn more, see our tips on writing great answers.




                                          draft saved


                                          draft discarded














                                          StackExchange.ready(
                                          function () {
                                          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997002%2fssh-browser-doesnt-work-in-compute-engine-gcp%23new-answer', 'question_page');
                                          }
                                          );

                                          Post as a guest















                                          Required, but never shown





















































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown

































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown







                                          Popular posts from this blog

                                          MongoDB - Not Authorized To Execute Command

                                          in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

                                          Npm cannot find a required file even through it is in the searched directory