Ryfujk

I have pushed all this code to my Github repo, TravisCI built a test image and tested my code, it passed the test. TravisCI then built production images, TravisCI pushed the production builds over to my Docker Hub and over to AWS Elasticbeanstalk, EB then presumably pulled the images from my Docker Hub and deployed it.

I am getting a 502 Bad Gateway on my application and I looked at the EB Logs and I believe this is the problem:

/var/log/containers/server-8b2907355681-stdouterr.log

-------------------------------------





> @ start /app

> node index.js





Listening

{ error: password authentication failed for user "Postgres"

    at Connection.parseE (/app/node_modules/pg/lib/connection.js:553:11)

    at Connection.parseMessage (/app/node_modules/pg/lib/connection.js:378:19)

    at Socket.<anonymous> (/app/node_modules/pg/lib/connection.js:119:22)

    at Socket.emit (events.js:189:13)

    at addChunk (_stream_readable.js:284:12)

    at readableAddChunk (_stream_readable.js:265:11)

    at Socket.Readable.push (_stream_readable.js:220:10)

    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

  name: 'error',

  length: 104,

  severity: 'FATAL',

  code: '28P01',

  detail: undefined,

  hint: undefined,

  position: undefined,

  internalPosition: undefined,

  internalQuery: undefined,

  where: undefined,

  schema: undefined,

  table: undefined,

  column: undefined,

  dataType: undefined,

  constraint: undefined,

  file: 'auth.c',

  line: '328',

  routine: 'auth_failed' }

However, I have corrected the password inside of EB Configuration to match exactly the one docker-compose.yml file:

api:

    build:

      dockerfile: Dockerfile.dev

      context: ./server

    volumes:

      - /app/node_modules

      - ./server:/app

    environment:

      - REDIS_HOST=redis

      - REDIS_PORT=6379

      - PGUSER=postgres

      - PGHOST=postgres

      - PGDATABASE=postgres

      - PGPASSWORD=password_protected

      - PGPORT=5432

I have tried changing Postgres to postgres inside the Elasticbeanstalk environment variables but that has not resolved the issue. I am still getting error: password authentication failed for user "Postgres"

I then deleted RDS instance and provisioned a new with the same exact username and password, case sensitive and all. I added that RDS to the Security Group, I am still getting a 502 Bad Gateway with the same error of:

/var/log/containers/server-8b2907355681-stdouterr.log

-------------------------------------

> @ start /app

> node index.js



Listening

{ error: password authentication failed for user "Postgres"

    at Connection.parseE (/app/node_modules/pg/lib/connection.js:553:11)

    at Connection.parseMessage (/app/node_modules/pg/lib/connection.js:378:19)

    at Socket.<anonymous> (/app/node_modules/pg/lib/connection.js:119:22)

    at Socket.emit (events.js:189:13)

    at addChunk (_stream_readable.js:284:12)

    at readableAddChunk (_stream_readable.js:265:11)

    at Socket.Readable.push (_stream_readable.js:220:10)

    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

  name: 'error',

  length: 104,

  severity: 'FATAL',

  code: '28P01',

  detail: undefined,

  hint: undefined,

  position: undefined,

  internalPosition: undefined,

  internalQuery: undefined,

  where: undefined,

  schema: undefined,

  table: undefined,

  column: undefined,

  dataType: undefined,

  constraint: undefined,

  file: 'auth.c',

  line: '328',

  routine: 'auth_failed' }

I provisioned a new PostgreSQL RDS for the third time, ensured that all username and passwords were the same including case sensitive and eliminated any special characters and this time not only did I still get the same error, I also got this one:

-------------------------------------

/var/log/containers/server-09be251b359b-stdouterr.log

-------------------------------------

> @ start /app

> node index.js



Listening

{ Error: connect ETIMEDOUT 172.31.82.39:5432

    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)

  errno: 'ETIMEDOUT',

  code: 'ETIMEDOUT',

  syscall: 'connect',

  address: '172.31.82.39',

  port: 5432 }

I don't have much else to go on except a 502 Bad Gateway is coming from Nginx and I am wondering if the issue lies in my Nginx configuration. Inside my Nginx service I have the default.conf file:

upstream client {

    server client:3000;

}



upstream api {

    server api:5000;

}



server {

    listen 80;



    location / {

        proxy_pass http://client;

    }



    location /sockjs-node {

        proxy_pass http://client;

        proxy_http_version 1.1;

        proxy_set_header Upgrade $http_upgrade;

        proxy_set_header Connection "Upgrade";

    }



    location /api {

        rewrite /api/(.*) /$1 break;

        proxy_pass http://api;

    }

}

Is there anything about this that AWS RDS or EB does not like?