ideonate / jhsingle-native-proxy

Wrap an arbitrary webapp so it can be used in place of jupyter-singleuser in a JupyterHub setting

Home Page:https://cdsdashboards.readthedocs.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Getting 404 error while launching Streamlit dashboard

sfc-gh-ppadige opened this issue · comments

I'm trying to launch a Streamlit dashboard on Jupyterhub-K8s (EKS) but facing 404 : Not Found You are requesting a page that does not exist! error. I've looked in to the dashboard pod container log, I see below error, and there are no other log statements in the log file.

Screenshot 2022-06-14 at 7 24 39 PM

Screenshot 2022-06-14 at 7 24 22 PM

Whereas same setup is working fine in Minikube, though I see the above error in the log file, Streamlit dashboard launched successfully.

@danlester Could you please help me find the root cause of this issue? TIA.

It really depends on the details of your configuration to be honest... One thing I can say is that the error you're seeing in the logs isn't a problem: https://cdsdashboards.readthedocs.io/en/stable/chapters/troubleshooting.html#dashboards-work-but-object-nonetype-error-in-logs

@danlester Thanks for your response. I've realised that I've been using dynamic storage with [ReadWriteOnce] access type. At the moment we couldn't onboard storage with [ReadWriteMany] access type. As a work around, I've implemented below solution, and it is working.

  • Applying podAffinity rules (to make sure notebook server pod and dashboard server pod schedule on same node so that both pods can share same volume)

  • Stop notebook server and refreshing the dashboard UI worked.

I'm now stuck in below issue. Appreciate your suggestions.

We've integrated Jupyterhub with Okta as our OAuth. Here is the Okta configuration.

Screenshot 2022-06-22 at 11 08 51 PM

I've created a Steamlit dashboard and shared with "All Users" option. When other users (who are alreay part of Okta groups) tried to access the dashboard they are getting 403 : Forbidden error. Though I've created a dashboardaccess role with access:server scope and assigned to these Okta groups, 403 error is not resolved. Folks are able to successfully access the dashboard only when I explicitly add them to one of the above mentioned groups using Mange groups UI in Admin tab.

Wondering if there is any alternate solution?
Screenshot 2022-06-22 at 11 09 44 PM