I run a Discord bot via discord.js. I can connect to my database perfectly fine via my laptop and view all the information. I’ve messed around with the configurations of the MariaDB database, but I just cannot get this to work. My bot hosted on a port on a separate VPS from the same provider who provides me the VPS for the Hestia panel is getting ETIMEDOUT when trying to connect to the database, no idea why? I’m assuming Hestia is somehow blocking the request or something on the VPS. I’ve tried disabling iptables and checked ufw is not on. I don’t know why I get this error, it’s unable to connect to the MariaDB server nor the FTP server, I used to use a DirectAdmin Reseller, I’ve kept the logic entirely the same and just modified the credentials and confirmed it. I used to host my database on a Pterodactyl instance with MariaDB so MariaDB should be compatible just fine with mysql2 package on NodeJS, no clue any ideas?
(Has been unable to connect to FTP nor Database, not even once via my other VPS hosting my Discord bot, but works fine connecting from my laptop, I’ve already set the bind address in configs to 0.0.0.0 to allow others to connect and not just localhost)
Error updating guild information: Error: connect ETIMEDOUT
at PoolConnection._handleTimeoutError (/home/container/node_modules/mysql2/lib/connection.js:205:17)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7) {
errorno: ‘ETIMEDOUT’,
code: ‘ETIMEDOUT’,
syscall: ‘connect’,
fatal: true
}
I miss the output of these two commands (remember to replace YourDBUser with the actual user):
mysql -uroot -e ‘select user,host from mysql.user where user = “YourDBUser”;’
lsof -Pn +c0 -i:3306 -sTCP:LISTEN
Regarding your iptables, you are not allowing connections to mysql port 3306, you should create a rule to allow connections to port 3306 from your external machine. I suppose your ip is 45.134.39.71 (you have a rule accepting all the connections) and that is the reason you can connect to your DB server.
I think I have just made the changes to the iptables and saved them. Thanks for your help in helping me find the issue. I’ll be testing it out right now. Here’s the additional info you requested just in case I messed something else up.
root@server:~# mysql -uroot -e ‘select user,host from mysql.user where user = “ash_bot”;’
±--------±----------+
| User | Host |
±--------±----------+
| ash_bot | % |
| ash_bot | localhost |
±--------±----------+
root@server:~#
root@server:~# lsof -Pn +c0 -i:3306 -sTCP:LISTEN
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
mariadbd 2492198 mysql 58u IPv4 38305343 0t0 TCP *:3306 (LISTEN)
root@server:~#