You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Hi! This has to be configured by the JupyterHub/K8s admin. We can't make it a default in Z2JH because there are multiple ingress providers, the parameter could by set by the K8s admin and we wouldn't want to hard-code an override, and it depends on what you as the JupyterHub admin want to set as the maximum size.
If you think the docs could be improved though please open a pull request. Thanks!
Bug description
Using ingress mode, I got 413 when I save a file (not so large).
I found that wrong ingress proxy configuration causes this problem.
** I already found a solution but I think it should be reported and fixed***
https://z2jh.jupyter.org/en/latest/administrator/advanced.html
https://stackoverflow.com/questions/64759983/nginx-ingress-returns-413-entity-too-large
How to reproduce
Expected behaviour
Saved a file successfully.
Actual behaviour
Got 413 request entity too large with Ingress proxy.
Your personal set up
ubuntu 20.20
microk8s: v1.26.11
JupyterHub with Kubernetes: 3.0.3
Jupyterlab: 4.0.8
Solution
Change JupyterHub Ingress configuration.
The text was updated successfully, but these errors were encountered: