Modern XMPP project discussion - 2026-04-14

https://github.com/snikket-im/xmpp-account-exporter/blob/master/index.js#L9

MattJ: Interesting, 'cause I thought I have the XEP-0156 requirement satisfied by having https://chatterboxtown.us/.well-known/host-meta and https://chatterboxtown.us/.well-known/host-meta.json set up. Even passing XEP-0156 compliance test. I tried the account exporter again and I'm still only able to have my server as source, but is not able to connect as destination.

That line is old, if you support XEP-0156 now then it should be removed

Hm it seems to be the same url, hardcoded or not.

admin, the Content-Type header of https://chatterboxtown.us/.well-known/host-meta is wrong, it should be application/rdf+xml, not text/html; charset=utf-8.

Oh wait it is correct with a GET, just not with a HEAD.

Same for the JSON, weird.

I'm using the ejabberd mod_host___meta for the request handler, but I'm also using apache ProxyPass to proxy from port 443 to 5443 (ejabberd's https listener) If you access https://chatterboxtown.us:5443/.well-known/host-meta is the result the same?

> I'm using the ejabberd mod_host___meta for the request handler, but I'm also using apache ProxyPass to proxy from port 443 to 5443 (ejabberd's https listener) If you access https://chatterboxtown.us:5443/.well-known/host-meta is the result the same? i can access the host-metas on :5443, but not :443 ↺

admin, yes, it even says 404 if I do a HEAD request.

You can test with this command: curl --head https://chatterboxtown.us:5443/.well-known/host-meta ✏

Ok. I'll report to ejabberd channel

quick question though, how does this explain the account exporter is able to log in to my server when I use it as the data source?

I don’t know if that’s your issue, but that’s an issue which could throw off some clients.