In case that there is many lines on Jupyter notebook, we face upload size error as shown above.
Does anybody have a solution on this?
do you see more detailed information in workspace log. You can find it here
do you have large dataset of just a big cell with many lines of code? Have you tried sync changes?
I can see User container is taking too long to configure errors.
WARN 2025-09-19 11:36:20.125 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:20.275 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:20.427 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:20.577 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:20.740 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:20.914 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:21.076 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:21.225 User container is taking too long to configure, proxying requests but reporting a warning
WARN 2025-09-19 11:36:21.233 [WARNING ServerApp] ServerApp.token config is deprecated in 2.0. Use IdentityProvider.token.
WARN 2025-09-19 11:36:21.287 [WARNING ServerApp] A _jupyter_server_extension_points function was not found in nbclassic. Instead, a _jupyter_server_extension_paths function was found and will be used for now. This function name will be deprecated in future releases of Jupyter Server.
INFO 2025-09-19 11:36:21.336 [W 2025-09-19 02:36:20.855 FileIdExtension] Config option kernel_spec_manager_class not recognized by FileIdExtension. Did you mean file_id_manager_class?
WARN 2025-09-19 11:36:21.379 User container is taking too long to configure, proxying requests but reporting a warning
INFO 2025-09-19 11:36:21.383 [W 2025-09-19 02:36:20.855 FileIdExtension] Config option kernel_spec_manager_class not recognized by FileIdExtension. Did you mean file_id_manager_class?
WARN 2025-09-19 11:36:21.454 [WARNING FileIdExtension] Config option kernel_spec_manager_class not recognized by FileIdExtension. Did you mean file_id_manager_class?
INFO 2025-09-19 11:36:21.506 [INFO ServerApp] jupyter_server_fileid | extension was successfully linked.
WARN 2025-09-19 11:36:21.551 User container is taking too long to configure, proxying requests but reporting a warning
INFO 2025-09-19 11:36:21.558 [W 2025-09-19 02:36:20.859 TerminalsExtensionApp] Config option kernel_spec_manager_class not recognized by TerminalsExtensionApp. Did you mean terminal_manager_class?
INFO 2025-09-19 11:36:21.614 [W 2025-09-19 02:36:20.860 TerminalsExtensionApp] Config option kernel_spec_manager_class not recognized by TerminalsExtensionApp. Did you mean terminal_manager_class?
WARN 2025-09-19 11:36:21.671 [WARNING TerminalsExtensionApp] Config option kernel_spec_manager_class not recognized by TerminalsExtensionApp. Did you mean terminal_manager_class?
WARN 2025-09-19 11:36:21.703 User container is taking too long to configure, proxying requests but reporting a warning
Hi Jacob_SE,
Could you please inspect your network tab requests and find the corresponding request for the 403? Sometimes 403s occur due to client-side firewalling, or there’s something else going on here. Either way there should be more info in the network logs.