Doesn't seem to work with remote IPython Notebook server?

[aldanor]

I wonder why doesn't it wanna work with a remote ipython notebook server? I have ipython notebook running on a remote unix machine and I'm forwarding port 7777 (and X11 stuff) through SSH. Works flawlessly in the browser -- just by connecting to 127.0.0.1:7777 from my local machine. However SublimeIPythonNotebook can't seem to be able to connect, any ideas why?

Cannot get a list of notebooks

[maximsch2]

I am using SSH port forwarding to connect to remote ipython server on port
8888 and it opens just fine in Sublime...
Do you see anything strange in the log when you are trying to connect?

Maxim Grechkin

On Thu, Sep 26, 2013 at 8:57 AM, Aldanor notifications@github.com wrote:

I wonder why doesn't it wanna work with a remote ipython notebook server?
I have ipython notebook running on a remote unix machine and I'm forwarding
port 7777 (and X11 stuff) through SSH. Works flawlessly in the browser --
just by connecting to 127.0.0.1:7777. However SublimeIPythonNotebook
can't seem to be able to connect, any ideas why?

Cannot get a list of notebooks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10
.

[aldanor]

I seem to be able to get JSON back in browser via http://127.0.0.1:7777/notebooks. However, I checked it out and apparently it's getting BadStatusLine('',) on this line:

req = urlopen("http://" + baseurl + "/notebooks")

[aldanor]

Looks like it's fixable, the problem is that your implementation doesn't handle proxies.

So, in get_notebooks() function, you can do something like

proxy = urllib2.ProxyHandler({})
opener = urllib2.build_opener(proxy)
req = opener.open('http://%s/notebooks/' % baseurl)

... which kinda seems to work :)

[aldanor]

On a side note, may I suggest saving the previous entered value of host/port instead of offering 127.0.0.1:888 as default every time? -- if someone uses a custom host/port (like I do), they would have to type it in manually every single time...

[maximsch2]

I've added the code to save previous host/port value and proxy handling code. But I am still not sure if using proxy will work now, because it looks like websocket-client doesn't support proxy...
Please try version 0.1.3 (should appear in Package Control shortly)

[caoimhinp]

Can't connect to a server using the following:

https://myurl.me:11111

https://192.168.0.7:11111

192.168.0.7:11111

I do have it password protected.
I am not getting any errors. It just silently fails.

[maximsch2]

Are you using proxy server? I don't think that would be expected to work
now, websocket library doesn't support proxy as far as I can tell

Maxim Grechkin

On Wed, Feb 12, 2014 at 6:31 PM, caoimhinp notifications@github.com wrote:

Can't connect to a server using the following:

https://myurl.me:11111

https://192.168.0.7:11111

192.168.0.7:11111

I do have it password protected.
I am not getting any errors. It just silently fails.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-34942600
.

[caoimhinp]

No. No proxy.
The myurl.me connection is port forwarded but the LAN ip is direct.

[maximsch2]

Can you try connecting to it without https?

Maxim Grechkin

On Wed, Feb 12, 2014 at 6:53 PM, caoimhinp notifications@github.com wrote:

No. No proxy.
The myurl.me connection is port forwarded but the LAN ip is direct.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-34943678
.

[caoimhinp]

No joy.
Tried:

myurl.me:11111
192.168.0.7:11111

[maximsch2]

What about those:
http://myurl.me:11111
http://192.168.0.7:11111

Will you server accept http connections or you have set it up to work over
https?

Maxim Grechkin

On Wed, Feb 12, 2014 at 6:58 PM, caoimhinp notifications@github.com wrote:

No joy.
Tried:

myurl.me:11111
192.168.0.7:11111

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-34943854
.

[caoimhinp]

No, it won't accept http. I have it password protected and configured for https.
However, I tried them just for completeness. No change.

[maximsch2]

OK, then of course there was no reason to try them. You can try to see if
it will work with just http.

I am not sure if the plugin is even expected to work with HTTPS. I've never
tested it with HTTPS and do not use it myself. As a workaround, to provide
secure access to remote ipython notebooks, I run them bound to localhost on
the server and then do port forwarding through SSH tunnel.

Patches to support HTTPS (if it is indeed HTTPS issue) will be of course
welcome.

Maxim Grechkin

On Wed, Feb 12, 2014 at 7:02 PM, caoimhinp notifications@github.com wrote:

No, it won't accept http. I have it password protected and configured for
https.
However, I tried them just for completeness. No change.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-34944066
.

[caoimhinp]

No worries. I just thought I'd post my issue to keep this issue alive.

I thought I'd try those strings simply because I don't know how you're handling them on the other side.

I noted that it supported passwords after seeing the z-m-k contrib acknowledgement. I assumed it supported https since using passwords in the clear is not such a useful function. ;)

... I just checked and it looks like you're forcing http in the url parsing. I'll see what I can do ...

[maximsch2]

Sounds great!

I think the main question will be the support for HTTPS in websocket-client
library (https://github.com/liris/websocket-client). It looks like they do
support SSL, so it might be relatively easy to add support for it in
SublimeIPythonNotebook

Maxim Grechkin

On Wed, Feb 12, 2014 at 7:17 PM, caoimhinp notifications@github.com wrote:

No worries. I just thought I'd post my issue to keep this issue alive.

I thought I'd try those strings simply because I don't know how you're
handling them on the other side.

I noted that it supported passwords after seeing the z-m-k contrib
acknowledgement. I assumed it supported https since using passwords in the
clear is not such a useful function. ;)

... I just checked and it looks like you're forcing http in the url
parsing. I'll see what I can do ...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-34944724
.