gistfile1.txt

dev@dev-System-Product-Name:~$ docker logs --tail 50 glassesusa.local_ssr
Node server is listening on port 8080!
Node server is listening on port 8080!
(node:1) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at https://glassesusa.local/ms/route/1/womens-eyeglasses reason: Unexpected token < in JSON at position 0
    at /home/node/app/server.js:454:27542
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /home/node/app/server.js:454:21674
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1) 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: 2)
(node:1) [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.
(node:1) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at https://glassesusa.local/ms/route/1/womens-eyeglasses reason: Unexpected token < in JSON at position 0
    at /home/node/app/server.js:454:27542
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /home/node/app/server.js:454:21674
(node:1) 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: 4)
(node:1) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at https://glassesusa.local/ms/route/1/sunglasses?p=1&gender=5 reason: Unexpected token < in JSON at position 0
    at /home/node/app/server.js:454:27542
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /home/node/app/server.js:454:21674
(node:1) 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: 6)
(node:1) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at https://glassesusa.local/ms/route/1/favicon.ico reason: Unexpected token < in JSON at position 0
    at /home/node/app/server.js:454:27542
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /home/node/app/server.js:454:21674
(node:1) 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: 8)
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!
Node server is listening on port 8080!