#Dashboard "Can't Find You on Discord"

1 messages · Page 1 of 1 (latest)

copper beacon
#

Hi I'm having issues getting the dashboard to work as per the image.

My dashboard settings:

{
    "host": "127.0.0.1",
    "port": "8000",
    "password": "<DASH_PASS>",
    "redirect_url": "https://vocard.domain.com/callback"
}

My vocard settings (the IPC part):

    "ipc_client": {
        "host": "127.0.0.1",
        "port": 8000,
        "password": "<DASH_PASS>",
        "secure": false,
        "enable": true
    },

My nginx config (i have a wildcard cert):

server {
    server_name vocard.domain.com;

    location / {
        proxy_pass http://127.0.0.1:8000;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_read_timeout 600s;
        proxy_send_timeout 600s;
    }
    include /etc/nginx/ssl_cert.conf;
}

I added the bot to my server with the following URL, so not sure if i'm missing some perms: https://discord.com/oauth2/authorize?client_id=<MY_BOT_CLIENT_ID>&scope=bot&permissions=377960279040

#

Dashboard Logs:

2025-12-24 22:08:13 INFO     dashboard Finished processing JavaScript files.
2025-12-24 22:08:13 INFO     dashboard Finished compiling SCSS files.
[2025-12-24 22:08:13 -0600] [1670542] [INFO] Running on http://127.0.0.1:8000 (CTRL + C to quit)
2025-12-24 22:08:13 INFO     hypercorn.error Running on http://127.0.0.1:8000 (CTRL + C to quit)
2025-12-24 22:08:35 INFO     dashboard Bot (<MY_BOT_CLIENT_ID>) has been connected!

Vocard logs:

[2025-12-24 22:08:34] [INFO    ] discord.client: logging in using static token
[2025-12-24 22:08:35] [INFO    ] vocard: Successfully connected to [vocard] MongoDB!
[2025-12-24 22:08:35] [INFO    ] vocard: Loaded Translator
[2025-12-24 22:08:35] [INFO    ] vocard: Loaded playlist
[2025-12-24 22:08:35] [INFO    ] vocard: Loaded basic
[2025-12-24 22:08:35] [INFO    ] vocard: Loaded settings
[2025-12-24 22:08:35] [INFO    ] vocard: Loaded task
[2025-12-24 22:08:35] [INFO    ] vocard: Loaded effect
[2025-12-24 22:08:35] [INFO    ] vocard: Loaded listeners
[2025-12-24 22:08:35] [INFO    ] ipc_client: Connected to dashboard!
[2025-12-24 22:08:35] [INFO    ] vocard: Node [DEFAULT] is connected!
[2025-12-24 22:08:35] [INFO    ] discord.gateway: Shard ID None has connected to Gateway (Session ID: <REDACTED>).
[2025-12-24 22:08:37] [INFO    ] vocard: Changed the bot status to /help
[2025-12-24 22:08:37] [INFO    ] vocard: ------------------
[2025-12-24 22:08:37] [INFO    ] vocard: Logging As <MY_BOT_USER>
[2025-12-24 22:08:37] [INFO    ] vocard: Bot ID: <MY_BOT_CLIENT_ID>
[2025-12-24 22:08:37] [INFO    ] vocard: ------------------
[2025-12-24 22:08:37] [INFO    ] vocard: Discord Version: 2.5.2
[2025-12-24 22:08:37] [INFO    ] vocard: Python Version: 3.13.11 (main, Dec  7 2025, 13:01:45) [GCC 15.2.1 20251112]
[2025-12-24 22:08:37] [INFO    ] vocard: ------------------
#

The only error i've seen on nginx side:

2025/12/24 22:04:50 [error] 1518383#1518383: *189 connect() failed (111: Connection refused) while connecting to upstream, client: <MY_PUBLIC_IP>, server: vocard.domain.com, request: "GET /ws_user HTTP/1.1", upstream: "http://127.0.0.1:8000/ws_user", host: "vocard.domain.com"
wooden pasture
copper beacon
#

looks like i didn't have my correct headers, the red error on the page has disappeard, and i see the 101 response on the network tab on firefox

#

but i still get an error on the back

#

looks like i got it

#

i was tryign with my domain in the host portion in the vocard config, and that was throwing me an error

#

i reverted back to what i posted here, and added modified the nginx config for the wss and it works now apparently

wooden pasture
#

hmm glad to hear that. Your logs looked healthy to me though

copper beacon
#

Added:

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";

so my nginx config now looks like this:

server {
    server_name vocard.domain.com;

    location / {
        proxy_pass http://127.0.0.1:8000;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_read_timeout 600s;
        proxy_send_timeout 600s;
    }
    include /etc/nginx/ssl_cert.conf;
}
#

for anyone stumbling upon this

copper beacon
#

At some point I was also having t his issue in the vocard logs:

 [2025-12-24 22:52:48] [ERROR   ] ipc_client: Error occurred while connecting to dashboard.
... <BUNCH_OF_PYTHON_GARB>
aiohttp.client_exceptions.ConnectionTimeoutError: Connection timeout to host wss://vocard.domain.com:8000/ws_bot

Which only happened when trying to use my domain from vocard settings.json, but idk, for some reason didn't think about actually double checking my websocket support lol

#

leaving that there as well in case it helps someone

wooden pasture
#

That is a common issue, but you are correct, I agree.

#

I probably wouldn't be able to help you today, I just remembered that this might be it. Hard to focus on anything since I was working all night.

copper beacon
#

yeah, thanks a lot, i'm actually mad at how easy of a fix it was, i spent a lot of time getting all the info for this post lmao

if you have some more time, do you have an idea why no image loads in the dashboard? i see some issues on content from discord, but not sure about the artwork for the songs

#

for some reason this just fails a lot idk

wooden pasture
#

I've seen it somewhere

#

I'll try to find more info

copper beacon
#

yeah nw, all good

#

thanks a gain!

wooden pasture
#

probably this one

#

I'm not sure if there was a solution, though

#

If this doesn’t help, then this is a new type of issue we have little info about. I can help with Docker, networking, and basic vocard related topics. But this stuff is outside my scope, unfortunately.

wooden pasture
#

@copper beacon so how did it go for you? Have you managed to fix it?

copper beacon
#

I didn't try to fix it, haven't looked into it