search

revoltchat / vortex

(in development) Pluggable WebRTC Voice Server
GNU Affero General Public License v3.0
119 stars 42 forks source link

the vc kicks users out for no reason #18

Closed scottoss closed 2 years ago

scottoss commented 2 years ago

i hear audio and it does work but it auto disconnect after like 1 minute

jim3692 commented 2 years ago

If you run Revolt behind Nginx, you have to add these to the WebSockets proxies

proxy_read_timeout 86400s;
proxy_send_timeout 86400s;

Check my full Nginx Revolt configuration here

IowaZoomer commented 2 years ago

I'm also experiencing this issue. However, I suspect it may be caused by something different. I've tried using the nginx site configuration above along with a couple of other templates people have provided. The result is still the same though. Even when using a clean docker image. A user in the vc will drop at random and have to join back. Sometimes those who weren't kicked from the vc have to mute then unmute their mic in order for the person who joined back to hear them again.

IowaZoomer commented 2 years ago

I'm also experiencing this issue. However, I suspect it may be caused by something different. I've tried using the nginx site configuration above along with a couple of other templates people have provided. The result is still the same though. Even when using a clean docker image. A user in the vc will drop at random and have to join back. Sometimes those who weren't kicked from the vc have to mute then unmute their mic in order for the person who joined back to hear them again.

I should also add that I have cloudflare standing in front of my instance. Websocket traffic is also proxied through cloudflare now along with https. I wonder if that's causing some sort of disruption leading to users in my instance getting randomly disconnected.

jim3692 commented 2 years ago

You probably need to check Cloudflare's documentation or contact their support. In my setup, users connect directly to my nginx proxy.

insertish commented 2 years ago

Can't tell if this is related to revolt.chat or a self-hosted instance;

Please re-open if this is an issue relating to revolt.chat otherwise:

In an effort to clean up the global issue tracker, I'm currently consolidating all issues regarding self-hosting Vortex into https://github.com/revoltchat/vortex/issues/23#issuecomment-1113594595.