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
Aftter some seconds when I run the command
npm run start stops and displays the following error:
(node:20824) UnhandledPromiseRejectionWarning: MongoServerSelectionError: connect ETIMEDOUT 3.210.115.71:27017
at Timeout._onTimeout (F:\Java-Jsf-1\tutorial-react\React-For-the-Rest-Of-Us\backend-api\node_modules\mongodb\lib\sdam\topology.js:292:38)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
(Use node --trace-warnings ... to show where the warning was created)
(node:20824) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:20824) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
P.S.This happened in section 4/28.
The text was updated successfully, but these errors were encountered:
Aftter some seconds when I run the command
npm run start stops and displays the following error:
(node:20824) UnhandledPromiseRejectionWarning: MongoServerSelectionError: connect ETIMEDOUT 3.210.115.71:27017
at Timeout._onTimeout (F:\Java-Jsf-1\tutorial-react\React-For-the-Rest-Of-Us\backend-api\node_modules\mongodb\lib\sdam\topology.js:292:38)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
(Use
node --trace-warnings ...
to show where the warning was created)(node:20824) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)(node:20824) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
P.S.This happened in section 4/28.
The text was updated successfully, but these errors were encountered: