Issues · marimo-team/marimo
Hey Marimo team 🙂 We are trying to host a notebook and having some trouble with it, just wanted to crosspost this here: https://github.com/marimo-team/marimo/issues/31. Happy to clarify anything about our setup
GitHub
Issues · marimo-team/marimo
Reactive notebooks that double as apps. Contribute to marimo-team/marimo development by creating an account on GitHub.
11 Replies
cross posting from github:
how many instances of your container are you running? the server has internal state (including the active sessions) and GCP could be distributing your requests across instances. one possible fix is reducing to one instance or setting up a custom load-balancer or reverse-proxy to manage traffic.
Ah, I was wondering that. It's a deployment with 2 replicas.
if you do want multiple containers, you could set the Session Affinity
https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-configuration#session_affinity
Nice, will give that a try. Thanks!
I reduced it to 1 replica, and that seems to have fixed the client side issues. But it's still retrying the
/iosocket and /instatiate requests over and over again, and not loading any of the charts. On the server side, I still see OSError: [Errno 9] Bad file descriptor
Although, I'm not sure that error is related, since it doesn't show up on each /instantiate requestCan you try upgrading to the latest version? I noticed you were on an old version. May not fix it but could give a better error
Are you able to deploy something super basic that just renders markdown and has no dependencies? It can help reduce the scope
Yeah, will do
hey @regis, how did upgrading go?
Hey Myles, thanks for checking in. Upgrade was easy, and I think it revealed the real issue, which seems to be some auth stuff on our end. I'll update you here in a bit 🙂
I fixed a bunch of issues on our end (we did this in a new cluster so some service accounts needed to be created), but page still not working. I think it's a CORS issue with IAP requests, everything after the first one is blocked by the cors policy. Looking into it...
We have CSRF headers which could be getting stripped as well
Hey Myles, this ended up being the main thing we were missing. It needed to be enabled in IAP. In case anyone else runs into something similar. Seems to be mostly working now, thanks for the help!
nice find!