Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Jupyter notebook Connection failed because Ambassador doesn't enable websockets #1344

Closed
fyuan1316 opened this issue Aug 10, 2018 · 2 comments
Closed

Jupyter notebook Connection failed because Ambassador doesn't enable websockets #1344

fyuan1316 opened this issue Aug 10, 2018 · 2 comments
Labels
area/jupyter Issues related to Jupyter priority/p1

Comments

@fyuan1316
Copy link
Contributor

version: kubeflow v0.2.2

when create a py2 or py3 notebook, receive error message:

Connection failed

A connection to the notebook server could not be established. The notebook will continue trying to reconnect. Check your network connection or notebook server configuration.`

in chrome console , there 's more details:

WebSocket connection to 'ws://150.109.69.83:31758/user/test/api/kernels/e064f45c-5e72-4814-82c2-f01c3dd48796/channels?session_id=d1b557af758946b0b55d61dcc9380cdc' failed: Error during WebSocket handshake: Unexpected response code: 403

image
@fyuan1316 fyuan1316 mentioned this issue Aug 10, 2018
Merged
@jlewi jlewi changed the title Jupyter notebook Connection failed Jupyter notebook Connection failed because Ambassador doesn't enable websockets Aug 10, 2018
@jlewi
Copy link
Contributor

jlewi commented Aug 10, 2018

Thanks for the report and the fix.

I'm curious why we haven't run into this before. My conjecture is that most people don't access Jupyter through Ambassador. On GKE I think we might be redirecting to JupyterHub before going through Ambassador.

@jlewi jlewi added priority/p1 area/jupyter Issues related to Jupyter labels Aug 10, 2018
k8s-ci-robot pushed a commit that referenced this issue Aug 14, 2018
@fyuan1316 @k8s-ci-robot
fixes issue #1344 (#1345)
753506b
@Aravinviju
Copy link

Hi Whats the Fix for this?
I'm not sure where to find it!
I'm facing the same issue.

Any help would be of great help!

Thanks
Arav

@anupash147 anupash147 mentioned this issue Sep 9, 2019
Closed
saffaalvi pushed a commit to StatCan/kubeflow that referenced this issue Feb 11, 2021
@fyuan1316 @k8s-ci-robot
fixes issue kubeflow#1344 (kubeflow#1345)
01b4d26
yanniszark pushed a commit to arrikto/kubeflow that referenced this issue Feb 15, 2021
@andreyvelich
Early Stopping Implementation (kubeflow#1344)
60f6c20 
* Init commit

* Experiment API changes

* Add APIs

* Remove old es apis

* Remove logging

* Add Early Stopping implementation

* Show metrics for early stopped trials

* Clean const

* Remove pid file with completed line from metrics collector

* Add unit test

* Add EarlyStopping as unique service

* Add early stopped Trials to completed

* Fix few comments

* Generate clients and SDK

* Fix tests

* Fix goptuna test

* Remove cluster role from test

* Update observation for early stopped Trials

* Fix pv name in e2e test

* Add Katib config for Early Stopping

* Fix comment

* Remove unused gRPC Experiment spec

* Remove legacy test files

* Remove labels and conditions from example

* Modify API to be consistent with Algorithm

* Ignore no such file error

* Add comments to proto

* Add median stop implementation

* Fix few comments

* Fix unit tests

* Add o-type flag to tfevent metrics collector

* Fix es unit test

* Fix hyperband suggestion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/jupyter Issues related to Jupyter priority/p1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jlewi @Aravinviju @fyuan1316