Anyone gotten Element to work when deployed via elestio?
-
Wanted to test out some FOSS slack alternatives for a local ngo and element is a top choice. Deployed and followed the instructions in the email to set up:
- Added CNAME record in my domain registrar (google), and added to elestio per https://docs.elest.io/books/security/page/custom-domain-and-automated-encryption-ssltls
- Brought down the service with
docker-compose down
after SSHing in, and changed/opt/app/element-config.json
linesdefault_server_config.m.homeserver.base_url
tohttps://chat.example.com:8448
anddefault_server_config.m.homeserver.server_name
tochat.example.com
- Ran the following command:
docker run --rm -v "/opt/app/synapse:/data" -e SYNAPSE_SERVER_NAME=chat.example.com -e SYNAPSE_REPORT_STATS=yes matrixdotorg/synapse:latest generate
- Brought docker back up with
docker-compose up -d
However, the service is unfortunately unusable. At both the default elestio CNAME, and my custom one
chat.example.com
, I have the following error on the element web client login page:Can't connect to homeserver - please check your connectivity, ensure your homeserver's SSL certificate is trusted, and that a browser extension is not blocking requests. Cannot reach homeserver Ensure you have a stable internet connection, or get in touch with the server admin
With the
homeserver
correctly showingchat.example.com
Any tips?
-
Hey @caleb, would you mind opening a support ticket from our dashboard so we can investigate your instance?
-
@jbenguira sure thing, done!