Access by federation doesn't work

[dumprop]

Describe the bug

Access by federation doesn't work in both sides

Context

• Hardware: VPS bought online
• YunoHost version: 4.2.8.3
• I have access to my server: Through SSH | through the webadmin
• Using, or trying to install package version/branch: latest main

Steps to reproduce

install synapse server on sub.domain.tld (in fact my root domain is sub.domain.tld, so synapse installed on synapse.sub.domain.tld)

Expected behavior

Access by federation

If applicable and useful, add screenshots to help explain your problem. Report for sub.domain.tld

Report for domain.tld

Element

So, for passing all checks there should be root domain for synapse (currently there only subdomain)

UPD: I installed on root domain (domain.tld and created user on that), it passes all checks and works correctly (element works fine)

[PxBCPG]

Do you have Cloudflare ?

[dumprop]

Do you have Cloudflare ?

No, but I use cloudflare as a nameserver

[PxBCPG]

I got the same problem using cloudflare, now I deactivated the proxy for the synapse server and it works :)

[dumprop]

YNH on domain.tld and Synapse on sub.domain.tld (domain.tld for usernames) - OK YNH on sub1.domain.tld and Synapse on sub2.domain.tld (domain.tld for usernames) - NO "A" record for domain.tld is another (not YNH related), that's problem I hope it will be fixed with 4.3 (using registrars API)

Currently I did a trick: temporary changed @ to YNH address and installed valid certificates So that problem when ynh installed on sub domain, synapse on sub sub domain and main domain is not ynh related :)

[Josue-T]

I think in these cases like that you might need to add some manual DNS registry to work correctly.

[Josue-T]

Closing as inactive