You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the mx-puppet-discord container, I can ping synapse and from the synapse
container I can ping bridge-mx-puppet-discord so I don't belive there is an
issue with the two containers communicating.
I have the following in my config.yaml for mx-puppet-discord
bridge:
# Port to host the bridge on
# Used for communication between the homeserver and the bridge
port: 8434
# The host connections to the bridge's webserver are allowed from
bindAddress: 0.0.0.0
# Public domain of the homeserver
domain: jn.hn
# Reachable URL of the Matrix homeserver
homeserverUrl: http://synapse:443
...
# Map of homeserver URLs to their C-S API endpoint
#
# Useful for double-puppeting if .well-known is unavailable for some reason
homeserverUrlMap:
jn.hn: http://synapse:443
However, I get the following logs from the bridge container:
May-3 20:28:50.459 [bot-sdk-MatrixLiteClient] info: (REQ-9) POST http://synapse:443/_matrix/client/r0/register
May-3 20:28:50.469 [bot-sdk-MatrixLiteClient] error: (REQ-9) RequestError: connect ECONNREFUSED 172.26.0.2:443
at ClientRequest.<anonymous> (/opt/mx-puppet-discord/node_modules/got/dist/source/core/index.js:937:25)
at Object.onceWrapper (node:events:486:26)
at ClientRequest.emit (node:events:391:22)
at ClientRequest.origin.emit (/opt/mx-puppet-discord/node_modules/@szmarczak/http-timer/dist/source/index.js:39:20)
at Socket.socketErrorListener (node:_http_client:494:9)
at Socket.emit (node:events:379:20)
at emitErrorNT (node:internal/streams/destroy:188:8)
at emitErrorCloseNT (node:internal/streams/destroy:153:3)
at processTicksAndRejections (node:internal/process/task_queues:81:21)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1139:16) {
code: 'ECONNREFUSED',
timings: {
start: 1620073730465,
socket: 1620073730465,
lookup: 1620073730466,
connect: undefined,
secureConnect: undefined,
upload: undefined,
response: undefined,
end: undefined,
error: 1620073730466,
abort: undefined,
phases: {
wait: 0,
dns: 1,
tcp: undefined,
tls: undefined,
request: undefined,
firstByte: undefined,
download: undefined,
total: 1
}
}
}
May-3 20:28:50.470 [bot-sdk-Appservice] error: Encountered error registering user:
May-3 20:28:50.474 [bot-sdk-Appservice] error: RequestError: connect ECONNREFUSED 172.26.0.2:443
at ClientRequest.<anonymous> (/opt/mx-puppet-discord/node_modules/got/dist/source/core/index.js:937:25)
at Object.onceWrapper (node:events:486:26)
at ClientRequest.emit (node:events:391:22)
at ClientRequest.origin.emit (/opt/mx-puppet-discord/node_modules/@szmarczak/http-timer/dist/source/index.js:39:20)
at Socket.socketErrorListener (node:_http_client:494:9)
at Socket.emit (node:events:379:20)
at emitErrorNT (node:internal/streams/destroy:188:8)
at emitErrorCloseNT (node:internal/streams/destroy:153:3)
at processTicksAndRejections (node:internal/process/task_queues:81:21)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1139:16) {
code: 'ECONNREFUSED',
timings: {
start: 1620073730465,
socket: 1620073730465,
lookup: 1620073730466,
connect: undefined,
secureConnect: undefined,
upload: undefined,
response: undefined,
end: undefined,
error: 1620073730466,
abort: undefined,
phases: {
wait: 0,
dns: 1,
tcp: undefined,
tls: undefined,
request: undefined,
firstByte: undefined,
download: undefined,
total: 1
}
}
}
Do you have any suggestions?
The text was updated successfully, but these errors were encountered:
Hi,
I am trying to make this work with docker compose. Here is the appropriate part
of my docker-compose file:
From the mx-puppet-discord container, I can ping
synapse
and from the synapsecontainer I can ping
bridge-mx-puppet-discord
so I don't belive there is anissue with the two containers communicating.
I have the following in my config.yaml for mx-puppet-discord
However, I get the following logs from the bridge container:
Do you have any suggestions?
The text was updated successfully, but these errors were encountered: