nconf | Hierarchical node.js configuration | Runtime Evironment library

From my limited as well experience so far with nginx, you need to add the following lines in the nginx default: ssl on; server_name your.domain.com; ssl_certificate /domain1/ssl-bundle.crt; ssl_certificate_key /domain1/server.key;

Also, in the default, you would need to add the location details for your nodejs server: location / { proxy_pass http://yourip:port/route; }

Lastly, I am not using certificates within my nodejs,it is an HTTP one, instead I let nginx handle those. The bundle.crt, contains both the rootca and public certificate as it is a self signed one in the above example.

It was solved by re-creating the dist folder with

npm run build

Thanks to @Dan for his help

Don't use apiClient. Do a get with the full url, rebuild your app, delete old dist folder, CTRL+F5 refresh once loaded. In fact, put a "?" on the end of the url and make sure you see it in Chrome headers

You need to res.setHeader('Access-Control-Allow-Origin', YourOrigin); in a middlewar before app.use(cors()); in order to allow the client.

EDIT :

You can do something like this :

If your build takes longer than 10m without output this will happen.

You can use travis_wait to print something to the console each minute, as per the docs: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

Just travis_wait {your_command} and you should be good to go.

Be aware that your build taking longer than 10m could be a indicator of a more complicated underlying problem/freeze.

Axios encodes the response body in utf8.
You should use other library like request.