[help] self hosting invite error "no valid providers in chain"

[bokchoi2020]

Hi guys, I've setup the self hosting docker image using the steps outlined in https://github.com/anyproto/any-sync-dockercompose/wiki/Configuration#running-as-a-non-privileged-user-only-for-linux. I am using RHEL10 to self host. On my client I am using AnyType version 0.50.5.

I've also whitelisted the right ports in the firewall.
sudo firewall-cmd --permanent --service=anytypeNotes --add-port=1001-1006/tcp --add-port=1011-1016/udp --add-port=9000-9001/tcp --add-port=27001/tcp --add-port=6379/tcp --add-port=8081-8083/tcp --add-port=8001-8006/tcp

On the client, I am able to import the client.yml and I can see that the sync is working (self hosted icon is green, files sync fine with checkmarks).

The problem I have now is that when I go to Invite members, and switch the invite link from Link disabled to Edit, I get this error:
store invite in ipfs: add data to IPFS: NoCredentialProviders: no valid providers in chain. Deprecated. For verbose messaging see aws.Config.CredentialsChainVerboseErrors, generate invite

In my .env.override I have:
UID=1000
GID=1000
EXTERNAL_LISTEN_HOST="192.168.0.x"
ANY_SYNC_NODE_VERSION=latest
ANY_SYNC_FILENODE_VERSION=latest
ANY_SYNC_COORDINATOR_VERSION=latest
ANY_SYNC_CONSENSUSNODE_VERSION=latest

I checked id -u and -g, it matches fine.

Is there anything I missed here? Thanks in advance.

[bokchoi2020]

I checked the docker logs for the any-sync-coordinator container. I see some more details, does anyone know? I redacted some of the id's, but I think the meaning should still be there.

Seems like I am having some kind of connection error between the client and the coordinator?

2025-11-06T18:43:29.996Z DEBUG common.net.drpcserver drpc serve peer {"remoteAddr": "172.18.0.12:56686", "localAddr": "172.18.0.6:1004"}
2025-11-06T18:43:29.996Z INFO rpcLog {"totalDur": 0.000008088, "addr": "yamux://172.18.0.12:56686", "app": "v0.7.3", "peerId": "peer0", "identity": "id0", "rpc": "coordinator.networkConfiguration", "peerVersion": ":/any-sync:v0.10.1"}
2025-11-06T18:43:29.997Z INFO common.net.peer serve connection error {"error": "manager closed: EOF", "errorVerbose": "manager closed: EOF\n\tstorj.io/drpc/drpcmanager.(*Manager).manageReader:234"}
2025-11-06T18:43:39.855Z INFO coordinator.acl GC: removed 0; cache size: 0
2025-11-06T18:43:40.068Z DEBUG common.net.drpcserver drpc serve peer {"remoteAddr": "172.18.0.12:56380", "localAddr": "172.18.0.6:1004"}
2025-11-06T18:43:40.068Z INFO rpcLog {"totalDur": 0.000004447, "addr": "yamux://172.18.0.12:56380", "app": "v0.7.3", "peerId": "peer1", "identity": "id1", "rpc": "coordinator.networkConfiguration", "peerVersion": ":/any-sync:v0.10.1"}
2025-11-06T18:43:40.068Z INFO common.net.peer serve connection error {"error": "manager closed: EOF", "errorVerbose": "manager closed: EOF\n\tstorj.io/drpc/drpcmanager.(*Manager).manageReader:234"}
2025-11-06T18:43:40.852Z INFO rpcLog {"totalDur": 0.000691313, "addr": "yamux://172.18.0.11:35958", "app": "v0.7.3", "peerId": "peer2", "identity": "id2", "rpc": "coordinator.deletionLog", "peerVersion": "any-sync-filenode:v0.9.2/any-sync:v0.10.3"}
2025-11-06T18:43:44.392Z INFO rpcLog {"totalDur": 0.007965649, "addr": "quic://client-ip:59262", "spaceId": "spaceid.14t9f26ldovr3", "app": "v0.7.3", "peerId": "id", "identity": "id", "rpc": "coordinator.spaceMakeShareable", "peerVersion": "Linux:0.50.5/middle:v0.44.5/any-sync:v0.10.2"}
2025-11-06T18:43:50.132Z DEBUG common.net.drpcserver drpc serve peer {"remoteAddr": "172.18.0.12:55752", "localAddr": "172.18.0.6:1004"}
2025-11-06T18:43:50.133Z INFO rpcLog {"totalDur": 0.000003454, "addr": "yamux://172.18.0.12:55752", "app": "v0.7.3", "peerId": "peer3", "identity": "id3", "rpc": "coordinator.networkConfiguration", "peerVersion": ":/any-sync:v0.10.1"}
2025-11-06T18:43:50.133Z INFO common.net.peer serve connection error {"error": "manager closed: EOF", "errorVerbose": "manager closed: EOF\n\tstorj.io/drpc/drpcmanager.(*Manager).manageReader:234"}
2025-11-06T18:43:57.049Z INFO rpcLog {"totalDur": 12.607341934, "addr": "quic://client-ip:59262", "error": "NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors", "errorVerbose": "NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:230\n\tstorj.io/drpc/drpcmanager.(*Manager).manageReader:250", "app": "v0.7.3", "peerId": "peer4", "identity": "id4", "rpc": "coordinator.aclUploadInvite", "peerVersion": "Linux:0.50.5/middle:v0.44.5/any-sync:v0.10.2"}

[bokchoi2020]

What it looks like

[tribals]

I believe the problem is that any-sync-filenode didn't get S3 credentials. Just got the same error and seemed like AWS credentials from environment is not picked up. I placed them in ~/.aws/credentials and this solved that particular problem but now I got another one: "Oops, something went wrong. Check network connection" but I'm absolutely sure network connectivity is fine.