Closed Sir-Photch closed 11 months ago
Just to check my sanity: you are using an 'appservice' user and not your actual user_id for the bridge, right?
It looks like this line:
Needs to be updated to use get_client_ip_if_available
.
Just to check my sanity: you are using an 'appservice' user and not your actual user_id for the bridge, right?
So when it's configured to go through localhost, the bridge successfully asks for the whatsappbot-user. Does that answer your question?
Comparing with my own server, I'm seeing a 502:
"synapse_inbound_client_readers" "synapse_inbound_client_readers" >> - "- [28/Sep/2023:18:00:43 +0000] "GET /_matrix/client/v3/account/whoami HTTP/1.1" 502 150 "-" "mautrix-gmessages/0.2.0+dev.622daca7 mautrix-go/v0.16.1 go/1.21.1" 0.000
Curiously though, whoami seems to work correctly when a user_id is provided in the query string:
"synapse_inbound_client_readers" "unix:/sockets/synapse_inbound_client_reader3.sock" >> - "- [28/Sep/2023:18:00:50 +0000] "GET /_matrix/client/v3/account/whoami?user_id=@signalbot:tcpip.uk HTTP/1.1" 200 92 "-" "mautrix-signal/0.4.3 mautrix-python/0.19.14 aiohttp/3.8.3 Python/3.10.11" 0.004
Hm, did this get fixed in 1.93?
Description
I have synapse set up to listen on a unix socket, and mautrix-whatsapp trying to connect to it via that socket. This does not work, as when accessing the
whoami
-endpoint the server returns error code 500 with the messageM_UNKNOWN
.The homeserver log reveals that this is due to the code expecting a host to be set, when this isn't applicable in a unix socket usecase.
Steps to reproduce
whoami
endpoint to connect to server via unix socketHomeserver
self-hosted
Synapse Version
1.29.1
Installation Method
Other (please mention below)
Database
fresh postgresql 15.4 setup
Workers
Single process
Platform
archlinux arm
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response