Follow button on other instances results in 'User not found'

Support
1

When I input my instance URL after clicking the ‘follow’ button on Mastodon instances, it takes me to my instance but says ‘User not found’. The generated url is:
https://s.firecat53.net/authorize_interaction?uri=https%3A%2F%2Fchaos.social%2Fusers%2Fnixos_org
However when I curl the webfinger address for my domain I get:

{
  "aliases": [
    "https://s.firecat53.net/users/firecat53"
  ],
  "links": [
    {
      "href": "https://s.firecat53.net/users/firecat53",
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html"
    },
    {
      "href": "https://s.firecat53.net/users/firecat53",
      "rel": "self",
      "type": "application/activity+json"
    },
    {
      "href": "https://s.firecat53.net/users/firecat53",
      "rel": "self",
      "type": "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\""
    },
    {
      "rel": "http://ostatus.org/schema/1.0/subscribe",
      "template": "https://s.firecat53.net/ostatus_subscribe?acct={uri}"
    }
  ],
  "subject": "acct:firecat53@firecat53.net"
}

If I change the URL to ostatus_subscribe?acct=.... (instead of authorize_interaction...), then my instance will correctly add the follow.

Is that a problem with my configuration or a Mastodon issue?

Running latest Akkoma 3.13.2 on NixOS behind Traefik reverse proxy and with the ‘split domain’ setup that seems to be functioning normally (user @firecat53@firecat53.net, instance at s.firecat53.net).

Thanks!

2

This is a Mastodon issue, see: The new remote interaction dialog results in a broken behavior when used with non-Mastodon servers · Issue #26995 · mastodon/mastodon · GitHub

In the comments over there it was claimed it should still work when using a user handle instead of bare domain, but in my testing it doesn’t (anymore) eventhough Akkoma’s webfinger reply for a user (there’s no entry for a bare domain) defines a rel="http://ostatus.org/schema/1.0/subscribe" link template

3

Thanks! I left a comment at the above github issue noting that Mastodon still is not providing the ostatus URL even when it is correctly available via the webfinger query.