# Node.js build fails with no obvious error

**URL:** https://travis-ci.community/t/node-js-build-fails-with-no-obvious-error/961
**Category:** Windows
**Created:** [November 17, 2018, 4:39pm UTC](https://travis-ci.community/t/node-js-build-fails-with-no-obvious-error/961 "2018-11-17T16:39:56Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![hunterlester](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hunterlester/32/528_2.png) [@hunterlester](https://travis-ci.community/u/hunterlester)
#### Post date: [November 22, 2018, 7:15pm UTC](https://travis-ci.community/t/node-js-build-fails-with-no-obvious-error/961/2 "2018-11-22T19:15:09Z")

</div>

@michaelmior I had the same exact issue. Same as you I had an secure environment variable defined in settings: [https://travis-ci.org/hunterlester/safe\_browser/jobs/458529411](https://travis-ci.org/hunterlester/safe_browser/jobs/458529411)

 ![travis-build](https://us1.discourse-cdn.com/flex015/uploads/travis_ci/original/1X/87ee14e79218032585af026b16534590bc3aff7e.png)

Once I deleted the env var in my settings then the [build went on as usual](https://travis-ci.org/hunterlester/safe_browser/builds/458532591).  
Of course I’m unable to deploy to Github but at least it’s documented now.  
I’m able to set a non-secure env var though.

Hopefully Travis team is tracking these threads?

---

_[View the full topic](https://travis-ci.community/t/node-js-build-fails-with-no-obvious-error/961)._