Closed fliiteAI closed 4 years ago
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
Finally, remember to use https://discuss.ipfs.io if you just need general support.
Ongoing discussion in https://github.com/ipfs/go-ipfs/issues/874.
Let's keep tracking in ipfs/go-ipfs#874 ... I'll close this here for the sake of avoiding duplication. Thanks!
Out of the box install of IPFS will conflict with Cisco Anywhere Connect. In my particular case it was running on OSX Catalina. I had a standard install of the VPN software with not customizations. I downloaded IPFS Desktop and spent better part of a day tracking down why the daemon wouldn't start. On the enterprise front CISCO VPN software is pretty standard and this will get in the way of enterprise level deployments. I think the notifications should come front and center for non-computer science types so they understand they have a port conflict. YMMV