-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MatchingServerName #3116
Comments
|
Right but Installation happens on another server "matrix. matrix-domain". doesn't that mean this field should just have the domain after matrix and not the full matrix.domain? |
Yes you set But you don't appear to have finished the installation process. For federation to work, you still must complete https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-well-known.md (which is step 3 here: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/installing.md#3-finalize-the-installation). |
Playbook Configuration:
My
vars.yml
file looks like this:Matrix Server:
Ansible:
If your problem appears to be with Ansible, tell us:
-version 2.16
Problem description:
Receiving a MatchingServerName error on https://federationtester.matrix.org/#matrix.darktundra.xyz
looking in /matrix/synapse/config/homeserver.yaml
config: null
server_name: darktundra.xyz
signing_key_path: /data/matrix.darktundra.xyz.signing.key
Describe what you're doing, what you expect to happen and what happens instead here.
I am not sure where it is getting that from as the onlything that is not matrix.darktundra.xyz in the config is for matrix_domain
The text was updated successfully, but these errors were encountered: