Connect jupyter python by tunneled connection (via ssh)












0















I have a problem with connecting to jupyter that I run on remote computer. I have configured jupyter with ssl as in the following doc:



https://jupyter-notebook.readthedocs.io/en/latest/public_server.html#hashed-pw



Then I run jupyter on remote machine with command: jupyter notebook as in tutorial.
When its running I make a tunnel in another terminal by running a command:



ssh -N -f -L 8889:127.0.0.1:8881 user_name@hostname.com


Of course the jupyter is running on port 8881. When I open the browser on my local computer and try to open page:



localhost:8889


I got an error that connection was reset, and in command line the ssh returns the following error:



channel 2: open failed: connect failed: Connection refused


Can anyone help me? I was looking for an answer for whole day and still can't fix it.










share|improve this question























  • The error message seems to suggest that Jupyter is not actually listening at the expected port. My advice is to try to look at some simpler aspects in order to make some progress. (1) execute netstat -atnvp to see which ports are open and what program is listening on them. Try that both on the local host and the server; do the results show what you expected? (2) instead of running Jupyter, maybe just try to echo or cat or nc (i.e. netcat).

    – Robert Dodier
    Nov 26 '18 at 5:34
















0















I have a problem with connecting to jupyter that I run on remote computer. I have configured jupyter with ssl as in the following doc:



https://jupyter-notebook.readthedocs.io/en/latest/public_server.html#hashed-pw



Then I run jupyter on remote machine with command: jupyter notebook as in tutorial.
When its running I make a tunnel in another terminal by running a command:



ssh -N -f -L 8889:127.0.0.1:8881 user_name@hostname.com


Of course the jupyter is running on port 8881. When I open the browser on my local computer and try to open page:



localhost:8889


I got an error that connection was reset, and in command line the ssh returns the following error:



channel 2: open failed: connect failed: Connection refused


Can anyone help me? I was looking for an answer for whole day and still can't fix it.










share|improve this question























  • The error message seems to suggest that Jupyter is not actually listening at the expected port. My advice is to try to look at some simpler aspects in order to make some progress. (1) execute netstat -atnvp to see which ports are open and what program is listening on them. Try that both on the local host and the server; do the results show what you expected? (2) instead of running Jupyter, maybe just try to echo or cat or nc (i.e. netcat).

    – Robert Dodier
    Nov 26 '18 at 5:34














0












0








0








I have a problem with connecting to jupyter that I run on remote computer. I have configured jupyter with ssl as in the following doc:



https://jupyter-notebook.readthedocs.io/en/latest/public_server.html#hashed-pw



Then I run jupyter on remote machine with command: jupyter notebook as in tutorial.
When its running I make a tunnel in another terminal by running a command:



ssh -N -f -L 8889:127.0.0.1:8881 user_name@hostname.com


Of course the jupyter is running on port 8881. When I open the browser on my local computer and try to open page:



localhost:8889


I got an error that connection was reset, and in command line the ssh returns the following error:



channel 2: open failed: connect failed: Connection refused


Can anyone help me? I was looking for an answer for whole day and still can't fix it.










share|improve this question














I have a problem with connecting to jupyter that I run on remote computer. I have configured jupyter with ssl as in the following doc:



https://jupyter-notebook.readthedocs.io/en/latest/public_server.html#hashed-pw



Then I run jupyter on remote machine with command: jupyter notebook as in tutorial.
When its running I make a tunnel in another terminal by running a command:



ssh -N -f -L 8889:127.0.0.1:8881 user_name@hostname.com


Of course the jupyter is running on port 8881. When I open the browser on my local computer and try to open page:



localhost:8889


I got an error that connection was reset, and in command line the ssh returns the following error:



channel 2: open failed: connect failed: Connection refused


Can anyone help me? I was looking for an answer for whole day and still can't fix it.







python jupyter-notebook jupyter






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 23 '18 at 13:56









Marek JustynaMarek Justyna

477




477













  • The error message seems to suggest that Jupyter is not actually listening at the expected port. My advice is to try to look at some simpler aspects in order to make some progress. (1) execute netstat -atnvp to see which ports are open and what program is listening on them. Try that both on the local host and the server; do the results show what you expected? (2) instead of running Jupyter, maybe just try to echo or cat or nc (i.e. netcat).

    – Robert Dodier
    Nov 26 '18 at 5:34



















  • The error message seems to suggest that Jupyter is not actually listening at the expected port. My advice is to try to look at some simpler aspects in order to make some progress. (1) execute netstat -atnvp to see which ports are open and what program is listening on them. Try that both on the local host and the server; do the results show what you expected? (2) instead of running Jupyter, maybe just try to echo or cat or nc (i.e. netcat).

    – Robert Dodier
    Nov 26 '18 at 5:34

















The error message seems to suggest that Jupyter is not actually listening at the expected port. My advice is to try to look at some simpler aspects in order to make some progress. (1) execute netstat -atnvp to see which ports are open and what program is listening on them. Try that both on the local host and the server; do the results show what you expected? (2) instead of running Jupyter, maybe just try to echo or cat or nc (i.e. netcat).

– Robert Dodier
Nov 26 '18 at 5:34





The error message seems to suggest that Jupyter is not actually listening at the expected port. My advice is to try to look at some simpler aspects in order to make some progress. (1) execute netstat -atnvp to see which ports are open and what program is listening on them. Try that both on the local host and the server; do the results show what you expected? (2) instead of running Jupyter, maybe just try to echo or cat or nc (i.e. netcat).

– Robert Dodier
Nov 26 '18 at 5:34












1 Answer
1






active

oldest

votes


















0














The problem is, that in my case jupyter is running on localhost. At my server remote server I have no access to remote localhost, so the solution was quite easy - I run jupyter on specified ip = 0.0.0.0



jupyter notebook --no-browser --port=8881 --ip=0.0.0.0





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%2f53448039%2fconnect-jupyter-python-by-tunneled-connection-via-ssh%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














    The problem is, that in my case jupyter is running on localhost. At my server remote server I have no access to remote localhost, so the solution was quite easy - I run jupyter on specified ip = 0.0.0.0



    jupyter notebook --no-browser --port=8881 --ip=0.0.0.0





    share|improve this answer




























      0














      The problem is, that in my case jupyter is running on localhost. At my server remote server I have no access to remote localhost, so the solution was quite easy - I run jupyter on specified ip = 0.0.0.0



      jupyter notebook --no-browser --port=8881 --ip=0.0.0.0





      share|improve this answer


























        0












        0








        0







        The problem is, that in my case jupyter is running on localhost. At my server remote server I have no access to remote localhost, so the solution was quite easy - I run jupyter on specified ip = 0.0.0.0



        jupyter notebook --no-browser --port=8881 --ip=0.0.0.0





        share|improve this answer













        The problem is, that in my case jupyter is running on localhost. At my server remote server I have no access to remote localhost, so the solution was quite easy - I run jupyter on specified ip = 0.0.0.0



        jupyter notebook --no-browser --port=8881 --ip=0.0.0.0






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 '18 at 7:44









        Marek JustynaMarek Justyna

        477




        477






























            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%2f53448039%2fconnect-jupyter-python-by-tunneled-connection-via-ssh%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

            Berounka

            Sphinx de Gizeh

            Different font size/position of beamer's navigation symbols template's content depending on regular/plain...