I am trying to use a custom jupyterhub setup and really struggling. I am using jupyterhub 2.3.0 and I also have jupyterlab 3.4.5 installed on the user servers. I set this all up on a single compute instance, made sure everything worked and then distributed some of these parts around in containers.
I am using a custom authentication that is hardcoded to return 'test_user". That is all the auth does until I can isolate this.
I am using this for spawner: GitHub - uktrade/fargatespawner: Spawns JupyterHub single user servers in Docker containers running in AWS Fargate
When I was testing this on a single compute instance w/ local Spawner I saw the cookies and everything worked fine. When I have jupyterhub running in a separate container from the jupyterhub-singleuser instances, users can never access the server.
In the Jupyterhub log I see the server get created and the proxy create the routes:
User logged in: test_user
Not recording activity for status 302 on /jupyterhub
302 POST /jupyterhub/hub/login?next=/jupyterhub/hub → /jupyterhub/hub
PROXY WEB /jupyterhub/user/test_user to http://10.x.x.x/
PROXY WEB /jupyterhub/user/test_user /api/kernels to http://10.x.x.x/
Then in the single user jupyter logs I see basically this:
200 GET /jupyterhub/user/test_user
No user identified
Any ideas on what the problem could be? I think the cookies are missing for some reason. They were working fine on a single node, do I need to handle that somewhere? Do I need to explicitly set user cookies even though I am using the jupyterhub-singleuser launch? I tried to set cookie_secret file to a shared location but jupyterhub-singleuser cookie_secret_file is not recognized so not too sure. I’d really appreciate your thoughts. Thanks!