I noticed some warnings when running the project (from source code, not binary):
In console back end:
(node:27780) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 172.217.160.78:443 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14) (node:27780) 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(). (rejection id: 3)
After logging in, Chrome suggests that the login is not safe:
Does anyone have similar issue?
Update: May be it's because the console is printing out login credentials each time...
like welcome $2b$10$zoD.V4IYLhWmwz5Kld3gAu/jhYsPZYDYAWamQToQeC4tenQ1p1wwS
I checked the code but didn't find where this info gets printed...?
I noticed some warnings when running the project (from source code, not binary):
In console back end:
(node:27780) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 172.217.160.78:443 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14) (node:27780) 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(). (rejection id: 3)
After logging in, Chrome suggests that the login is not safe: Does anyone have similar issue?
Update: May be it's because the console is printing out login credentials each time... like
welcome $2b$10$zoD.V4IYLhWmwz5Kld3gAu/jhYsPZYDYAWamQToQeC4tenQ1p1wwS
I checked the code but didn't find where this info gets printed...?