fix: try with a different port

[daviddias]

No description provided.

[victorb]

👎 not a proper fix as this might break in the future too. We cannot make assumptions about free ports (but I bet you already knew this). As mentioned elsewhere, I'm working on fixing this right now.

[daviddias]

@victorbjelkholm I'm testing you hypothesis from #206 (comment)

I claim that it isn't the port but rather the server that is not being closed properly. Making the port random generated would just hide the problem for now, but it would create issues for users.

[daviddias]

Alright, seems that indeed Mac OS uses port 9999 for something, so the server is being closed properly.

👌🏽

[victorb]

Making the port random generated would just hide the problem for now, but it would create issues for users

The fix I'm working on doesn't involve ipfsd-ctl at all, just how ipfs/js-ipfs is using it.

[dryajov]

I say we change the port to something else - the one here seems reasonable, 9999 seems too common and super easy to clash with. @diasdavid lets get this merged?

[victorb]

Silly but 4737 would mean IPFS on a T9 keyboard (and US phonenumbers somehow?). Would be a good port and easy to remember if you used to send sms's a couple of years ago 🎉

[daviddias]

#211

[daviddias]

@victorbjelkholm that one would be good for the ipfs daemon default listening port :)