Hey all, I decided to try setting up matrix/synapse via cloudflare tunnels.
I was following this guide
http://192.168.1.2:8009/_matrix/static/ shows
It works! Synapse is running
as does https://matrix.example.com/_matrix/static/
https://matrix.example.com/.well-known/matrix/server
comes up with 404. Is anything ever truly *well* known?
and matrix/synapse container shows 401 unauthorized when trying to access public rooms
synapse.http.matrixfederationclient - 676 - INFO - POST-87644 - {POST-O-3}
federation tester is showing
Hosts
_dc-srv.959fd81029a5._matrix._tcp.matrix.example.com.
Addresses
Errors
SRV record target _dc-srv.959fd81029a5._matrix._tcp.matrix.example.com. is a CNAME record, which is forbidden (as per RFC2782)
can anyone point me in the right direction?
I’m assuming this is still an issue with ./well-known or something.
cheers
How exactly is your Matrix server running? Behind an nginx reverse proxy or are you using the cloudflare tunnel directly to it? Personally, I have mine behind a reverse proxy and just point the tunnel at my proxy.
Since I just migrated to cf tunnels I set it up to directly point to my matrix instance. I was planning on implementing the rproxy back in once I got it working.
My old setup was way over convoluted with a double reverse proxy, ec2 instance, and vpn lmao.
So, my setup is this: Nginx reverse proxy using LE wildcard certs for my domain. I put my Matrix on a subdomain on my domain. Then I just point the CF tunnel to the reverse proxy using the subdomain for my public hostname. Everything works for me. Federation, local chat, etc. I have Home Assistant notifying me via Matrix now too.
To add more, I think you’re right in suspecting your ./well-known setting. I’m not sure where you would set that in a direct to Matrix setup like you have but it’s pretty easy using nginx. I just ran mine through the federation checker and my hosts section came back as exactly what I set in my location /.well-known/matrix/server directive in my nginx config.