Can't ssh to server as a regular user after Debian upgrade to Buster

Multi tool use
Multi tool use

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











up vote
0
down vote

favorite












I have just upgraded my Debian server from Stretch to Buster.



One strange thing I can't seem to resolve:



$ ssh vlastimil@192.168.0.102 -p [censored] -o ConnectTimeout=5 -i /home/vlastimil/.ssh/id_rsa -vvv


results in:



OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "192.168.0.102" port [censored]
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.0.102 [192.168.0.102] port [censored].
debug2: fd 3 setting O_NONBLOCK
debug1: connect to address 192.168.0.102 port [censored]: Connection refused




ssh: connect to host 192.168.0.102 port [censored]: Connection refused





However, if I log in as that user locally (I can even log off then, it just needs one login), it does work.



I am now heading to try to log in as root. Wait for it, I have only one machine, from which it is possible and I am currently at another one.









share

























    up vote
    0
    down vote

    favorite












    I have just upgraded my Debian server from Stretch to Buster.



    One strange thing I can't seem to resolve:



    $ ssh vlastimil@192.168.0.102 -p [censored] -o ConnectTimeout=5 -i /home/vlastimil/.ssh/id_rsa -vvv


    results in:



    OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: /etc/ssh/ssh_config line 19: Applying options for *
    debug2: resolving "192.168.0.102" port [censored]
    debug2: ssh_connect_direct: needpriv 0
    debug1: Connecting to 192.168.0.102 [192.168.0.102] port [censored].
    debug2: fd 3 setting O_NONBLOCK
    debug1: connect to address 192.168.0.102 port [censored]: Connection refused




    ssh: connect to host 192.168.0.102 port [censored]: Connection refused





    However, if I log in as that user locally (I can even log off then, it just needs one login), it does work.



    I am now heading to try to log in as root. Wait for it, I have only one machine, from which it is possible and I am currently at another one.









    share























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have just upgraded my Debian server from Stretch to Buster.



      One strange thing I can't seem to resolve:



      $ ssh vlastimil@192.168.0.102 -p [censored] -o ConnectTimeout=5 -i /home/vlastimil/.ssh/id_rsa -vvv


      results in:



      OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
      debug1: Reading configuration data /etc/ssh/ssh_config
      debug1: /etc/ssh/ssh_config line 19: Applying options for *
      debug2: resolving "192.168.0.102" port [censored]
      debug2: ssh_connect_direct: needpriv 0
      debug1: Connecting to 192.168.0.102 [192.168.0.102] port [censored].
      debug2: fd 3 setting O_NONBLOCK
      debug1: connect to address 192.168.0.102 port [censored]: Connection refused




      ssh: connect to host 192.168.0.102 port [censored]: Connection refused





      However, if I log in as that user locally (I can even log off then, it just needs one login), it does work.



      I am now heading to try to log in as root. Wait for it, I have only one machine, from which it is possible and I am currently at another one.









      share













      I have just upgraded my Debian server from Stretch to Buster.



      One strange thing I can't seem to resolve:



      $ ssh vlastimil@192.168.0.102 -p [censored] -o ConnectTimeout=5 -i /home/vlastimil/.ssh/id_rsa -vvv


      results in:



      OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
      debug1: Reading configuration data /etc/ssh/ssh_config
      debug1: /etc/ssh/ssh_config line 19: Applying options for *
      debug2: resolving "192.168.0.102" port [censored]
      debug2: ssh_connect_direct: needpriv 0
      debug1: Connecting to 192.168.0.102 [192.168.0.102] port [censored].
      debug2: fd 3 setting O_NONBLOCK
      debug1: connect to address 192.168.0.102 port [censored]: Connection refused




      ssh: connect to host 192.168.0.102 port [censored]: Connection refused





      However, if I log in as that user locally (I can even log off then, it just needs one login), it does work.



      I am now heading to try to log in as root. Wait for it, I have only one machine, from which it is possible and I am currently at another one.







      debian ssh





      share












      share










      share



      share










      asked 1 min ago









      Vlastimil

      7,0371152125




      7,0371152125

























          active

          oldest

          votes











          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%2f478353%2fcant-ssh-to-server-as-a-regular-user-after-debian-upgrade-to-buster%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478353%2fcant-ssh-to-server-as-a-regular-user-after-debian-upgrade-to-buster%23new-answer', 'question_page');

          );

          Post as a guest













































































          ATxt8OJFxHMXiEBtc,wJfzzTENOlmuk tYXr60X fqZ291iV4MQsHgXa,p0UzaFN,Ihar,YlxlyNxu
          C5w1ywPEog85,Mr3JoKrOkT1GKv4PgQ,KM3n nBvGpqFnrHNPzwH tdAlJEnFMfrl2X 8AEmK1H x3PTCDlylso9OEA

          Popular posts from this blog

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

          How many registers does an x86_64 CPU actually have?

          Displaying single band from multi-band raster using QGIS