mautrix.errors.request.MUnknownToken: Unrecognised access token

[ronilaukkarinen]

I'm sure I followed the instructions pretty thoroughly, but still getting this:

# /usr/local/bin/heisenbridge -c /etc/matrix-synapse/conf.d/heisenbridge.yaml -p 9897
Heisenbridge v1.14.5
ERROR:root:Unexpected failure when registering appservice user.
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/heisenbridge-1.14.5-py3.10.egg/heisenbridge/__main__.py", line 502, in run
    await self.api.request(
  File "/usr/local/lib/python3.10/dist-packages/mautrix/api.py", line 395, in request
    resp_data, resp = await self._send(
  File "/usr/local/lib/python3.10/dist-packages/mautrix/api.py", line 250, in _send
    raise make_request_error(
mautrix.errors.request.MUnknownToken: Unrecognised access token
ERROR:asyncio:Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7fc3a138d9c0>
ERROR:asyncio:Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7fc3a13b2560>, 819481.518503257)]']
connector: <aiohttp.connector.TCPConnector object at 0x7fc3a138da80>

The generated yaml file should be ok.

[lnicola]

Perhaps moving the yaml to a different place. If you're using split Synapse config files, there are two files involved, one generated by heisenbridge, and one Synapse needs to load the former. Mine was:

app_service_config_files:
  - /etc/matrix-synapse/appservices.d/heisenbridge.yaml

So Synapse loads everything in /etc/matrix-synapse/conf.d/ as Synapse config, but the Heisenbridge config file isn't that.

[KhalilSantana]

I've tried using @lnicola's approach without success (Synapse server running on NixOS + heisenbridge inside a docker container with --network host)