Thanks Kevin -- do you know how to test that? On the sever, netstat - a starts
Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:8000 *:* LISTEN tcp 0 0 *:58244 *:* LISTEN tcp 0 0 *:sunrpc *:* LISTEN tcp 0 0 *:www *:* LISTEN tcp 0 0 *:ssh *:* LISTEN tcp 0 0 localhost:6010 *:* LISTEN tcp 0 0 localhost:6011 *:* LISTEN tcp 0 0 localhost:6012 *:* LISTEN which includes a listen on 8000 (and the sage server is running), but what does that prove? John On 16 Aug, 21:22, Kevin Horton <khorto...@rogers.com> wrote: > John Cremona wrote: > > Thanks for the replies. > > > It's on the big wide internet, not local. > > > On 16 Aug, 19:27, William Stein <wst...@gmail.com> wrote: > > >> On Sun, Aug 16, 2009 at 6:49 AM, John Cremona<john.crem...@gmail.com> > >> wrote: > > >>> In the docstring for notebook() it says " More documentation is available > >>> in the > >>> Sage installation guide, in the "Running the Sage Notebook Securely" > >>> chapter" but there is not such chapter. Has this documentation > >>> moved? There is also a link to a wiki page, but that page has almost > >>> no information on it. > > >>> For the first time in my life I tried running sage on one machine and > >>> connecting from another, and I cannot get it to work. > > >> What exactly did you do that didn't work? > > >> Do > > >> sage: notebook(address="", secure=True, open_viewer=False) > > >> and then go tohttps://address.of.the.machine.you.did.that.on:8000 > >> on the other machine. > > > That is what I did. firefox just waits, displaying "loading..." until > > it times out. > > > Note that the output from that notebook command says "Open your web > > browser tohttps://localhost:8000"; which is definitely not right since > > I am trying to connect from somewhere else entirely. So the address I > > go to is in facthttps://137.205.37.242:8000 > > > That machine is reachable, as you'll see if you try going to > >http://137.205.37.242(that's http not https). > > Could there possibly be a firewall or port forwarding issue? The > default ports for http and https are 80 and 443 respectively, so an > ability to connect with http does not guarantee that https will work. > -- > Kevin Horton --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
