-
Notifications
You must be signed in to change notification settings - Fork 352
Running on a remote machine over SSH with port forwarding? #184
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
Comments
Hi @vvolhejn ! Is this on the latest version of FastRTC? The HF Turn Server is in Us-east region so it could be taking a while to resolve esp if you are using a VPN. Have you tried without VPN or with twilio? We're working on making the HF TURN infrastructure a lot beefier in the next couple of weeks. So please bear with us 🙏 |
Thanks for the response! When I run the server on localhost with the VPN active, it takes about 5 seconds to connect (also from localhost), which is likely due to what you describe. But when I run it on a remote host - let's call it Edit: Yesterday I was using version 0.0.15. I see that a new one came out in the meantime - I've re-tested with 0.0.16, with the same result. |
Same problem here, I guess we need to build a custom webrtc turn server to replace the rtc_configuration. Or you need to run the client locally (only forward the vllm port).
|
Hi! I was experiencing a similar issue using Twilio (get_twilio_turn_credentials), and I realised that my firewall was blocking all iceServers connections to Twilio servers that were using port 3478 (UDP and TCP), waiting around 30 seconds to get a timeout to start the connection. I have fixed it only choosing the iceservers that were using port 443, that is not usually blocked by any firewall. Here you have a code snipped just in case it is useful for you:
|
Shouldn't be necessary but please follow @jjcampana 's suggestion. The UDP/TCP ports need to be open on the remote machine. Does this solve your issue @vvolhejn ? |
Hi! I just tried to test this. Unfortunately, Twilio doesn't allow me to use their Turn servers on a test account (no billing set):
|
same problem here, using openai api with vscode port forwarding |
just chiming in to say similarly, when using remote machine cannot get fastrtc to work even with the echo back hello world type example from the blog post here: https://huggingface.co/blog/fastrtc although using gradio directly I am able to get an audio echo back server working and it works fine if running locally. guessing there is some specific param like the |
Will look into this |
hello @freddyaboulton, any update? |
I have the same problem when trying to run in a docker container. Dockerfile:
Python app:
Command to reproduce:
I can open the window at localhost:7865 but "record" does not work correctly. Edit: I fixed the issue by using host network for the container, instead of exposing ports:
|
Hi, I'm trying to run the FastRTC hello world on a machine I'm SSH'd to:
I've forwarded the 7860 port I'm running the server on and I do see the web UI just fine. But when I press the "record" button, after a few seconds I get the "Taking a while to connect. Are you on a VPN?" popup and nothing happens.
When I run the same server locally, it works fine. In both cases, I am connected to a VPN. What could be going wrong and what is the configuration needed to make this work? Thanks!
The text was updated successfully, but these errors were encountered: