20260212085050

Running test_matrix.py, I see that

$ python3 test_matrix.py tsuki.games

Testing server tsuki.games
  Federation url: https://matrix.tsuki.games:443
✔ Server well-known exists
𐄂 Client well-known redirect #1 has no CORS header
✔ Client well-known has proper CORS header
  Client url: https://matrix.tsuki.games/
✔ Server version: Tuwunel (1.5.0)
✔ Federation API endpoints seem to work fine
✔ Client API endpoints seem to work fine
  QR code login is disabled (MSC 4108)
  Public room directory is disabled
  No MatrixRTC SFU configured
✔ Direct registration and guest access forbidden per se 👍

I confirmed that "redirect #1" is referring to https://www.tsuki.games/.well-known which redirects to https://matrix.tsuki.games/.well-known which is missing CORS headers and that matrix.tsuki.games already has the CORS headers set correctly.

I try to update the .htaccess file...

 Redirect 301 /.well-known https://matrix.tsuki.games/.well-known
+Header always add Access-Control-Allow-Origin: "*"

...and curl reports that the Access-Control-Allow-Origin header is now set...

$ curl -I https://www.tsuki.games/.well-known/matrix/server
HTTP/2 301
date: Thu, 12 Feb 2026 09:02:42 GMT
server: Apache
access-control-allow-origin: *
location: https://matrix.tsuki.games/.well-known/matrix/server
age: 530
via: e7s
content-type: text/html; charset=iso-8859-1

...but test_matrix.py still complains:

python3 test_matrix.py tsuki.games
Testing server tsuki.games
  Federation url: https://matrix.tsuki.games:443
✔ Server well-known exists
𐄂 Client well-known redirect #1 has no CORS header
✔ Client well-known has proper CORS header
  Client url: https://matrix.tsuki.games/
✔ Server version: Tuwunel (1.5.0)
✔ Federation API endpoints seem to work fine
✔ Client API endpoints seem to work fine
  QR code login is disabled (MSC 4108)
  Public room directory is disabled
  No MatrixRTC SFU configured
✔ Direct registration and guest access forbidden per se 👍

I'm not sure why this is. However, it seems like federation is working properly now, so I'm not sure this is actually a problem.

content

meta