-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
docs: Vortex Configuration guide #23
Comments
I agree on this aspect i continually get the same issue, i check the debug console and no errors come threw i had to keep attempting till finally got the api working with vortex but when i click join voice call 💩 all happpens |
i also wish some sort of guide existed ive been trying to find out why i cant hear audio when i join a vc and ive tried to find the problem using chrome://webrtc-internals/ but i have had no luck. if anyone knows why that would be much appreciated. |
Marking this issue for use later, Vortex will not be receiving any documentation in the near future since the developer behind it is currently not available. More over there's a lot of things which we want to rebuild or completely replace and we don't have the time spare to currently handle this. I would recommend not self-hosting Vortex until it's received a proper overhaul, though as to consolidate discussion relating to the matter, I'm closing all related issues and pointing them to this comment (as to help out anyone looking for info anyways). |
Hi guys i need help Caused by: Help please... |
Hi, I'm having problems while configuring vortex. The Vortex program seems to work out but it's like it doesn't interface with Revolt: when I click on the button to connect with the voice chat it doesn't have any effect, but when I digit the Vortex URL it shows the following writing :
{"vortex":"0.3.0-alpha.1","features":{"rtp":true},"ws":"wss://vortex.revolt.chat"}
I have already followed every other guide in this site, so I'd like to ask for a more general guide in order to configure it. Thanks for the help.
The text was updated successfully, but these errors were encountered: