vencord / vencloud

Vencord API

Vencord

The cutest Discord client mod

A screenshot of vencord showcasing the vencord-theme

Features

• Super easy to install (Download Installer, open, click install button, done)
• 100+ plugins built in: See a list
  • Some highlights: SpotifyControls, MessageLogger, Experiments, GameActivityToggle, Translate, NoTrack, QuickReply, Free Emotes/Stickers, PermissionsViewer, CustomCommands, ShowHiddenChannels, PronounDB
• Fairly lightweight despite the many inbuilt plugins
• Excellent Browser Support: Run Vencord in your Browser via extension or UserScript
• Works on any Discord branch: Stable, Canary or PTB all work (though for the best experience I recommend stable!)
• Custom CSS and Themes: Inbuilt css editor with support to import any css files (including BetterDiscord themes)
• Privacy friendly, blocks Discord analytics & crash reporting out of the box and has no telemetry
• Maintained very actively, broken plugins are usually fixed within 12 hours
• Settings sync: Keep your plugins and their settings synchronised between devices / apps (optional)

Installing / Uninstalling

Visit https://vencord.dev/download

Join our Support/Community Server

https://discord.gg/D9uwnFnqmd

Sponsors

Thanks a lot to all Vencord sponsors!!
generated using github-sponsor-graph

Star History

Disclaimer

Discord is trademark of Discord Inc. and solely mentioned for the sake of descriptivity. Mention of it does not imply any affiliation with or endorsement by Discord Inc.

Using Vencord violates Discord's terms of service

Client modifications are against Discord’s Terms of Service.

However, Discord is pretty indifferent about them and there are no known cases of users getting banned for using client mods! So you should generally be fine as long as you don’t use any plugins that implement abusive behaviour. But no worries, all inbuilt plugins are safe to use!

Regardless, if your account is very important to you and it getting disabled would be a disaster for you, you should probably not use any client mods (not exclusive to Vencord), just to be safe

Additionally, make sure not to post screenshots with Vencord in a server where you might get banned for it

vencloud's Issues

Oauth doesn't seem to work

Essentially I managed to host this in a Type 1 Hypervisor (proxmox) after using a Fedora 38 image for a LXC and adding this config option:

lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir

under my /etc/pve/lxc/<c.id>.conf file.

After that I created my application on the discord developer portal:

And setting up my .env file:

PORT=8080
HOST=0.0.0.0
REDIS_URI=redis:6379
ROOT_REDIRECT=/

DISCORD_CLIENT_ID=11<rest of id>
DISCORD_CLIENT_SECRET=A55<rest of secret>
DISCORD_REDIRECT_URI=https://my-custom-domain-via-reverse-proxy/v1/oauth/callback

PEPPER_SECRETS=0c... # openssl rand -hex 32
PEPPER_SETTINGS=c4... # openssl rand -hex 32

SIZE_LIMIT=33554432

# ALLOWED_USERS=

PROMETHEUS=false

And then run podman build . and podman-compose up -d --force-recreate.

And then finally going to ArmCord:


And getting this error:

Here are the logs from running podman logs -f vencloud_backend_1:

 ┌───────────────────────────────────────────────────┐ 
 │                   Fiber v2.42.0                   │ 
 │               http://127.0.0.1:8080               │ 
 │       (bound on host 0.0.0.0 and port 8080)       │ 
 │                                                   │ 
 │ Handlers ............ 26  Processes ........... 1 │ 
 │ Prefork ....... Disabled  PID ................. 1 │ 
 └───────────────────────────────────────────────────┘ 

22:52:44 | 200 |      0s |   192.168.0.144 | GET     | /v1/oauth/settings 
Failed to request access token: Post "https://discord.com/api/oauth2/token": dial tcp: lookup discord.com on 10.89.0.1:53: read udp 10.89.0.7:44387->10.89.0.1:53: read: connection refused22:52:57 | 500 |  5.004s |   192.168.0.144 | GET     | /v1/oauth/callback 
23:01:42 | 200 |      0s |   192.168.0.144 | GET     | /v1/oauth/settings 
Failed to request access token: Post "https://discord.com/api/oauth2/token": dial tcp: lookup discord.com on 10.89.0.1:53: read udp 10.89.0.7:36356->10.89.0.1:53: read: connection refused23:01:48 | 500 |  5.003s |   192.168.0.144 | GET     | /v1/oauth/callback 
23:03:20 | 200 |      0s |   192.168.0.144 | GET     | /v1/oauth/settings 
23:04:03 | 200 |      0s |   192.168.0.144 | GET     | /v1/oauth/settings 
Failed to request access token: Post "https://discord.com/api/oauth2/token": dial tcp: lookup discord.com on 10.89.0.1:53: read udp 10.89.0.7:34339->10.89.0.1:53: read: connection refused23:04:03 | 500 |  5.004s |   192.168.0.144 | GET     | /v1/oauth/callback 
23:04:41 | 200 |      0s |   192.168.0.144 | GET     | /v1/oauth/settings 
Failed to request access token: Post "https://discord.com/api/oauth2/token": dial tcp: lookup discord.com on 10.89.0.1:53: read udp 10.89.0.7:41391->10.89.0.1:53: read: connection refused23:04:48 | 500 |  5.003s |   192.168.0.144 | GET     | /v1/oauth/callback 

This is exactly what I get (after a few presses of enter on logs) when I try to do an oauth login:

23:05:54 | 200 |      0s |   192.168.0.144 | GET     | /v1/oauth/settings 
Failed to request access token: Post "https://discord.com/api/oauth2/token": dial tcp: lookup discord.com on 10.89.0.1:53: read udp 10.89.0.7:51564->10.89.0.1:53: read: connection refused23:06:01 | 500 |  5.004s |   192.168.0.144 | GET     | /v1/oauth/callback

Port 8080 isn't working with the docker image

Hello!
I've tried to build and self-host the image, built it through my github fork, and when I try to put my URL it says it cannot connect to it (don't worry it is not a network issue I've made sure of that)

You say in your readme that the port for the backend is 8080, but when I pull up the backend logs, it shows this:

Are we sure the backend uses the 8080 port?

env vars untouched:

Why can't we just have a basic Docker Compose Installer?

Seems like it would be easier to just have a docker-compose that installs everything and sets up the ports. Services like CasaOS really like to use this and it would make it so much easier to set this up.

Vencord Cloud issue with UserScript

When using the Vencord UserScript instead of the extension, Vencloud will not turn on after the Discord authorisation popup from clicking the toggle.

help

Can someone please guide me on what to do? As the documentation is quite sparse

Request: removing the need for a reverse proxy to serve at /v1/

that's adding an additionnal step in the configuration for nothing, you should include them directly in the backend so the code can match what the vencord client uses, instead of having everyone changing their config each time you changes the api version

Cant connect to redis

I edited the REDIS_URI to redis:6379 but in the console it says panic: dial tcp: lookup redis on 8.8.4.4:53: no such host