-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error 403 on new notebook #754
Comments
If
returns nothing, which is what I expect, then you need to look at the kernel json files in If it does return an entry, and that entry isn't reflected in |
the relevant line in
moreover, the kernel file created in response to the
the chrome web interface seems to have no problems interacting with this kernel. |
That's the cross-site forgery token, which is not relevant. I would rather see something like:
Thus it appears your server does not ask for a user, which would account for tornado complaining with 403, no current user.
That is perturbing.
Hmm.. that didn't help me. Maybe you could report back with the nbserver.*.json |
An empty |
I have a modicum of control over how the server is run.
How do you want me to run it?
I don't set anything moreover, when I run
and
I still get the same error
|
I know as little about cookies as the next non-web programmer, but artificially parsing an old jar file is mildly suspect. It's conceivable the server insists on new cookies for each new session.
So it sounds like this is the case. The jar file has the username entry, but the in-memory url-cookie-list doesn't, and worse is completely empty, which is very suspect. You should
url-cookie-store isn't firing.
|
this is not an old file - its
|
It sounds like you are continuing along the path of woe of force parsing Starting from scratch, you said |
no, I am not doing that.
|
no
and now
|
Hum, that output looks good. Your token is non-empty "ZZZZ". Your server should not just let you in without asking for it. I've seen inconsistent behaviors when invoking the server with
? I am approaching the limits of what I can advise remotely. On-site troubleshooting is possible for a nominal fee. |
this is the token in
I have been using I can force being asked for the token by removing
The fee is probably not a problem, access is. |
I would be surprised if deleting the cookie jar suddenly caused the server to require ZZZZ. My understanding was the "token" has nothing to do with the cookie business. Either way, it would be instructive to know if a server requiring ZZZZ is better behaved (doesn't 403). |
huh, I renamed cookie jar and repeated #754 (comment)
note that the password/token (288XXX.....) is not in the cookie jar.
2e9XXX is not in the jar either... |
Sorry, I can't help you. It'd be a moderate hassle but replicating the server configuration onto your local laptop and attempting to replicate the problem wholly on one machine might be very instructive. |
That's what did happen!
My understanding is that when a server authenticates a user, it sets a cookie on the client which the client is supposed to submit in all future communications in lieu of re-authentication (this is why intercepting cookies is so dangerous).
No change. |
Ah, you're right. The above statement is a complete falsehood. |
just to make it clear - the problem is HTTP 403 error when connecting to jupyter server behind a proxy |
Are you familiar with ahyatt/emacs-websocket#73? Right now websockets don't work correctly with the rest of emacs connection proxying. There's a fix, but it's kind of half-baked at the moment. You can try the pull request in the fix and see if it helps you. About server authentication & cookies - this really depends on what exactly the server is doing. Normal HTTP authentication doesn't use cookies, but does requires the You should authenticate via whatever HTTP method your server supports at the beginning of the websocket session. Further communication shouldn't need anything, and it's only needed again when you re-connect. Those re-connections should be rare, since the websockets can last a while. |
Problem description
When I click on
New Notebook
, I get the following remote logsand backtrace
Steps to reproduce the problem
had to do
to work around ahyatt/emacs-websocket#75
System info:
The text was updated successfully, but these errors were encountered: