Unable to SSH into Google Cloud Server after Reboot

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
4
down vote

favorite
1












I was learning to configure a Debian server and familiarising myself with the common command lines.



However, after executing the reboot command in SSH, my subsequent SSH connections were refused and I have total no access to the server.



I was able to ping the server. I attempted to reboot through the Google cloud interface too, however I was still unable to connect successfully.



Having this as a cloud server, I do not have any physical access to the server. The solution that I seem to see are to reconfigure the SSH settings which I can't without logging in.



What are the possible alternatives I have now or recreating a new instance is the only solution?










share|improve this question























  • be prepared for the fact that you might have to redo your server from scratch....baring any help that the google cloud server people may be able to provide you.
    – mdpc
    May 9 '14 at 1:08










  • @mdpc thanks for your reply. i am pretty much ready to redo the server. but my main concern is how can i avoid such problems in the future although reboot doesn't occur often but may be still required at times.
    – toffee.beanns
    May 9 '14 at 1:23










  • It's a bug. It also happened to me. You have append JSON to the key.
    – Thufir
    Jul 28 '16 at 11:12










  • Did the IP address of the server remain the same?
    – multithr3at3d
    Dec 31 '17 at 20:15














up vote
4
down vote

favorite
1












I was learning to configure a Debian server and familiarising myself with the common command lines.



However, after executing the reboot command in SSH, my subsequent SSH connections were refused and I have total no access to the server.



I was able to ping the server. I attempted to reboot through the Google cloud interface too, however I was still unable to connect successfully.



Having this as a cloud server, I do not have any physical access to the server. The solution that I seem to see are to reconfigure the SSH settings which I can't without logging in.



What are the possible alternatives I have now or recreating a new instance is the only solution?










share|improve this question























  • be prepared for the fact that you might have to redo your server from scratch....baring any help that the google cloud server people may be able to provide you.
    – mdpc
    May 9 '14 at 1:08










  • @mdpc thanks for your reply. i am pretty much ready to redo the server. but my main concern is how can i avoid such problems in the future although reboot doesn't occur often but may be still required at times.
    – toffee.beanns
    May 9 '14 at 1:23










  • It's a bug. It also happened to me. You have append JSON to the key.
    – Thufir
    Jul 28 '16 at 11:12










  • Did the IP address of the server remain the same?
    – multithr3at3d
    Dec 31 '17 at 20:15












up vote
4
down vote

favorite
1









up vote
4
down vote

favorite
1






1





I was learning to configure a Debian server and familiarising myself with the common command lines.



However, after executing the reboot command in SSH, my subsequent SSH connections were refused and I have total no access to the server.



I was able to ping the server. I attempted to reboot through the Google cloud interface too, however I was still unable to connect successfully.



Having this as a cloud server, I do not have any physical access to the server. The solution that I seem to see are to reconfigure the SSH settings which I can't without logging in.



What are the possible alternatives I have now or recreating a new instance is the only solution?










share|improve this question















I was learning to configure a Debian server and familiarising myself with the common command lines.



However, after executing the reboot command in SSH, my subsequent SSH connections were refused and I have total no access to the server.



I was able to ping the server. I attempted to reboot through the Google cloud interface too, however I was still unable to connect successfully.



Having this as a cloud server, I do not have any physical access to the server. The solution that I seem to see are to reconfigure the SSH settings which I can't without logging in.



What are the possible alternatives I have now or recreating a new instance is the only solution?







debian ssh reboot google-cloud






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 14 '17 at 0:45









Tomasz

8,56552760




8,56552760










asked May 8 '14 at 22:58









toffee.beanns

381147




381147











  • be prepared for the fact that you might have to redo your server from scratch....baring any help that the google cloud server people may be able to provide you.
    – mdpc
    May 9 '14 at 1:08










  • @mdpc thanks for your reply. i am pretty much ready to redo the server. but my main concern is how can i avoid such problems in the future although reboot doesn't occur often but may be still required at times.
    – toffee.beanns
    May 9 '14 at 1:23










  • It's a bug. It also happened to me. You have append JSON to the key.
    – Thufir
    Jul 28 '16 at 11:12










  • Did the IP address of the server remain the same?
    – multithr3at3d
    Dec 31 '17 at 20:15
















  • be prepared for the fact that you might have to redo your server from scratch....baring any help that the google cloud server people may be able to provide you.
    – mdpc
    May 9 '14 at 1:08










  • @mdpc thanks for your reply. i am pretty much ready to redo the server. but my main concern is how can i avoid such problems in the future although reboot doesn't occur often but may be still required at times.
    – toffee.beanns
    May 9 '14 at 1:23










  • It's a bug. It also happened to me. You have append JSON to the key.
    – Thufir
    Jul 28 '16 at 11:12










  • Did the IP address of the server remain the same?
    – multithr3at3d
    Dec 31 '17 at 20:15















be prepared for the fact that you might have to redo your server from scratch....baring any help that the google cloud server people may be able to provide you.
– mdpc
May 9 '14 at 1:08




be prepared for the fact that you might have to redo your server from scratch....baring any help that the google cloud server people may be able to provide you.
– mdpc
May 9 '14 at 1:08












@mdpc thanks for your reply. i am pretty much ready to redo the server. but my main concern is how can i avoid such problems in the future although reboot doesn't occur often but may be still required at times.
– toffee.beanns
May 9 '14 at 1:23




@mdpc thanks for your reply. i am pretty much ready to redo the server. but my main concern is how can i avoid such problems in the future although reboot doesn't occur often but may be still required at times.
– toffee.beanns
May 9 '14 at 1:23












It's a bug. It also happened to me. You have append JSON to the key.
– Thufir
Jul 28 '16 at 11:12




It's a bug. It also happened to me. You have append JSON to the key.
– Thufir
Jul 28 '16 at 11:12












Did the IP address of the server remain the same?
– multithr3at3d
Dec 31 '17 at 20:15




Did the IP address of the server remain the same?
– multithr3at3d
Dec 31 '17 at 20:15










3 Answers
3






active

oldest

votes

















up vote
1
down vote













Your best bet is to create the key manually with the gcloud console:



thufir@mordor:~$ 
thufir@mordor:~$ gcloud compute config-ssh
WARNING: The private SSH key file for Google Compute Engine does not exist.
WARNING: You do not have an SSH key for Google Compute Engine.
WARNING: [/usr/bin/ssh-keygen] will be executed to generate a key.
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/thufir/.ssh/google_compute_engine.
Your public key has been saved in /home/thufir/.ssh/google_compute_engine.pub.
The key fingerprint is:
SHA256:ioreurewiopruweoiprwe thufir@mordor
The key's randomart image is:
+---[RSA 2048]----+
.......
| |
| |
+----[SHA256]-----+

Updated [https://www.googleapis.com/compute/v1/projects/<project>].
You should now be able to use ssh/scp with your instances.
For example, try running:

$ ssh <instance>.<location>.<project>

thufir@mordor:~$
thufir@mordor:~$ ssh <instance>.<location>.<project>
The authenticity of host 'compute.<####> (<ip address>)' can't be established.
ECDSA key fingerprint is SHA256:<fingerprint?>.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'compute.<####>' (ECDSA) to the list of known hosts.
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-31-generic x86_64)

* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage

Get cloud support with Ubuntu Advantage Cloud Guest:
http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.



The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

$
$
$ whoami
thufir
$ pwd
/home/thufir
$ exit
Connection to <ip address> closed.
thufir@mordor:~$


source:



https://askubuntu.com/questions/803908/



see also:



How do I append a SSH key with JSON for Google cloud compute VPS?






share|improve this answer





























    up vote
    0
    down vote













    I think Google gives a quite a comprehensive list of solutions for troubleshooting SSH errors, please refer here.



    IMO, you may have incorrectly set up SSH keys, or there are misconfigured iptables.






    share|improve this answer




















    • hey delta24, thanks for your answer. I am still testing out the server, but seems like i got stucked at one part of the solution list you provided. I ran the command to add the ssh rule to the firewall and tried to do a netcat test to see the banner. However, nothing came out. There was no further instructions to which I could try out. Could you help me out? Appreciated!
      – toffee.beanns
      May 9 '14 at 13:48










    • google seems to do very strange things with SSH keys and JSON.
      – Thufir
      Jul 28 '16 at 11:19

















    up vote
    0
    down vote













    Good night, this has just happened cmg tbm, I think you should have already fixed or reconfigured your vps, but for those who face this problem, I was able to connect through port 443, after that, run nano command / etc / ssh / sshd_config and uncomment the line that has #Port 22, only take the #





    share








    New contributor




    Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

















      Your Answer







      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      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',
      convertImagesToLinks: false,
      noModals: false,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













       

      draft saved


      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f128556%2funable-to-ssh-into-google-cloud-server-after-reboot%23new-answer', 'question_page');

      );

      Post as a guest






























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      1
      down vote













      Your best bet is to create the key manually with the gcloud console:



      thufir@mordor:~$ 
      thufir@mordor:~$ gcloud compute config-ssh
      WARNING: The private SSH key file for Google Compute Engine does not exist.
      WARNING: You do not have an SSH key for Google Compute Engine.
      WARNING: [/usr/bin/ssh-keygen] will be executed to generate a key.
      Generating public/private rsa key pair.
      Enter passphrase (empty for no passphrase):
      Enter same passphrase again:
      Your identification has been saved in /home/thufir/.ssh/google_compute_engine.
      Your public key has been saved in /home/thufir/.ssh/google_compute_engine.pub.
      The key fingerprint is:
      SHA256:ioreurewiopruweoiprwe thufir@mordor
      The key's randomart image is:
      +---[RSA 2048]----+
      .......
      | |
      | |
      +----[SHA256]-----+

      Updated [https://www.googleapis.com/compute/v1/projects/<project>].
      You should now be able to use ssh/scp with your instances.
      For example, try running:

      $ ssh <instance>.<location>.<project>

      thufir@mordor:~$
      thufir@mordor:~$ ssh <instance>.<location>.<project>
      The authenticity of host 'compute.<####> (<ip address>)' can't be established.
      ECDSA key fingerprint is SHA256:<fingerprint?>.
      Are you sure you want to continue connecting (yes/no)? yes
      Warning: Permanently added 'compute.<####>' (ECDSA) to the list of known hosts.
      Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-31-generic x86_64)

      * Documentation: https://help.ubuntu.com
      * Management: https://landscape.canonical.com
      * Support: https://ubuntu.com/advantage

      Get cloud support with Ubuntu Advantage Cloud Guest:
      http://www.ubuntu.com/business/services/cloud

      0 packages can be updated.
      0 updates are security updates.



      The programs included with the Ubuntu system are free software;
      the exact distribution terms for each program are described in the
      individual files in /usr/share/doc/*/copyright.

      Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
      applicable law.

      $
      $
      $ whoami
      thufir
      $ pwd
      /home/thufir
      $ exit
      Connection to <ip address> closed.
      thufir@mordor:~$


      source:



      https://askubuntu.com/questions/803908/



      see also:



      How do I append a SSH key with JSON for Google cloud compute VPS?






      share|improve this answer


























        up vote
        1
        down vote













        Your best bet is to create the key manually with the gcloud console:



        thufir@mordor:~$ 
        thufir@mordor:~$ gcloud compute config-ssh
        WARNING: The private SSH key file for Google Compute Engine does not exist.
        WARNING: You do not have an SSH key for Google Compute Engine.
        WARNING: [/usr/bin/ssh-keygen] will be executed to generate a key.
        Generating public/private rsa key pair.
        Enter passphrase (empty for no passphrase):
        Enter same passphrase again:
        Your identification has been saved in /home/thufir/.ssh/google_compute_engine.
        Your public key has been saved in /home/thufir/.ssh/google_compute_engine.pub.
        The key fingerprint is:
        SHA256:ioreurewiopruweoiprwe thufir@mordor
        The key's randomart image is:
        +---[RSA 2048]----+
        .......
        | |
        | |
        +----[SHA256]-----+

        Updated [https://www.googleapis.com/compute/v1/projects/<project>].
        You should now be able to use ssh/scp with your instances.
        For example, try running:

        $ ssh <instance>.<location>.<project>

        thufir@mordor:~$
        thufir@mordor:~$ ssh <instance>.<location>.<project>
        The authenticity of host 'compute.<####> (<ip address>)' can't be established.
        ECDSA key fingerprint is SHA256:<fingerprint?>.
        Are you sure you want to continue connecting (yes/no)? yes
        Warning: Permanently added 'compute.<####>' (ECDSA) to the list of known hosts.
        Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-31-generic x86_64)

        * Documentation: https://help.ubuntu.com
        * Management: https://landscape.canonical.com
        * Support: https://ubuntu.com/advantage

        Get cloud support with Ubuntu Advantage Cloud Guest:
        http://www.ubuntu.com/business/services/cloud

        0 packages can be updated.
        0 updates are security updates.



        The programs included with the Ubuntu system are free software;
        the exact distribution terms for each program are described in the
        individual files in /usr/share/doc/*/copyright.

        Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
        applicable law.

        $
        $
        $ whoami
        thufir
        $ pwd
        /home/thufir
        $ exit
        Connection to <ip address> closed.
        thufir@mordor:~$


        source:



        https://askubuntu.com/questions/803908/



        see also:



        How do I append a SSH key with JSON for Google cloud compute VPS?






        share|improve this answer
























          up vote
          1
          down vote










          up vote
          1
          down vote









          Your best bet is to create the key manually with the gcloud console:



          thufir@mordor:~$ 
          thufir@mordor:~$ gcloud compute config-ssh
          WARNING: The private SSH key file for Google Compute Engine does not exist.
          WARNING: You do not have an SSH key for Google Compute Engine.
          WARNING: [/usr/bin/ssh-keygen] will be executed to generate a key.
          Generating public/private rsa key pair.
          Enter passphrase (empty for no passphrase):
          Enter same passphrase again:
          Your identification has been saved in /home/thufir/.ssh/google_compute_engine.
          Your public key has been saved in /home/thufir/.ssh/google_compute_engine.pub.
          The key fingerprint is:
          SHA256:ioreurewiopruweoiprwe thufir@mordor
          The key's randomart image is:
          +---[RSA 2048]----+
          .......
          | |
          | |
          +----[SHA256]-----+

          Updated [https://www.googleapis.com/compute/v1/projects/<project>].
          You should now be able to use ssh/scp with your instances.
          For example, try running:

          $ ssh <instance>.<location>.<project>

          thufir@mordor:~$
          thufir@mordor:~$ ssh <instance>.<location>.<project>
          The authenticity of host 'compute.<####> (<ip address>)' can't be established.
          ECDSA key fingerprint is SHA256:<fingerprint?>.
          Are you sure you want to continue connecting (yes/no)? yes
          Warning: Permanently added 'compute.<####>' (ECDSA) to the list of known hosts.
          Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-31-generic x86_64)

          * Documentation: https://help.ubuntu.com
          * Management: https://landscape.canonical.com
          * Support: https://ubuntu.com/advantage

          Get cloud support with Ubuntu Advantage Cloud Guest:
          http://www.ubuntu.com/business/services/cloud

          0 packages can be updated.
          0 updates are security updates.



          The programs included with the Ubuntu system are free software;
          the exact distribution terms for each program are described in the
          individual files in /usr/share/doc/*/copyright.

          Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
          applicable law.

          $
          $
          $ whoami
          thufir
          $ pwd
          /home/thufir
          $ exit
          Connection to <ip address> closed.
          thufir@mordor:~$


          source:



          https://askubuntu.com/questions/803908/



          see also:



          How do I append a SSH key with JSON for Google cloud compute VPS?






          share|improve this answer














          Your best bet is to create the key manually with the gcloud console:



          thufir@mordor:~$ 
          thufir@mordor:~$ gcloud compute config-ssh
          WARNING: The private SSH key file for Google Compute Engine does not exist.
          WARNING: You do not have an SSH key for Google Compute Engine.
          WARNING: [/usr/bin/ssh-keygen] will be executed to generate a key.
          Generating public/private rsa key pair.
          Enter passphrase (empty for no passphrase):
          Enter same passphrase again:
          Your identification has been saved in /home/thufir/.ssh/google_compute_engine.
          Your public key has been saved in /home/thufir/.ssh/google_compute_engine.pub.
          The key fingerprint is:
          SHA256:ioreurewiopruweoiprwe thufir@mordor
          The key's randomart image is:
          +---[RSA 2048]----+
          .......
          | |
          | |
          +----[SHA256]-----+

          Updated [https://www.googleapis.com/compute/v1/projects/<project>].
          You should now be able to use ssh/scp with your instances.
          For example, try running:

          $ ssh <instance>.<location>.<project>

          thufir@mordor:~$
          thufir@mordor:~$ ssh <instance>.<location>.<project>
          The authenticity of host 'compute.<####> (<ip address>)' can't be established.
          ECDSA key fingerprint is SHA256:<fingerprint?>.
          Are you sure you want to continue connecting (yes/no)? yes
          Warning: Permanently added 'compute.<####>' (ECDSA) to the list of known hosts.
          Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-31-generic x86_64)

          * Documentation: https://help.ubuntu.com
          * Management: https://landscape.canonical.com
          * Support: https://ubuntu.com/advantage

          Get cloud support with Ubuntu Advantage Cloud Guest:
          http://www.ubuntu.com/business/services/cloud

          0 packages can be updated.
          0 updates are security updates.



          The programs included with the Ubuntu system are free software;
          the exact distribution terms for each program are described in the
          individual files in /usr/share/doc/*/copyright.

          Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
          applicable law.

          $
          $
          $ whoami
          thufir
          $ pwd
          /home/thufir
          $ exit
          Connection to <ip address> closed.
          thufir@mordor:~$


          source:



          https://askubuntu.com/questions/803908/



          see also:



          How do I append a SSH key with JSON for Google cloud compute VPS?







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 13 '17 at 12:36









          Community♦

          1




          1










          answered Jul 28 '16 at 11:14









          Thufir

          656834




          656834






















              up vote
              0
              down vote













              I think Google gives a quite a comprehensive list of solutions for troubleshooting SSH errors, please refer here.



              IMO, you may have incorrectly set up SSH keys, or there are misconfigured iptables.






              share|improve this answer




















              • hey delta24, thanks for your answer. I am still testing out the server, but seems like i got stucked at one part of the solution list you provided. I ran the command to add the ssh rule to the firewall and tried to do a netcat test to see the banner. However, nothing came out. There was no further instructions to which I could try out. Could you help me out? Appreciated!
                – toffee.beanns
                May 9 '14 at 13:48










              • google seems to do very strange things with SSH keys and JSON.
                – Thufir
                Jul 28 '16 at 11:19














              up vote
              0
              down vote













              I think Google gives a quite a comprehensive list of solutions for troubleshooting SSH errors, please refer here.



              IMO, you may have incorrectly set up SSH keys, or there are misconfigured iptables.






              share|improve this answer




















              • hey delta24, thanks for your answer. I am still testing out the server, but seems like i got stucked at one part of the solution list you provided. I ran the command to add the ssh rule to the firewall and tried to do a netcat test to see the banner. However, nothing came out. There was no further instructions to which I could try out. Could you help me out? Appreciated!
                – toffee.beanns
                May 9 '14 at 13:48










              • google seems to do very strange things with SSH keys and JSON.
                – Thufir
                Jul 28 '16 at 11:19












              up vote
              0
              down vote










              up vote
              0
              down vote









              I think Google gives a quite a comprehensive list of solutions for troubleshooting SSH errors, please refer here.



              IMO, you may have incorrectly set up SSH keys, or there are misconfigured iptables.






              share|improve this answer












              I think Google gives a quite a comprehensive list of solutions for troubleshooting SSH errors, please refer here.



              IMO, you may have incorrectly set up SSH keys, or there are misconfigured iptables.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered May 9 '14 at 3:26









              delta24

              784411




              784411











              • hey delta24, thanks for your answer. I am still testing out the server, but seems like i got stucked at one part of the solution list you provided. I ran the command to add the ssh rule to the firewall and tried to do a netcat test to see the banner. However, nothing came out. There was no further instructions to which I could try out. Could you help me out? Appreciated!
                – toffee.beanns
                May 9 '14 at 13:48










              • google seems to do very strange things with SSH keys and JSON.
                – Thufir
                Jul 28 '16 at 11:19
















              • hey delta24, thanks for your answer. I am still testing out the server, but seems like i got stucked at one part of the solution list you provided. I ran the command to add the ssh rule to the firewall and tried to do a netcat test to see the banner. However, nothing came out. There was no further instructions to which I could try out. Could you help me out? Appreciated!
                – toffee.beanns
                May 9 '14 at 13:48










              • google seems to do very strange things with SSH keys and JSON.
                – Thufir
                Jul 28 '16 at 11:19















              hey delta24, thanks for your answer. I am still testing out the server, but seems like i got stucked at one part of the solution list you provided. I ran the command to add the ssh rule to the firewall and tried to do a netcat test to see the banner. However, nothing came out. There was no further instructions to which I could try out. Could you help me out? Appreciated!
              – toffee.beanns
              May 9 '14 at 13:48




              hey delta24, thanks for your answer. I am still testing out the server, but seems like i got stucked at one part of the solution list you provided. I ran the command to add the ssh rule to the firewall and tried to do a netcat test to see the banner. However, nothing came out. There was no further instructions to which I could try out. Could you help me out? Appreciated!
              – toffee.beanns
              May 9 '14 at 13:48












              google seems to do very strange things with SSH keys and JSON.
              – Thufir
              Jul 28 '16 at 11:19




              google seems to do very strange things with SSH keys and JSON.
              – Thufir
              Jul 28 '16 at 11:19










              up vote
              0
              down vote













              Good night, this has just happened cmg tbm, I think you should have already fixed or reconfigured your vps, but for those who face this problem, I was able to connect through port 443, after that, run nano command / etc / ssh / sshd_config and uncomment the line that has #Port 22, only take the #





              share








              New contributor




              Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                up vote
                0
                down vote













                Good night, this has just happened cmg tbm, I think you should have already fixed or reconfigured your vps, but for those who face this problem, I was able to connect through port 443, after that, run nano command / etc / ssh / sshd_config and uncomment the line that has #Port 22, only take the #





                share








                New contributor




                Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.



















                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  Good night, this has just happened cmg tbm, I think you should have already fixed or reconfigured your vps, but for those who face this problem, I was able to connect through port 443, after that, run nano command / etc / ssh / sshd_config and uncomment the line that has #Port 22, only take the #





                  share








                  New contributor




                  Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  Good night, this has just happened cmg tbm, I think you should have already fixed or reconfigured your vps, but for those who face this problem, I was able to connect through port 443, after that, run nano command / etc / ssh / sshd_config and uncomment the line that has #Port 22, only take the #






                  share








                  New contributor




                  Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share


                  share






                  New contributor




                  Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 2 mins ago









                  Dhouel

                  1




                  1




                  New contributor




                  Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Dhouel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.



























                       

                      draft saved


                      draft discarded















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f128556%2funable-to-ssh-into-google-cloud-server-after-reboot%23new-answer', 'question_page');

                      );

                      Post as a guest













































































                      Popular posts from this blog

                      How to check contact read email or not when send email to Individual?

                      Bahrain

                      Postfix configuration issue with fips on centos 7; mailgun relay