Troubleshooting, work arounds, and known issues.

Unable to connect to the Fission IPFS peer

🛰 Unable to connect to the Fission IPFS peer, trying again...
🛰 Unable to connect to the Fission IPFS peer, trying again...
😭 We were unable to connect to the Fission IPFS peer!
Try checking your connection or logging in again

This message most often appears when your local IPFS server isn't running, or if you're offline. Turn on your IPFS Desktop, run ipfs daemon &, or whatever method you're using to run IPFS.

Maximum Open Files on Ubuntu, Mac OS, ChromeOS

We've had a report with uploading large numbers of files using ipfs-deploy with Fission support that you may need to increase the number of open files that your operating system supports. This could also occur with fission watch.

For ubuntu, read underyx's article to increase the number of open files allowed.

For Mac OS, Wilson Mar has a one liner:

sudo launchctl limit maxfiles 65536 200000

As described in the article, you'll want to add it to your bash or other shell profile so this change is permanent.

On a Chromebook in the native ChromeOS shell? Yeah, Boris hit this issue too when running large jekyll or gatsby builds:

sudo sysctl fs.inotify.max_user_watches=1048576

Re-installing brew on Mac

We've had some hiccups with our brew formula recently. To re-install / reset brew, run the following:

brew untap fission-suite/fission

Now re-run the installation instructions, copied here for convenience:

brew tap fission-suite/fission
brew install fission-cli

This is related to issue #37.

DEBUG mode for fission cli

If you want to see what the Fission CLI is doing under the covers, you can turn on DEBUG mode by calling commands like this:

DEBUG=true fission up .

You'll see that fission up calls your locally installed ipfs command to add files to IPFS. We can see that it's using the 0.4.22 version of ipfs, installed using Homebrew in the "Cellar" where brew keeps installed items.

Then, it sends the hash of the entire directory to our web API, which pins it and fetches the files directly from your laptop and any other IPFS nodes that already have copies of those files in the network.

In this case, we can see that after the "Remote pinning Qm…", there is a 504 Gateway Time-out error from our server. This is a known issue, which we're working on to support large files / large quantities of files.

Running IPFS as a service on Linux and WSL

WSL doesn't have systemd, so this init.d script should work. Place the script in your init.d folder and then run /etc/init.d/ipfs start/status/stop to control the IPFS daemon.