You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for the code... it seems I am doing something wrong, but i have no idea what is happening:
I tried to run your code, but i got connection refused ( I think something wrong whith por number... server is listenning port 8080 and sequelize/database are using 3306 by default ).
At models/index.js I just added a line to change the port:
host: config.HOST,
dialect: config.dialect,
operatorsAliases: 0,
port:'8080'
Now connection is not refused, but i got a time out error
original: Error: connect ETIMEDOUT
at Connection._handleTimeoutError (C:[...]\node_modules\mysql2\lib\connection.js:189:17)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
fatal: true
}
}
I am using "mysql2": "^2.3.3" and "sequelize": "^6.28.0"... Maybe the error could be from differente versions of the packages?
Thanks in advance.
Cheers
The text was updated successfully, but these errors were encountered:
Hi, thanks for the code... it seems I am doing something wrong, but i have no idea what is happening:
I tried to run your code, but i got connection refused ( I think something wrong whith por number... server is listenning port 8080 and sequelize/database are using 3306 by default ).
At models/index.js I just added a line to change the port:
host: config.HOST,
dialect: config.dialect,
operatorsAliases: 0,
port:'8080'
Now connection is not refused, but i got a time out error
original: Error: connect ETIMEDOUT
at Connection._handleTimeoutError (C:[...]\node_modules\mysql2\lib\connection.js:189:17)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
fatal: true
}
}
Thanks in advance.
Cheers
The text was updated successfully, but these errors were encountered: