BinderHub fails to launch notebook server despite logs indicating success

I am trying to test a binderhub deployment.

This is the log I get:

Found built image, launching…
Launching server…
Server requested
2025-09-10T16:41:03.992366Z [Normal] Successfully assigned ocw/jupyter-aashishpanta0-n-a–x—7e8681fd to ip-192-168-43-101.us-west-2.compute.internal
2025-09-10T16:41:06Z [Normal] AttachVolume.Attach succeeded for volume “pvc-6ec37581-e076-4fe3-93ef-3c0ce081fd58”
2025-09-10T16:41:07Z [Normal] Pulling image “ Quay
2025-09-10T16:41:08Z [Normal] Successfully pulled image “ Quay in 1.647s (1.647s including waiting)
2025-09-10T16:41:08Z [Normal] Created container block-cloud-metadata
2025-09-10T16:41:08Z [Normal] Started container block-cloud-metadata
2025-09-10T16:41:09Z [Normal] Pulling image “nasasattrain/binder-dev-aashishpanta0-2dnasa-2darset-2dtraining-d0bc74:e90b2ec406fe37cf381f945f89caf771f6decc7a”
2025-09-10T16:41:53Z [Normal] Successfully pulled image “nasasattrain/binder-dev-aashishpanta0-2dnasa-2darset-2dtraining-d0bc74:e90b2ec406fe37cf381f945f89caf771f6decc7a” in 44.022s (44.022s including waiting)
2025-09-10T16:41:53Z [Normal] Created container notebook
2025-09-10T16:41:53Z [Normal] Started container notebook
Server ready at /user/aashishpanta0-n–arset-training-asq4onr3/
server running at

If I click on the above URL manually, it does work but it leaves me inside a landing page asking me for a password or user token.

So nothing appears to be wrong, and when I check every single pod log I can’t see any issues either. Only thing that seems amiss is this from the hub pod:

Warning Unhealthy 17m (x3 over 17m) kubelet Readiness probe failed: Get “”: dial tcp 192.168.109.199:8081: connect: connection refused

Do you have the same error with one of the example repositories such as

?

1 Like