Unable to join voice channel #17

New Issue

2026-02-16T12:51:07-05:00

yindo commented

2026-02-16 12:51:07 -05:00

Originally created by @spoctoss on GitHub (Jan 10, 2022).

Managed to get revolt running using docker swarm with traefik as the reverse proxy. However I am still facing an issue with being unable to join voice channels. The API server seems to be getting the request to join and says the request is successful but the browser is showing a 400 error for a request to the API server.

[2022-01-10T21:34:16Z INFO  rocket::server] POST /channels/01FQF3P68N2CNBP1QAH7TZ0P4W/join_call:
[2022-01-10T21:34:16Z INFO  rocket::server] Matched: (req) POST /channels/<target>/join_call
[2022-01-10T21:34:16Z INFO  rocket::server] Outcome: Success
[2022-01-10T21:34:16Z INFO  rocket::server] Response succeeded.

xhr.js:187 POST https://<removed real URL>/channels/01FQF3P68N2CNBP1QAH7TZ0P4W/join_call 400

Error: Request failed with status code 400
    at mp (createError.js:16)
    at T2 (settle.js:17)
    at XMLHttpRequest.f (xhr.js:54)

Originally created by @spoctoss on GitHub (Jan 10, 2022). Managed to get revolt running using docker swarm with traefik as the reverse proxy. However I am still facing an issue with being unable to join voice channels. The API server seems to be getting the request to join and says the request is successful but the browser is showing a 400 error for a request to the API server. ``` [2022-01-10T21:34:16Z INFO rocket::server] POST /channels/01FQF3P68N2CNBP1QAH7TZ0P4W/join_call: [2022-01-10T21:34:16Z INFO rocket::server] Matched: (req) POST /channels/<target>/join_call [2022-01-10T21:34:16Z INFO rocket::server] Outcome: Success [2022-01-10T21:34:16Z INFO rocket::server] Response succeeded. ``` ``` xhr.js:187 POST https://<removed real URL>/channels/01FQF3P68N2CNBP1QAH7TZ0P4W/join_call 400 ``` ``` Error: Request failed with status code 400 at mp (createError.js:16) at T2 (settle.js:17) at XMLHttpRequest.f (xhr.js:54) ```

yindo closed this issue

2026-02-16 12:51:07 -05:00

yindo commented

2026-02-16 12:51:08 -05:00

@Zomatree commented on GitHub (Jan 10, 2022):

Are you running vortex which is required for voice channels? its not included in the docker compose file by default yet so you there is a possibility you are not running it.

@Zomatree commented on GitHub (Jan 10, 2022): Are you running [vortex](https://github.com/revoltchat/vortex) which is required for voice channels? its not included in the docker compose file by default yet so you there is a possibility you are not running it.

yindo commented

2026-02-16 12:51:08 -05:00

@spoctoss commented on GitHub (Jan 10, 2022):

That's probably it as I am not running it currently. I will tinker with that for a bit and see how far I get. Is there any documentation on running it selfhosted yet?

Thanks for the response

@spoctoss commented on GitHub (Jan 10, 2022): That's probably it as I am not running it currently. I will tinker with that for a bit and see how far I get. Is there any documentation on running it selfhosted yet? Thanks for the response

yindo commented

2026-02-16 12:51:08 -05:00

@spoctoss commented on GitHub (Jan 10, 2022):

I got vortex going and configured, restarted everything, checked vortex is responding via http. Still getting the same 400 error from the api server when trying to join a voice channel. No logs in the vortex container. Any ideas?

@spoctoss commented on GitHub (Jan 10, 2022): I got vortex going and configured, restarted everything, checked vortex is responding via http. Still getting the same 400 error from the api server when trying to join a voice channel. No logs in the vortex container. Any ideas?

yindo commented

2026-02-16 12:51:08 -05:00

@FrostiiZ commented on GitHub (Jan 26, 2022):

I've got Vortex setup and running on my own server and I've faced a similar error 400 in the console. Mine was related to a wrong websocket address.

First thing I always do with Revolt is check the json response on Delta's port 8000. This lists all the routes that are declared to the back-end from the .env file. You can easily see if any route is wrong. On my side, the websocket route of vortex was wrong.

While I was trying to deploy Vortex, I saw the client was using ws://example.com instead of my configuration, but the key "WS_URL" was already set. Check that you've setup the env variables called "VOSO_PUBLIC_URL" and "VOSO_WS_HOST" along with "WS_URL". VOSO_WS_HOST was the missing key in my configuration, but the back-end was watching for this value for Vortex's websocket.

Also, I've seen that the front-end uses the browser's local storage and cookies to store different informations, including routes. When changing your .env file, make sure you've refreshed your containers to use the updated values, and also try to clear all data of the front-end on your browser. This should refresh all the routes.

After this, Vortex is running on my own server and I can connect to a voice channel.

For your interest, I have also deployed the revolt stack behind a reverse-proxy, I'm using the swag container from LinuxServer.io.

Sorry if this comment is a bit weird to read, English is not my primary language. :) I hope I've been somehow helpful, or to someone else facing a smilliar issue as I did.

@FrostiiZ commented on GitHub (Jan 26, 2022): I've got Vortex setup and running on my own server and I've faced a similar error 400 in the console. Mine was related to a wrong websocket address. **First thing I always do with Revolt is check the json response on Delta's port 8000**. This lists all the routes that are declared to the back-end from the .env file. You can easily see if any route is wrong. On my side, the websocket route of vortex was wrong. While I was trying to deploy Vortex, I saw the client was using ws://example.com instead of my configuration, but the key "WS_URL" was already set. Check that you've setup the env variables called "**VOSO_PUBLIC_URL**" and "**VOSO_WS_HOST**" along with "**WS_URL**". **VOSO_WS_HOST** was the missing key in my configuration, but the back-end was watching for this value for Vortex's websocket. Also, I've seen that the front-end uses the browser's local storage and cookies to store different informations, including routes. When changing your .env file, make sure you've refreshed your containers to use the updated values, and also try to clear all data of the front-end on your browser. This should refresh all the routes. After this, Vortex is running on my own server and I can connect to a voice channel. For your interest, I have also deployed the revolt stack behind a reverse-proxy, I'm using the swag container from LinuxServer.io. Sorry if this comment is a bit weird to read, English is not my primary language. :) I hope I've been somehow helpful, or to someone else facing a smilliar issue as I did.

yindo commented

2026-02-16 12:51:08 -05:00

@josealonso commented on GitHub (Apr 4, 2022):

@kylesmith63, @FrostiiZ, what did you do to make the Network Error on the login page go away ? I'm using the .env file shown in the docs. Did you change it ?

@josealonso commented on GitHub (Apr 4, 2022): @kylesmith63, @FrostiiZ, what did you do to make the `Network Error` on the login page go away ? I'm using the `.env` file shown in the docs. Did you change it ?

yindo commented

2026-02-16 12:51:08 -05:00

@josealonso commented on GitHub (Apr 4, 2022):

@FrostiiZ, I visited the linuxserver.io web page and I didn't see the revolt chat used anywhere.

@josealonso commented on GitHub (Apr 4, 2022): @FrostiiZ, I visited the *linuxserver.io* web page and I didn't see the revolt chat used anywhere.

yindo commented

2026-02-16 12:51:08 -05:00

@FrostiiZ commented on GitHub (Apr 27, 2022):

@kylesmith63, @FrostiiZ, what did you do to make the Network Error on the login page go away ? I'm using the .env file shown in the docs. Did you change it ?

Yes, the .env file have been changed. The env variables that have been modified on my side are explained in my last comment. Take a closer look at "VOSO_PUBLIC_URL" "VOSO_WS_HOST" "WS_URL"
To fix my network error, I had to add the missing key "VOSO_WS_HOST" in my .env file with the correct address.

@FrostiiZ, I visited the linuxserver.io web page and I didn't see the revolt chat used anywhere.

Swag is just a very robust web server and reverse-proxy container that uses nginx behind the hood. This is to state that Revolt and Vortex can run behind such a setup for those wondering if it's possible or not. Swag is not shipped with a default config for Revolt, I had to create my own proxy configuration to make it work.

@FrostiiZ commented on GitHub (Apr 27, 2022): > @kylesmith63, @FrostiiZ, what did you do to make the `Network Error` on the login page go away ? I'm using the `.env` file shown in the docs. Did you change it ? Yes, the .env file have been changed. The env variables that have been modified on my side are explained in my last comment. Take a closer look at "**VOSO_PUBLIC_URL**" "**VOSO_WS_HOST**" "**WS_URL**" To fix my network error, I had to add the missing key "**VOSO_WS_HOST**" in my .env file with the correct address. > @FrostiiZ, I visited the _linuxserver.io_ web page and I didn't see the revolt chat used anywhere. Swag is just a very robust web server and reverse-proxy container that uses nginx behind the hood. This is to state that Revolt and Vortex can run behind such a setup for those wondering if it's possible or not. Swag is not shipped with a default config for Revolt, I had to create my own proxy configuration to make it work.

yindo commented

2026-02-16 12:51:08 -05:00

@insertish commented on GitHub (Apr 29, 2022):

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.

@insertish commented on GitHub (Apr 29, 2022): 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.

yindo referenced this issue

2026-02-16 12:51:39 -05:00

[PR #17] [MERGED] Added warning to readme #145

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#17