-
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
With gradio==4.18.0, only get loading screen for server for remote connections going through nginx #7391
Comments
Related of course, but not same issue: #6920 Would be good if both related issues were fixed. I'm back to gradio 3.50.2 again because of these two regressions. |
Could you open your browser console and tell us if there are any errors being reported? |
Hmm yes it would be great if you could share a repro with the nginx config as well please @pseudotensor |
Dev console in bad 4.18.0 case:
I can't just share screenshot since it has private information. So I've redacted the text above for DNS to xxxx.ai. For completeness, for h2oGPT, the only error in dev console I get when using 4.17.0 is the TypeError one and 2 warnings w.r.t. non-interactive or hidden tab that are probably ignorable:
|
Ah interesting, I thought I fixed this issue. Can you possibly share the code for the Gradio app as well? |
I think any gradio app will do it, let me launch a trivial one. |
The full app I'm launching is h2oGPT. This one doesn't behave the same, but still behaves badly:
Note that direct port access to that simple gradio app is still good like h2oGPT is good: Nothing appears in dev console for this direct port access. If it's helpful, I can see if there's a specific extra thing in h2oGPT that makes it even worse (i.e. only loading screen), but I'd guess the errors provided give sufficient hints. I'm not an nginx expert, but if required I can figure out how to start that locally so a remote connection would fail in this way. But hopefully there's enough info so far for some insights. I guess gradio testing might benefit from nginx and k8, google colab, and other cloud testing. |
@FurkanGozukara are you open to sharing your runpod url if its a public url? |
@abidlabs |
@abidlabs We setup a nginx case for you as well. The config is:
Raw system is at: http://52.0.25.199:14051/ Raw shows: Proxy shows: |
Thank you @pseudotensor and @FurkanGozukara! Looking into this |
I think I know the problem, setting up my own nginx server to test |
@pseudotensor it looks like the site is down, would you be able to restart please? |
It's back, thanks! |
I left it open like 1 day yesterday :/ it burns money on runpod haha if you are here reply me i will open again |
Nw @FurkanGozukara I'm working off of the logs from @pseudotensor's for now. I'll open a PR for you guys to try soon |
@FurkanGozukara @pseudotensor could you please try installing this version of
|
That'd be great! Let me know if you see any issues |
I played around with a few things and don't notice any issues. So probably back to 4.17.0 behavior, thanks! |
Amazing, thanks for confirming! |
hello. I just tested and still same error for me :/ when you are here let me know i will start an instance for you on a cheap gpu and leave open pip freeze
|
Can you please try with |
hello i just tested same here you can test running on rtx 4090 please let me know if you are available |
The problem seems to be that the Runpod Proxy isn't passing along the headers properly. I see this request in the logs: ![]() So its trying to get the theme from "https://localhost:7860/". I can also confirm this by going to: https://eneoz4xloaxllz-7861.proxy.runpod.net/config and looking at the bottom most part of the dict, where it says that "root": "https://localhost:7860/" So this tells me two things:
Do you know if its possible to configure the Runpod Proxy @FurkanGozukara? You'd want to set it up like this:
(if its nginx) or
if its apache |
@abidlabs I will forward this to them. can i close pod now? |
Yes sure thanks @FurkanGozukara! |
hello again. they made the changes but still same error here can you test? https://eneoz4xloaxllz-3001.proxy.runpod.net/ they suspect this : #4463 |
The host header is still not being set correctly as far as I can tell. You can check by going to: https://eneoz4xloaxllz-3001.proxy.runpod.net/config and looking at the root. This is directly the |
thanks forwarding right now |
I have similar issues working with privateGPT |
@abidlabs Actually I still have issues with this. gr.Audio playing gets stuck and doesn't play, and then never goes to stop/pause mode after clicking play. However, this only happens for the indirect nginx DNS not the direct port. So should re-open this issue. |
Ok let me reopen so that we can figure this out -- so the only issues you are seeing are with |
Oh noticed that you opened a separate issue with more details -- will close this |
Ya sorry, related to this issue, ok to only look at new one, but I guess seems systemic problem. |
Describe the bug
With gradio==4.18.0, only get loading screen for server for remote connections
Have you searched existing issues? 🔎
Reproduction
No repro yet, but it works locally, but not when using nginx on remote server.
It happens each time I switch back and forth. So something new broke nginx/proxy use in gradio 4.18.0.
For gradio 4.18.0, using non-ngnix name, just raw ip/port, works fine. So definitely proxy issue that wasn't there in 4.17.0.
Screenshot
Logs
No response
System Info
Severity
Blocking usage of gradio
The text was updated successfully, but these errors were encountered: