anyproto / anyproto/anytype-cli
Error acceptor xyz is not the network key in v0.2.1 (v0.2.0 works)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 134
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Have you read a contributing guide?
- I have read CONTRIBUTING.md
- I have searched the existing issues and didn't find any that were similar
- I have considered creating a pull request with fixes instead of a bug report and want to proceed
Current Behavior
Hi, I use the latest version of the cli v0.2.1 andsee the following error. I noticed it because I can not get all spaces via the cli anymore. The log is seen short after the start of the container.
Error:
{"level":"ERROR","ts":"2026-04-29T08:22:55.774Z","logger":"app","msg":"can't init service","service":"common.acl.syncacl","error":"acceptor xyz is not the network key"}
Expected Behavior
The /v1/spaces Endpoint should get all spaces which the api key has access to
Steps To Reproduce
- Update to the latest docker image
- try to get all spaces from the /v1/spaces
Environment
- OS: ubuntu (kubernetes)
- Version: v0.2.1
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the v0.2.1 Docker image and compare it with v0.2.0. Trace initialization of the service producing “acceptor xyz is not the network key” while requesting /v1/spaces. Done means the endpoint returns all spaces accessible to the API key without the startup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100