hope.net homeserver problems

[half-duplex]

Tracking issue for problems with the hope.net homeserver, not bot-related.

Element desktop reports that hope.net is not a valid homeserver

Dev tools shows a request to https://hope.net/.well-known/matrix/client fails because of CORS. Requests to that URL get a 302 that doesn't have an access-control-allow-origin header, pointing to the same path on www.hope.net which does. Reported, unfixed.

Invite/sync Problems

During HOPE26, several users on other homeservers were able to redeem their tokens but were unable to actually be invited to the space. Other non-HOPE homeservers worked.

hope.ems.host: Synapse 1.158.0+pro.1

• Broken: heretic.li, continuwuity 26.8.0-alpha.1 (a148174)
• Broken: rue.nabulator.com, continuwuity 26.7.3 (6957ff7)
• Broken: theargo.space, continuwuity 26.8.0-alpha.1 (a148174)
• Working: matrix.org, Synapse 1.158.0 (b=matrix-org-hotfixes-priv,228237b168)
• Working: wilsoz.com, Synapse 1.147.1
• Working: my test server, continuwuity 0.5.10
• Broken: my test server, continuwuity 26.7.3

DEBUG router{method=PUT path=/_matrix/federation/v2/invite/{room_id}/{event_id} ip="127.0.0.1"}:request:handle{active=219 handled=0}:invite: conduwuit_api::server::invite: Validating invite room state for invite request event_id=$aAe7iSbSmXpZ593gIoPBu5VQ1ww63Av1kO2zBZlgjPw room_id=!anrSJkzBrUiJCBFfhs:hope.net room_version=V10 via=None
DEBUG router{method=PUT path=/_matrix/federation/v2/invite/{room_id}/{event_id} ip="127.0.0.1"}:request:handle{active=219 handled=0}:invite: conduwuit_api::server::invite: Invite state event is not a PDU idx=0
DEBUG router{method=PUT path=/_matrix/federation/v2/invite/{room_id}/{event_id} ip="127.0.0.1"}:request:handle{active=219 handled=0}: conduwuit_core::error::response: Client error error=InvalidParam: PDU in invite state (index 0) violates the room event format kind=InvalidParam status=400 Bad Request
DEBUG router{method=PUT path=/_matrix/federation/v2/invite/{room_id}/{event_id} ip="127.0.0.1"}:request: conduwuit_router::request: 400 Bad Request method=PUT uri=/_matrix/federation/v2/invite/%21anrSJkzBrUiJCBFfhs%3Ahope.net/%24aAe7iSbSmXpZ593gIoPBu5VQ1ww63Av1kO2zBZlgjPw
DEBUG router{method=PUT path=/_matrix/federation/v2/invite/{room_id}/{event_id} ip="127.0.0.1"}: tower_http::trace::on_response: finished processing request latency=0 ms status=400

Raised from https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/src/api/server/invite.rs#L301-L307
continuwuity explanation: https://forgejo.ellis.link/continuwuation/continuwuity/issues/1971
Synapse PR: element-hq/synapse#19723

Nitpicks and Best Practices

/.well-known/matrix/server content-type

Currently served as text/plain instead of application/json

No /.well-known/matrix/support

https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/1929-admin-contact.md
I would prefer this go to a tech support room instead of to only me, but I'm not sure that's supported. If it's not supported and there's nobody more suited, you can put my mxid. Email should probably go to a HOPE or 2600 address.

Outgoing IPv6 federation problems

Reported by the connectivity tester below. I can't easily verify this. Probably a question for EMS.

Testing tool

Current state: https://connectivity-tester.mtrnord.blog/results/p/0Sq-Ju2fbsNp
Check again: https://connectivity-tester.mtrnord.blog/results?serverName=hope.net