[X] I have searched the existing issues and didn't find any that were similar
[X] I have considered creating a pull request with fixes instead of a bug report and want to proceed
Current Behavior
On a brand new deployment (no preexisting volumes) + make start, on a brand new vault after uploading the new client.yml, no server communication succeeds :
apply the diff provided in "anything else" (which basically shouldn't modify anything critical ? and worked before 5.X branch
make start
update client.yml accordingly
create a new vault
?
Don't profit
Environment
# Hosting node :
- OS: Debian Bullseye (11)
- Version: Linux tooling 5.10.0-23-amd64 #1 SMP Debian 5.10.179-3 (2023-07-27) x86_64 GNU/Linux
- docker version :
Client: Docker Engine - Community
Version: 24.0.5
API version: 1.43
Go version: go1.20.6
Git commit: ced0996
Built: Fri Jul 21 20:35:45 2023
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 24.0.5
API version: 1.43 (minimum version 1.12)
Go version: go1.20.6
Git commit: a61e2b4
Built: Fri Jul 21 20:35:45 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.22
GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca
runc:
Version: 1.1.8
GitCommit: v1.1.8-0-g82f18fe
docker-init:
Version: 0.19.0
GitCommit: de40ad0
- Docker compose version : v2.20.2
# Client machine
OS version: linux x64 6.10.2-arch1-1
App version: 0.42.0
Build number: build on 2024-07-31 08:28:58 +0000 UTC at #4a8c39e4e991d3e9d6819f5ff495c688415bc288
Library version: v0.35.0-rc12
Anytype Identity: A7CoWMYx1Z4NWf9uUE9M71kVPVMgJiZKVW761WBSi4cvwyud
Analytics ID: f2ad75ad-428c-402f-9f70-e97024008e9e
Device ID: 12D3KooWFFZNwuHGQ7pWzZFWAqhZcyXVzvo1vyg9hygJmDFfmEa2
Anything else?
On branch main
Your branch is up to date with 'origin/main'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: .env.override.latest
modified: docker-compose.yml
Untracked files:
(use "git add <file>..." to include in what will be committed)
any-sync-node-1/
any-sync-node-2/
any-sync-node-3/
docker-generateconfig/.networkId
docker-generateconfig/.networkSigningKey
docker-generateconfig/account.yml
docker-generateconfig/account0.yml
docker-generateconfig/account1.yml
docker-generateconfig/account2.yml
docker-generateconfig/account3.yml
docker-generateconfig/account4.yml
docker-generateconfig/account5.yml
docker-generateconfig/network.yml
docker-generateconfig/nodes.yml
docker-generateconfig/nodesProcessed.yml
minio/
mongo-1/
networkStore/
redis/
Have you read a contributing guide?
Current Behavior
On a brand new deployment (no preexisting volumes) + make start, on a brand new vault after uploading the new client.yml, no server communication succeeds :
And here's a relevant log excerpt :
Expected Behavior
For my vaults to sync
Steps To Reproduce
Environment
Anything else?
Thanks for the great app (latest updates are rad !)