Enabling SSH on boot via config files

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








up vote
1
down vote

favorite












How can I configure ssh service to run on boot other than via shell? Is it through /etc/init/ssh.conf ? If that's the case, what parametters should I look for in it?
The reason I can't do this through terminal is that I've lost SSH acces to the server. The hosting company enables a network recovery mode ssh acces, which in turn allows me to mount the partitions and access my server files. Their privacy policies do not allow them to acces the server file system or services. All they could was a server reboot which didn't solve the issue.



note. OpenSSH is installed. Other services Apache/MySQL/php/proPTFd are running smoothly.







share|improve this question




















  • paste the ssh -vvv user@your-server-ip using paste.ubuntu.com and if you can manually create a symbolic link of /usr/lib/systemd/system/sshd.service to /etc/systemd/system/multi-user.target.wants/sshd.service that might start the ssh service at boot.
    – Pavel Sayekat
    May 1 at 18:15















up vote
1
down vote

favorite












How can I configure ssh service to run on boot other than via shell? Is it through /etc/init/ssh.conf ? If that's the case, what parametters should I look for in it?
The reason I can't do this through terminal is that I've lost SSH acces to the server. The hosting company enables a network recovery mode ssh acces, which in turn allows me to mount the partitions and access my server files. Their privacy policies do not allow them to acces the server file system or services. All they could was a server reboot which didn't solve the issue.



note. OpenSSH is installed. Other services Apache/MySQL/php/proPTFd are running smoothly.







share|improve this question




















  • paste the ssh -vvv user@your-server-ip using paste.ubuntu.com and if you can manually create a symbolic link of /usr/lib/systemd/system/sshd.service to /etc/systemd/system/multi-user.target.wants/sshd.service that might start the ssh service at boot.
    – Pavel Sayekat
    May 1 at 18:15













up vote
1
down vote

favorite









up vote
1
down vote

favorite











How can I configure ssh service to run on boot other than via shell? Is it through /etc/init/ssh.conf ? If that's the case, what parametters should I look for in it?
The reason I can't do this through terminal is that I've lost SSH acces to the server. The hosting company enables a network recovery mode ssh acces, which in turn allows me to mount the partitions and access my server files. Their privacy policies do not allow them to acces the server file system or services. All they could was a server reboot which didn't solve the issue.



note. OpenSSH is installed. Other services Apache/MySQL/php/proPTFd are running smoothly.







share|improve this question












How can I configure ssh service to run on boot other than via shell? Is it through /etc/init/ssh.conf ? If that's the case, what parametters should I look for in it?
The reason I can't do this through terminal is that I've lost SSH acces to the server. The hosting company enables a network recovery mode ssh acces, which in turn allows me to mount the partitions and access my server files. Their privacy policies do not allow them to acces the server file system or services. All they could was a server reboot which didn't solve the issue.



note. OpenSSH is installed. Other services Apache/MySQL/php/proPTFd are running smoothly.









share|improve this question











share|improve this question




share|improve this question










asked Apr 30 at 9:46









InspectorG34

63




63











  • paste the ssh -vvv user@your-server-ip using paste.ubuntu.com and if you can manually create a symbolic link of /usr/lib/systemd/system/sshd.service to /etc/systemd/system/multi-user.target.wants/sshd.service that might start the ssh service at boot.
    – Pavel Sayekat
    May 1 at 18:15

















  • paste the ssh -vvv user@your-server-ip using paste.ubuntu.com and if you can manually create a symbolic link of /usr/lib/systemd/system/sshd.service to /etc/systemd/system/multi-user.target.wants/sshd.service that might start the ssh service at boot.
    – Pavel Sayekat
    May 1 at 18:15
















paste the ssh -vvv user@your-server-ip using paste.ubuntu.com and if you can manually create a symbolic link of /usr/lib/systemd/system/sshd.service to /etc/systemd/system/multi-user.target.wants/sshd.service that might start the ssh service at boot.
– Pavel Sayekat
May 1 at 18:15





paste the ssh -vvv user@your-server-ip using paste.ubuntu.com and if you can manually create a symbolic link of /usr/lib/systemd/system/sshd.service to /etc/systemd/system/multi-user.target.wants/sshd.service that might start the ssh service at boot.
– Pavel Sayekat
May 1 at 18:15











1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










I managed to regain ssh access again. For some reason the ufw rule for port 22 was lost. It should have been the first place to look, but it was an error on my part to not question if ssh service was up. I made a bad assumption that it was down. Lesson learned.



If a beginner with the same issue stumbles on this, if you use ufw check your /lib/ufw/user.rules and /lib/ufw/user6.rules to see if a rule for OpenSSH exists. In my case adding the below solved it:



### tuple ### allow any 22 0.0.0.0/0 any 0.0.0.0/0 in
-A ufw-user-input -p tcp --dport 22 -j ACCEPT
-A ufw-user-input -p udp --dport 22 -j ACCEPT





share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    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: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f1030047%2fenabling-ssh-on-boot-via-config-files%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote



    accepted










    I managed to regain ssh access again. For some reason the ufw rule for port 22 was lost. It should have been the first place to look, but it was an error on my part to not question if ssh service was up. I made a bad assumption that it was down. Lesson learned.



    If a beginner with the same issue stumbles on this, if you use ufw check your /lib/ufw/user.rules and /lib/ufw/user6.rules to see if a rule for OpenSSH exists. In my case adding the below solved it:



    ### tuple ### allow any 22 0.0.0.0/0 any 0.0.0.0/0 in
    -A ufw-user-input -p tcp --dport 22 -j ACCEPT
    -A ufw-user-input -p udp --dport 22 -j ACCEPT





    share|improve this answer
























      up vote
      0
      down vote



      accepted










      I managed to regain ssh access again. For some reason the ufw rule for port 22 was lost. It should have been the first place to look, but it was an error on my part to not question if ssh service was up. I made a bad assumption that it was down. Lesson learned.



      If a beginner with the same issue stumbles on this, if you use ufw check your /lib/ufw/user.rules and /lib/ufw/user6.rules to see if a rule for OpenSSH exists. In my case adding the below solved it:



      ### tuple ### allow any 22 0.0.0.0/0 any 0.0.0.0/0 in
      -A ufw-user-input -p tcp --dport 22 -j ACCEPT
      -A ufw-user-input -p udp --dport 22 -j ACCEPT





      share|improve this answer






















        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        I managed to regain ssh access again. For some reason the ufw rule for port 22 was lost. It should have been the first place to look, but it was an error on my part to not question if ssh service was up. I made a bad assumption that it was down. Lesson learned.



        If a beginner with the same issue stumbles on this, if you use ufw check your /lib/ufw/user.rules and /lib/ufw/user6.rules to see if a rule for OpenSSH exists. In my case adding the below solved it:



        ### tuple ### allow any 22 0.0.0.0/0 any 0.0.0.0/0 in
        -A ufw-user-input -p tcp --dport 22 -j ACCEPT
        -A ufw-user-input -p udp --dport 22 -j ACCEPT





        share|improve this answer












        I managed to regain ssh access again. For some reason the ufw rule for port 22 was lost. It should have been the first place to look, but it was an error on my part to not question if ssh service was up. I made a bad assumption that it was down. Lesson learned.



        If a beginner with the same issue stumbles on this, if you use ufw check your /lib/ufw/user.rules and /lib/ufw/user6.rules to see if a rule for OpenSSH exists. In my case adding the below solved it:



        ### tuple ### allow any 22 0.0.0.0/0 any 0.0.0.0/0 in
        -A ufw-user-input -p tcp --dport 22 -j ACCEPT
        -A ufw-user-input -p udp --dport 22 -j ACCEPT






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 2 at 11:26









        InspectorG34

        63




        63



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1030047%2fenabling-ssh-on-boot-via-config-files%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491