Can you share the deployment logs?

yeah uhh where can i find that

You'll need to navigate to your service, click on the most recent deployment, and go to the deployment logs, then send the content here.

[19:04:17] [startup]: Starting TitanBot...

node src/app.js

[email protected] start

[19:04:18] [startup]: Initializing database...

[19:04:19] [warn]: No schema version found. Bootstrapped schema ledger to version 1 (baseline-v1).

[19:04:19] [startup]: ✅ Database Status: postgresql (fully operational)

[19:04:19] [startup]: Starting web server...

[19:04:19] [startup]: Loading commands...

[19:04:19] [startup]: ✅ Web Server running on 0.0.0.0:8080

[19:04:19] [startup]: Health endpoint: http://0.0.0.0:8080/health

[19:04:19] [startup]: Ready endpoint: http://0.0.0.0:8080/ready

[19:04:19] [startup]: Commands loaded: 99

[19:04:19] [startup]: Loading handlers...

[19:04:19] [startup]: Loading handlers...

[19:04:19] [startup]: Loading handler: events

[19:04:19] [startup]: ✅ Loaded events

[19:04:19] [startup]: Loading handler: interactions

[19:04:19] [startup]: ✅ Loaded interactions

[19:04:19] [startup]: Handlers loaded

[19:04:19] [startup]: Logging into Discord...

[19:04:20] [startup]: Discord login successful

[19:04:20] [startup]: Registering slash commands globally...

[19:04:20] [warn]: Command count (99) is near Discord's 100 global command limit

[19:04:20] [startup]: Ready! Logged in as Nederland Roleplay#9139

[19:04:20] [startup]: Serving 1 guild(s)

[19:04:20] [startup]: Loaded 99 commands

[19:04:20] [startup]: Reaction role reconciliation: scanned 0, removed 0, errors 0

[19:04:20] [startup]: Ticket panel health: scanned 1 guilds, healthy 0, deleted 0, missing channel 0, recovered 0, errors 0

[19:04:20] [startup]: Verification panel health: scanned 1 guilds, healthy 0, deleted 0, missing channel 0, recovered 0, errors 0

[19:04:20] [startup]: Reaction role panel health: scanned 0 panels, healthy 0, deleted 0, missing channel 0, recovered 0, errors 0

[19:04:20] [startup]: Level role sync: scanned 1 guilds, pruned 0 stale rewards, re-awarded 0 roles, errors 0

[19:04:24] [startup]: Slash commands registration complete

[19:04:24] [startup]: ONLINE ✅ | 99 commands loaded | 50 buttons, 4 menus, 10 modals | Database: Connected (persistent data enabled)

[19:05:20] [warn]: Lavalink node "Jirayu" disconnected.

[19:10:20] [warn]: Lavalink node "Jirayu" disconnected.

[19:15:25] [warn]: Lavalink node "Jirayu" error: Unable to connect with Jirayu node after 3 attempts.

[19:35:56] [warn]: Lavalink node "MilloHost" disconnected.

[19:37:42] [error]: TitanBotError: Level 10002 exceeds maximum level 1000

at addLevels (file:///usr/src/app/src/services/leveling/leveling.js:326:13)

at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

at async Object.execute (file:///usr/src/app/src/commands/Leveling/leveladd.js:65:22)

at async file:///usr/src/app/src/events/interactionCreate.js:163:13

at async TitanBot.safeExecute (file:///usr/src/app/src/handlers/loaders/events.js:28:21)

[19:37:53] [error]: TitanBotError: Level 1002 exceeds maximum level 1000

at addLevels (file:///usr/src/app/src/services/leveling/leveling.js:326:13)

at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

at async Object.execute (file:///usr/src/app/src/commands/Leveling/leveladd.js:65:22)

at async file:///usr/src/app/src/events/interactionCreate.js:163:13

at async TitanBot.safeExecute (file:///usr/src/app/src/handlers/loaders/events.js:28:21)

[19:38:05] [error]: TitanBotError: Level 1001 exceeds maximum level 1000

at addLevels (file:///usr/src/app/src/services/leveling/leveling.js:326:13)

at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

at async Object.execute (file:///usr/src/app/src/commands/Leveling/leveladd.js:65:22)

at async file:///usr/src/app/src/events/interactionCreate.js:163:13

at async TitanBot.safeExecute (file:///usr/src/app/src/handlers/loaders/events.js:28:21)

[19:57:43] [warn]: Lavalink node "TriniumHost" disconnected.

[20:28:41] [error]: Track error in 1542550657553399999 for "Perfect Gentleman (2024 Remaster)":

[20:28:41] [error]: Error: Unable to play for Player with Guild Id 1542550657553399999, Queue is empty (length: 0)!

at Player.play (/usr/src/app/node_modules/riffy/build/structures/Player.js:149:39)

at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

is this right?

Is the bot completely unresponsive or offline?

its online but doesnt react to a command

I assume that means Discord shows "The application did not respond"?

yeah

Were you trying to run some kind of leveladd command or a player command when the bot doesn't respond?

(Also, if there is a /ping command, does it respond to that? From the current state, it doesn't seem like the bot has completely crashed...)

it responds to nothing hold on lemme check it

for now just the music

the bot is fully offline now too

I'd try using a different Lavalink node, or selfhost one yourself on Railway (although this may consume your Free plan resources faster)

Are there any crash statements at the very bottom of the deployment logs?

not that i know i see error and some warn things

Same errors as above? (And does the bot come back online on its own?)

not the same above when i try a command its says that it doesnt respond it crashed at 21.28

Could you share the new errors?

[error]: Track error in 1542550657553399999 for "Perfect Gentleman (2024 Remaster)":

[20:28:41] [error]: Error: Unable to play for Player with Guild Id 1542550657553399999, Queue is empty (length: 0)!

at Player.play (/usr/src/app/node_modules/riffy/build/structures/Player.js:149:39)

at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

You can redeploy the service to get the bot back online.

Also, I'd recommend handling errors in your code to make sure the queue isn't empty before a song is being played. Seems like that's what's causing the bot to go down based on the logs.

the service is the thing above the name and thing of the bot the postgress thing

I'm not too sure what you're trying to describe.

You can initiate a redeployment by clicking into the service, clicking the 3 dots next to the active (or most recent) deployment, and select redeploy.

alr, thank you for the help il try it