My bad I had replied to two people who had asked for it. I didn’t know how to format it so I had fixed it once, but I will delete it and try to add it to the main post.
EDIT: hopefully that is better to look at!
- 7 Posts
- 32 Comments
Joined 6 months ago
Cake day: July 8th, 2024
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Please explain how I am spamming when my last post in this community was 3 days ago?
I find this resource very helpful, I am trying to learn.
My bad it is now fixed
I set it up multiple different times in different locations:
/home/inventory/host_vars/matrix.bishbash.com
/home/inventory/hosts
/home/matrix-docker-ansible-deploy/inventory/host_vars/
/Home/matrix-docker-ansible-deploy/inventory/hosts
/desktop/ansible playbook/matrix-docker-ansible-deploy/inventory/host_vars
/desktop/ansible playbook/matrix-docker-ansible-deploy/inventory/hosts
deleted by creator
‘’’ —
The bare domain name which represents your Matrix identity.
Matrix user IDs for your server will be of the form (
@alice:example.com).Note: this playbook does not touch the server referenced here.
Installation happens on another server (“matrix.example.com”, see
matrix_server_fqn_matrix).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.
matrix_domain: matrix.bishbash.com
The Matrix homeserver software to install.
See:
-
roles/custom/matrix-base/defaults/main.ymlfor valid options- the
docs/configuring-playbook-IMPLEMENTATION_NAME.mddocumentation page, if one is available for your implementation choiceBy default, we use Synapse, because it’s the only full-featured Matrix server at the moment.
Note that the homeserver implementation of a server will not be able to be changed without data loss.
matrix_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: ‘I_put_my_actual_key_here’
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: [email protected]
traefik_config_certificatesResolvers_acme_email: ‘’
A Postgres password to use for the superuser Postgres user (called
matrixby default).The playbook creates additional Postgres users and databases (one for each enabled service)
using this superuser account.
postgres_connection_password: ‘I_made_a_password_here’
By default, we configure Coturn’s external IP address using the value specified for
ansible_hostin yourinventory/hostsfile.If this value is an external IP address, you can skip this section.
If
ansible_hostis 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/jsonAPI.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: ‘’. ‘’’
deleted by creator
3·8 days agoYes because when someone else’s suffering is worse it means your suffering is invalid. By that nature no one should ever bring up their trials and tribulations because someone always has it worse.
No I was deploying regular conduit. Now I am trying conduwuit and when I try and connect it says it doesn’t support sliding sync. I cannot seems to find it referenced in the config file either.
EDIT: nvm I just read it is not implemented yet on conduwuit. 🥲 kind of a dealbreaker because I am trying to get element x working for group calling.
Its a joke, in that clip he says “two steps ahead, I am always two steps ahead” it was viral for a while.
1·14 days agoI just installed ntfy and am going to give that a go for a while and report back!
So sorry my bad!
The device that struggles with push notifications is a pixel 8 with GrapheneOS. Element was installed through f droid.
Also another problem that I have been facing is I cannot multitask while in a call otherwise it cuts my microphone. I have to stay in app to be able to talk with the person I am in the call with.
Notifications work just fine on my desktop running arch.
I will update the post with this information.
Holy. Fuck. You just did it. You absolute madlad. It works no issues!!!
Thank you!!
Just barely fixed that! Thanks! I have another issue thst I fommented about though:
Progress has been made!
So I got it working with the domain name. The turn testing tools now respond with relay and pin point the vps server! Nice!
However when I put the info into the matrix dendrite.yaml it still crashes. The logs say
“Invalid config file: yaml: line 210: did not find expected key”
“Invalid config file: yaml: line 206: did not find expected " - " indicator”
Line 210 and 206 refer to the turn section which is formatted:
turn: turn_user_lifetime: “5m” turn_uris: - turn:turn.exampledomain.com?transport=udp - turn:turn.exampledomain.com?transport=tcp
turn_username: user turn_password: password
Progress has been made!
So I got it working with the domain name. The turn testing tools now respond with relay and pin point the vps server! Nice!
However when I put the info into the matrix dendrite.yaml it still crashes. The logs say
“Invalid config file: yaml: line 210: did not find expected key”
“Invalid config file: yaml: line 206: did not find expected " - " indicator”
Line 210 and 206 refer to the turn section which is formatted:
turn: turn_user_lifetime: “5m” turn_uris: - turn:turn.exampledomain.com?transport=udp - turn:turn.exampledomain.com?transport=tcp
turn_username: user turn_password: passwordEDIT: line 206 seems to be
- turn:turn.exampledomain.com?transport=tcp
And line 210 is uncommented description so I don’t know what that is about
I did fill that out, anytime I do matrix crashes and I think the logs say something along the lines of not being able to find the turn server. I just tried it now with the vps ip and port and it still caused matrix to crash.
The turn tesying tools don’t work with the URI at all its only the ip and port they work with.
When I use the dig A command it gives me different ips than the vps ip.
Sorry I jusy recently updated my comment. I was able to get it to say “relay” when using the regular public ip and port for my vps. It doesn’t work if I use the domain I created for it though “turn.domainexample.com”
The domain name should be pointed to the vps public ip type A
Paid subscription? No I only have the cloudflare domain and the vps subscription. Do I need the subscription to get this working? 😮💨
Or is there another solution?
I am not dead set on using ansible that is just the top recommendation I was recieving purely based off of how much documentation there is for it. That and iy sets up element chat for you which is what I really needed. That and postgres database. This seems a lot closer to my tempo and I will totally try to get it running! Thank you!