IPFS: failed to listen on any address

Describe the bug

can’t run service ‘ipfs’: failed to listen on any addresses: [listen tcp4 0.0.0.0:63437: bind: An attempt was made to access a socket in a way forbidden by its access permissions.]

To Reproduce

Steps to reproduce the behavior:

Ran Anytype, updated to the latest version when prompted. It worked fine. But when I open it again. I get the following error.

Expected behavior

Any type should have loaded and landed on the main page

Desktop (please complete the following information):

  • OS: Windows 10 21H1
  • OS Build: Microsoft Windows [Version 10.0.19043.1110]
  • Device: Desktop
  • Version: AnyType 0.18.54

Additional context

Last time I fixed this by delete the AnyType2 working folder and resyncing from cloud.

1 Like

I logged back in and now its saying migrating profile.

@InimitableMind The message comes on the linux desktop app too, but after a minute the app opens up for me. Is Anytype working for you now?

I also have the same error, only difference is my Windows build is: 19042.1110

I’m also offered to log in after acknowledging the error, however it doesn’t move past Migration in progress. It can take up to 5 minutes....

I waited a long time. It never moved past Migration in progress view.

I simply deleted the working folder AnyType2 and resync from cloud using the key.

I had the same problem today. Removing the working directory and signing in again ‘solved’ it.

I have no clue why, but I seem to have this problem quite often. Yesterday I got this error, and today again. The only solution seems to be to completely remove the working directory and syncing it again.

It’s still happening for me in version 0.18.59.

If I remove the data sub folder and log back in, it works for a little while.

If I remove the Anytype2 main folder and log back in, it works until there is a new version release.

Describe the bug

Getting this error when i try to open anytype.

Error:

can’t run service ‘ipfs’: failed to listen on any addresses: [listen tcp4 0.0.0.0:13540: bind: An attempt was made to access a socket in a way forbidden by its access permissions.]

Desktop (please complete the following information):

  • OS: Windows 10
  • Device: Laptop
  • Version: 0.18.57

@starman-- please refer to this article.

https://community.anytype.io/t/-/1559

1 Like

@div3xi Thank you

@InimitableMind I’m still having this problem too. It happens very frequently. This is what my Roaming folder is starting to look like:

@daanl this is new, please create a new bug report as this type of Roaming folder has not been seen.

@div3xi No this is not a bug. I rename the anytype2 folder manually whenever the above problem occurs. The actual bug is that signing into Anytype is not possible quite often, as you can see by looking at the modified dates of all of these folders.

@daanl I thought anytype was doing this and i did see the modification date. I assumed you tried re-installing several time.

1 Like

@div3xi Oh I see! Yeah no, that’s me trying to make sure I don’t lose data if anything would go wrong :stuck_out_tongue:

1 Like

Was this solved for you?