No CORS fields in response header in production

[AlexisSMT]

I faced this issue:

SSL issues with ForestAdmin

@kasro @feeleebaire It has just been fixed a few minutes ago Could you try again with the latest version of lumber? (v3.7.2) If you want to fix your actual project without re-running the install command, add this line to your .env file: DATABASE_REJECT_UNAUTHORIZED=false Then edit models/index.js (here): - databaseOptions.dialectOptions.ssl = true; + const rejectUnauthorized = process.env.DATABASE_REJECT_UNAUTHORIZED; + if (rejectUnauthorized && (JSON.parse(rejectUnauthorized.toLowerCase…

node-postgres

https://help.heroku.com/MDM23G46/why-am-i-getting-an-error-when-i-upgrade-to-pg-8

The node version used is 14.15.5. Here some of the build logs with the corresponding info:

-----> Building on the Heroku-18 stack
-----> Node.js app detected
       
-----> Creating runtime environment
       
       NPM_CONFIG_LOGLEVEL=error
       USE_YARN_CACHE=true
       NODE_ENV=production
       NODE_MODULES_CACHE=true
       NODE_VERBOSE=false
       
-----> Installing binaries
       engines.node (package.json):  unspecified
       engines.npm (package.json):   unspecified (use default)
       engines.yarn (package.json):  unspecified (use default)
       
       Resolving node version 14.x...
       Downloading and installing node 14.15.5...
       Using default npm version: 6.14.11
       Resolving yarn version 1.22.x...
       Downloading and installing yarn (1.22.10)
       Installed yarn 1.22.10