-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outputs that are larger than 2 MB do not work with share=True
#2260
Comments
Thanks @MrNeon for the interesting issue. This might be a limitation based on how the sharing servers have been configured. Will take a look and get back to you |
Is there any update on this? |
share=True
I've been able to reproduce the issue, but haven't been able to find a fix yet. Sorry about that, we are looking to see what could be the problem |
Not sure if this helps, but if you use ngrok inside Google Colab and use it to point to localhost:7860 and then access through ngrok url instead of gradio.app, it never hangs. Here is the code:
Maybe it helps to see what ngrok is doing differently, unless is a server setting 🤷 |
Hi @R4ZZ3 we're still ironing out some issues related to the FRP branch -- but if you would like to test it out (no guarantee on its stability!) you can do it by installing
before you run your Gradio app. Let me know how it goes! |
Hi everyone! We've now officially merged in #2509, which should increase the file limits of what can be shared with public links, i.e. |
Describe the bug
When using the shared tunneled link I get this error when receiving outputs that are around 2MB or larger.
Error in Chrome: net::ERR_HTTP2_PROTOCOL_ERROR 200

Firefox errors too but without any code, just an uncaught exception.
When using localhost or using ngrok to tunnel the connection the issue never happens.
Is there an existing issue for this?
Reproduction
Screenshot
No response
Logs
System Info
Severity
annoying
The text was updated successfully, but these errors were encountered: