You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
---
# The bare domain name which represents your Matrix identity.# Matrix user ids for your server will be of the form (`@user:<matrix-domain>`).## Note: this playbook does not touch the server referenced here.# Installation happens on another server ("matrix.<matrix-domain>").## If you've deployed using the wrong domain, you'll have to run the Uninstalling step,# because you can't change the Domain after deployment.## Example value: example.commatrix_domain: xxx# The Matrix homeserver software to install.# See:# - `roles/custom/matrix-base/defaults/main.yml` for valid options# - the `docs/configuring-playbook-IMPLEMENTATION_NAME.md` documentation page, if one is available for your implementation choicematrix_homeserver_implementation: synapse# A secret used as a base, for generating various other secrets.# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).matrix_homeserver_generic_secret_key: 'xxx'# By default, the playbook manages its own Traefik (https://doc.traefik.io/traefik/) reverse-proxy server.# It will retrieve SSL certificates for you on-demand and forward requests to all other components.# For alternatives, see `docs/configuring-playbook-own-webserver.md`.matrix_playbook_reverse_proxy_type: playbook-managed-traefik# This is something which is provided to Let's Encrypt when retrieving SSL certificates for domains.## In case SSL renewal fails at some point, you'll also get an email notification there.## If you decide to use another method for managing SSL certificates (different than the default Let's Encrypt),# you won't be required to define this variable (see `docs/configuring-playbook-ssl-certificates.md`).## Example value: someone@example.comdevture_traefik_config_certificatesResolvers_acme_email: 'xxx'# A Postgres password to use for the superuser Postgres user (called `matrix` by default).## The playbook creates additional Postgres users and databases (one for each enabled service)# using this superuser account.devture_postgres_connection_password: 'xxx'# By default, we configure Coturn's external IP address using the value specified for `ansible_host` in your `inventory/hosts` file.# If this value is an external IP address, you can skip this section.## If `ansible_host` is not the server's external IP address, you have 2 choices:# 1. Uncomment the line below, to allow IP address auto-detection to happen (more on this below)# 2. Uncomment and adjust the line below to specify an IP address manually## By default, auto-detection will be attempted using the `https://ifconfig.co/json` API.# Default values for this are specified in `matrix_coturn_turn_external_ip_address_auto_detection_*` variables in the Coturn role# (see `roles/custom/matrix-coturn/defaults/main.yml`).## If your server has multiple IP addresses, you may define them in another variable which allows a list of addresses.# Example: `matrix_coturn_turn_external_ip_addresses: ['1.2.3.4', '4.5.6.7']`## matrix_coturn_turn_external_ip_address: ''#### ADDED CONFIG### Storing Synapse media files on Amazon S3 or another compatible Object Storage### https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-s3.md### https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-synapse-s3-storage-provider.mdmatrix_synapse_ext_synapse_s3_storage_provider_enabled: truematrix_synapse_ext_synapse_s3_storage_provider_config_bucket: xxxmatrix_synapse_ext_synapse_s3_storage_provider_config_region_name: eu-central-1 # e.g. eu-central-1matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url: https://s3.eu-central-1.amazonaws.com # adjust thismatrix_synapse_ext_synapse_s3_storage_provider_config_storage_class: STANDARD # or STANDARD_IA, etc.# Authentication Method 1 - (access key id + secret)# This works on all providers (AWS and other compatible systems).# Uncomment the variables below to use it.matrix_synapse_ext_synapse_s3_storage_provider_config_access_key_id: xxxmatrix_synapse_ext_synapse_s3_storage_provider_config_secret_access_key: xxx# Authentication Method 2 - EC2 instance profile which grants permission to access S3# This only works on AWS when your server is hosted on an EC2 instance with the correct instance profile set.# Uncomment the variable below to use it.# matrix_synapse_ext_synapse_s3_storage_provider_config_ec2_instance_profile: true# For additional advanced settings, take a look at `roles/custom/matrix-synapse/defaults/main.yml`### Serving the base domain### https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-base-domain-serving.mdmatrix_static_files_container_labels_base_domain_enabled: true# Prevent the default index.html file from being installedmatrix_static_files_file_index_html_enabled: false# Disable the automatic redirectin of `https://DOMAIN/` to `https://matrix.DOMAIN/`.# This gets automatically enabled when you disable `matrix_static_files_file_index_html_enabled`, as we're doing above.matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false### Adjusting ma1sd Identity Server configuration### https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-ma1sd.mdmatrix_ma1sd_enabled: true#### Setting up BOTS#### https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook.md#bots### Setting up matrix-registration-bot### https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-bot-matrix-registration-bot.mdmatrix_bot_matrix_registration_bot_enabled: true# By default, the playbook will set use the bot with a username like this: `@bot.matrix-registration-bot:DOMAIN`.# To use a different username, uncomment & adjust the variable below:# matrix_bot_matrix_registration_bot_matrix_user_id_localpart: bot.matrix-registration-bot# Generate a strong password here. Consider generating it with `pwgen -s 64 1`matrix_bot_matrix_registration_bot_bot_password: xxx# Enables registrationmatrix_synapse_enable_registration: true# Restrict registration to users with a tokenmatrix_synapse_registration_requires_token: true# Matrix registration bot is failing because of timeoutdevture_systemd_service_manager_up_verification_delay_seconds: 90
Matrix Server:
OS: centos
Architecture amd64
Problem description:
After setting up matrix registration bot I get these errors:
Playbook Configuration:
My
vars.yml
file looks like this:Matrix Server:
Problem description:
After setting up matrix registration bot I get these errors:
user: list
bot.matrix-registration-bot: The bot encountered the following error:
The registration api returned 404: Not Found for GET: https://matrix.xxx/_synapse/admin/v1/registration_tokens
user: create
bot.matrix-registration-bot: The bot encountered the following error:
Token not found or API not reachable (404 Not Found)
Can you please help understanding what I'm doing wrong?
The text was updated successfully, but these errors were encountered: