Bot crashing with Error: Error: Connection error about palbot

[Ly-sec]

Please double check that your rcon password is still set.
Just updated my server and everything seems to be working fine.

[alex010x]

Password is correctly set.
It works for a while, then suddenly crash with that error, which I guess is somehow related to the rcon connect failure

[Ly-sec]

So I assume you're using the whitelist feature, right?
Please download the newest version and see if that fixes it.

[alex010x]

Yes, whitelist feature.
I tried the new version, but error is still ongoing.

[Ly-sec]

Can you try disabling the whitelist and try to use other rcon commands (players, broadcast etc)? I would love to know if you also get errors with that.

[alex010x]

Yea.

Error connecting to Rcon: Error: Connection error
    at Socket.<anonymous> (/root/PalBot-v2/node_modules/minecraft-rcon-client/lib/index.js:29:68)
    at Object.onceWrapper (node:events:633:26)
    at Socket.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

Error: Connection error
    at Socket.<anonymous> (/root/PalBot-v2/node_modules/minecraft-rcon-client/lib/index.js:29:68)
    at Object.onceWrapper (node:events:633:26)
    at Socket.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[Ly-sec]

This is very odd since it seems like most people don't have an issue with that.
Are you connecting through the rcon port (25575), are you using the correct IP address?
Did you setup the password in your palworld server config?

[Ly-sec]

I pushed an attempt at fixing this issue, since I didn't encounter it yet I can only guess. It started happening since the status feature is in place so please download / pull the newest version and see if that helps.

[alex010x]

Same error from here: #9 (comment) ?

Still got the same errors as before, with the new version. So far, /server seems to be the only command working

[Ly-sec]

Same error from here: #9 (comment) ?

Still got the same errors as before, with the new version. So far, /server seems to be the only command working

I really don't get it, it's working totally fine for me and also others. Wanna add me on discord (Lysec) real quick? might be easier to troubleshoot

[Ly-sec]

Should be fixed now!

Closing this issue since we got a fully reworked bot. Let's see what other issues are going to appear now.