SSH connection refused. Error 61

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












0















So, I set up another FreeBSD server. Everything was ok until I tried to connect to it via my old FreeBSD.



On connection it echoes:



Unable to connect to relay host, errno=61
ssh_exchange_identification: Connection closed by remote host


But I just used Putty to connect to it and it works. On top of it, I had connected to my old via SSH with no problem. It still can't connect to new one.



TL;DR:

SSH
1)Win->Old = ok
2)Win->New = ok
3)New->Old = ok
4)Old->New = no_go


What am I doing wrong?










share|improve this question
























  • What messages do you get in the security log from the ssh server on the new host?

    – roaima
    Jun 26 '15 at 9:39






  • 1





    Maybe the new ssh server request stronger encryption (or newer protocol) than the old client can do. Run ssh with -vvv flag to see more information about the internals. Do you have configured some unreachable ssh proxy/relay host on the old freebsd system (the error message seems to confirm this)?

    – jofel
    Jun 26 '15 at 9:40












  • @jofel that's where I was heading, too.

    – roaima
    Jun 26 '15 at 9:43






  • 1





    Please edit your original question and add the output of the ssh command to it, so it can be formatted properly.

    – dr01
    Jun 26 '15 at 10:22






  • 1





    The problem is probably not ssh but the to me unknown proxy-connect program. Does the SOCKS proxy work from the old bsd machine if you are using it for other connections (web browsing etc.)? Can you ping 192.168.0.1 from the old machine? Do you need the proxy or is a direct connection possible (seems to be same subnet)?

    – jofel
    Jun 26 '15 at 10:26















0















So, I set up another FreeBSD server. Everything was ok until I tried to connect to it via my old FreeBSD.



On connection it echoes:



Unable to connect to relay host, errno=61
ssh_exchange_identification: Connection closed by remote host


But I just used Putty to connect to it and it works. On top of it, I had connected to my old via SSH with no problem. It still can't connect to new one.



TL;DR:

SSH
1)Win->Old = ok
2)Win->New = ok
3)New->Old = ok
4)Old->New = no_go


What am I doing wrong?










share|improve this question
























  • What messages do you get in the security log from the ssh server on the new host?

    – roaima
    Jun 26 '15 at 9:39






  • 1





    Maybe the new ssh server request stronger encryption (or newer protocol) than the old client can do. Run ssh with -vvv flag to see more information about the internals. Do you have configured some unreachable ssh proxy/relay host on the old freebsd system (the error message seems to confirm this)?

    – jofel
    Jun 26 '15 at 9:40












  • @jofel that's where I was heading, too.

    – roaima
    Jun 26 '15 at 9:43






  • 1





    Please edit your original question and add the output of the ssh command to it, so it can be formatted properly.

    – dr01
    Jun 26 '15 at 10:22






  • 1





    The problem is probably not ssh but the to me unknown proxy-connect program. Does the SOCKS proxy work from the old bsd machine if you are using it for other connections (web browsing etc.)? Can you ping 192.168.0.1 from the old machine? Do you need the proxy or is a direct connection possible (seems to be same subnet)?

    – jofel
    Jun 26 '15 at 10:26













0












0








0








So, I set up another FreeBSD server. Everything was ok until I tried to connect to it via my old FreeBSD.



On connection it echoes:



Unable to connect to relay host, errno=61
ssh_exchange_identification: Connection closed by remote host


But I just used Putty to connect to it and it works. On top of it, I had connected to my old via SSH with no problem. It still can't connect to new one.



TL;DR:

SSH
1)Win->Old = ok
2)Win->New = ok
3)New->Old = ok
4)Old->New = no_go


What am I doing wrong?










share|improve this question
















So, I set up another FreeBSD server. Everything was ok until I tried to connect to it via my old FreeBSD.



On connection it echoes:



Unable to connect to relay host, errno=61
ssh_exchange_identification: Connection closed by remote host


But I just used Putty to connect to it and it works. On top of it, I had connected to my old via SSH with no problem. It still can't connect to new one.



TL;DR:

SSH
1)Win->Old = ok
2)Win->New = ok
3)New->Old = ok
4)Old->New = no_go


What am I doing wrong?







ssh freebsd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 26 '15 at 10:20









Kevdog777

2,102123259




2,102123259










asked Jun 26 '15 at 9:34









h0l3h0l3

11




11












  • What messages do you get in the security log from the ssh server on the new host?

    – roaima
    Jun 26 '15 at 9:39






  • 1





    Maybe the new ssh server request stronger encryption (or newer protocol) than the old client can do. Run ssh with -vvv flag to see more information about the internals. Do you have configured some unreachable ssh proxy/relay host on the old freebsd system (the error message seems to confirm this)?

    – jofel
    Jun 26 '15 at 9:40












  • @jofel that's where I was heading, too.

    – roaima
    Jun 26 '15 at 9:43






  • 1





    Please edit your original question and add the output of the ssh command to it, so it can be formatted properly.

    – dr01
    Jun 26 '15 at 10:22






  • 1





    The problem is probably not ssh but the to me unknown proxy-connect program. Does the SOCKS proxy work from the old bsd machine if you are using it for other connections (web browsing etc.)? Can you ping 192.168.0.1 from the old machine? Do you need the proxy or is a direct connection possible (seems to be same subnet)?

    – jofel
    Jun 26 '15 at 10:26

















  • What messages do you get in the security log from the ssh server on the new host?

    – roaima
    Jun 26 '15 at 9:39






  • 1





    Maybe the new ssh server request stronger encryption (or newer protocol) than the old client can do. Run ssh with -vvv flag to see more information about the internals. Do you have configured some unreachable ssh proxy/relay host on the old freebsd system (the error message seems to confirm this)?

    – jofel
    Jun 26 '15 at 9:40












  • @jofel that's where I was heading, too.

    – roaima
    Jun 26 '15 at 9:43






  • 1





    Please edit your original question and add the output of the ssh command to it, so it can be formatted properly.

    – dr01
    Jun 26 '15 at 10:22






  • 1





    The problem is probably not ssh but the to me unknown proxy-connect program. Does the SOCKS proxy work from the old bsd machine if you are using it for other connections (web browsing etc.)? Can you ping 192.168.0.1 from the old machine? Do you need the proxy or is a direct connection possible (seems to be same subnet)?

    – jofel
    Jun 26 '15 at 10:26
















What messages do you get in the security log from the ssh server on the new host?

– roaima
Jun 26 '15 at 9:39





What messages do you get in the security log from the ssh server on the new host?

– roaima
Jun 26 '15 at 9:39




1




1





Maybe the new ssh server request stronger encryption (or newer protocol) than the old client can do. Run ssh with -vvv flag to see more information about the internals. Do you have configured some unreachable ssh proxy/relay host on the old freebsd system (the error message seems to confirm this)?

– jofel
Jun 26 '15 at 9:40






Maybe the new ssh server request stronger encryption (or newer protocol) than the old client can do. Run ssh with -vvv flag to see more information about the internals. Do you have configured some unreachable ssh proxy/relay host on the old freebsd system (the error message seems to confirm this)?

– jofel
Jun 26 '15 at 9:40














@jofel that's where I was heading, too.

– roaima
Jun 26 '15 at 9:43





@jofel that's where I was heading, too.

– roaima
Jun 26 '15 at 9:43




1




1





Please edit your original question and add the output of the ssh command to it, so it can be formatted properly.

– dr01
Jun 26 '15 at 10:22





Please edit your original question and add the output of the ssh command to it, so it can be formatted properly.

– dr01
Jun 26 '15 at 10:22




1




1





The problem is probably not ssh but the to me unknown proxy-connect program. Does the SOCKS proxy work from the old bsd machine if you are using it for other connections (web browsing etc.)? Can you ping 192.168.0.1 from the old machine? Do you need the proxy or is a direct connection possible (seems to be same subnet)?

– jofel
Jun 26 '15 at 10:26





The problem is probably not ssh but the to me unknown proxy-connect program. Does the SOCKS proxy work from the old bsd machine if you are using it for other connections (web browsing etc.)? Can you ping 192.168.0.1 from the old machine? Do you need the proxy or is a direct connection possible (seems to be same subnet)?

– jofel
Jun 26 '15 at 10:26










1 Answer
1






active

oldest

votes


















0














I think the problem is related to a not-found matching private key. The ssh client sequentially tries several keys (from .ssh/) which are denied by the server, until a limit is reached.
Try to specify a specific identity with



ssh -i .ssh/<correct key> ....





share|improve this answer






















    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f212368%2fssh-connection-refused-error-61%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I think the problem is related to a not-found matching private key. The ssh client sequentially tries several keys (from .ssh/) which are denied by the server, until a limit is reached.
    Try to specify a specific identity with



    ssh -i .ssh/<correct key> ....





    share|improve this answer



























      0














      I think the problem is related to a not-found matching private key. The ssh client sequentially tries several keys (from .ssh/) which are denied by the server, until a limit is reached.
      Try to specify a specific identity with



      ssh -i .ssh/<correct key> ....





      share|improve this answer

























        0












        0








        0







        I think the problem is related to a not-found matching private key. The ssh client sequentially tries several keys (from .ssh/) which are denied by the server, until a limit is reached.
        Try to specify a specific identity with



        ssh -i .ssh/<correct key> ....





        share|improve this answer













        I think the problem is related to a not-found matching private key. The ssh client sequentially tries several keys (from .ssh/) which are denied by the server, until a limit is reached.
        Try to specify a specific identity with



        ssh -i .ssh/<correct key> ....






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 26 '15 at 10:46









        gerhard d.gerhard d.

        1,136310




        1,136310



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f212368%2fssh-connection-refused-error-61%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

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

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay