Open danil-topchiy opened 5 years ago
Hi @matejak
This branch is based from #9
Having issue with testing federated cloud shares here: I've added new service to docker-compose with one more nextcloud instance to make federated cloudshare with it, but when I send request to nextcloud to make federated cloudshare it responds with
'Sharing Documents failed, could not find admin@app2:80, maybe the server is currently unreachable or uses a self-signed certificate.'
I think because nextcloud cannot resolve app2 domain(even though container by itself does resolve each others domain with ping for example).
Could you, please, have a look at this and may be you know a way how to get around it?
Sure, the problem that you face is interesting I will take a look into it and probably simplify the docker-compose.yml
too while I am at it.
I am able to reproduce your issue, and I was not able to find a solution. Technically it is possible that the http connection is the problem, but that is somewhat unlikely. While it is possible to debug the issue e.g. by examining outgoing connections on app
and incoming connections on app2
, it is too much work for a feature that is not a priority for the foreseeable future. Therefore, I propose to leave it open with the blocked
label, and focus resources on those other PRs.
Good job nailing the issue though!
Agree, thanks for investigating it!
Federated cloud shares fixes, tests, docs