# Setting DontCheckOSXFUSE true does not seem to work

**URL:** <https://discuss.ipfs.tech/t/setting-dontcheckosxfuse-true-does-not-seem-to-work/498>\
**Category:** Help\
**Created:** [May 23, 2017, 8:29pm UTC](https://discuss.ipfs.tech/t/setting-dontcheckosxfuse-true-does-not-seem-to-work/498 "2017-05-23T20:29:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [May 23, 2017, 8:29pm UTC](https://discuss.ipfs.tech/t/setting-dontcheckosxfuse-true-does-not-seem-to-work/498/1 "2017-05-23T20:29:13Z")

</div>

_From @DavidBooher on Wed Jan 27 2016 00:44:43 GMT+0000 (UTC)_  
  
Version: 0.3.10  
Fuse: 2.8.3

jimbo:.ipfs dbooher$ ipfs config DontCheckOSXFUSE true  
jimbo:.ipfs dbooher$ ipfs daemon --mount  
Initializing daemon…  
Swarm listening on /ip4/127.0.0.1/tcp/4001  
Swarm listening on /ip4/127.0.0.1/tcp/4001  
Swarm listening on /ip4/172.16.144.1/tcp/4001  
Swarm listening on /ip4/172.16.144.1/tcp/4001  
Swarm listening on /ip4/192.168.22.200/tcp/4001  
Swarm listening on /ip4/192.168.22.200/tcp/4001  
Swarm listening on /ip4/192.168.89.1/tcp/4001  
Swarm listening on /ip4/192.168.89.1/tcp/4001  
Swarm listening on /ip4/73.44.241.86/tcp/15950  
Swarm listening on /ip4/73.44.241.86/tcp/64096  
API server listening on /ip4/127.0.0.1/tcp/5001  
Gateway (readonly) server listening on /ip4/127.0.0.1/tcp/8080  
18:37:36.343 ERROR swarm2: swarm listener accept error: peerstream listener failed: accept tcp 0.0.0.0:4001: use of closed network connection swarm\_listen.go:129  
18:37:36.343 ERROR swarm2: swarm listener accept error: peerstream listener failed: accept tcp 0.0.0.0:4001: use of closed network connection swarm\_listen.go:129  
Error: config key invalid: DontCheckOSXFUSE %!s(bool=true)  
You may be able to get this error to go away by setting it again:

```auto
ipfs config DontCheckOSXFUSE true

```

Either way, please tell us at: [GitHub · Where software is built](http://github.com/ipfs/go-ipfs/issues)

jimbo:bin dbooher$ ipfs config DontCheckOSXFUSE true  
Error: Failed to set config value: Wrong config type, expected bool (maybe use --json?)  
jimbo:bin dbooher$  
  
  
_Copied from original issue: [Setting DontCheckOSXFUSE true does not seem to work · Issue #18 · ipfs-inactive/support · GitHub](https://github.com/ipfs/support/issues/18)_

---

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [May 23, 2017, 8:29pm UTC](https://discuss.ipfs.tech/t/setting-dontcheckosxfuse-true-does-not-seem-to-work/498/2 "2017-05-23T20:29:20Z")

</div>

_From @RichardLitt on Thu Mar 10 2016 18:33:16 GMT+0000 (UTC)_  
  
I am not sure what is going on here. Ping @whyrusleeping.

---

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [May 23, 2017, 8:29pm UTC](https://discuss.ipfs.tech/t/setting-dontcheckosxfuse-true-does-not-seem-to-work/498/3 "2017-05-23T20:29:23Z")

</div>

_From @frerepoulet on Mon Apr 25 2016 14:27:54 GMT+0000 (UTC)_  
  
fyi: having the same issue on Mac OS X 10.11.4, ipfs 0.4.0 installed via `brew install ipfs`

---

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [May 23, 2017, 8:29pm UTC](https://discuss.ipfs.tech/t/setting-dontcheckosxfuse-true-does-not-seem-to-work/498/4 "2017-05-23T20:29:25Z")

</div>

_From @whyrusleeping on Mon Apr 25 2016 18:19:48 GMT+0000 (UTC)_  
  
hrm… thats very strange. Try running:

```auto
ipfs config --json DontCheckOSXFUSE true

```

Theres obviously a bug in the checking code, but that should at least correctly set the config var
