Verified Commit 0d136325 authored by Jan Alexander Steffens (heftig)'s avatar Jan Alexander Steffens (heftig)
Browse files

matrix: Use node --dns-result-order=ipv4first to work around bug

Node's address lookup strips the scope ID from link-local IPv6
addresses, making them invalid and unable to be connected to.

We're getting hit with this since Node 17 because it now defaults to the
`verbatim` dns-result-order and this happens to return the link-local
IPv6 address for `` first.

Specify `ipv4first` so we return to Node 16's behavior.
parent 69bb5a94
Pipeline #13633 passed with stage
in 46 seconds
......@@ -6,7 +6,7 @@ synapse.service
ExecStart=/usr/bin/node app.js \
ExecStart=/usr/bin/node --dns-result-order=ipv4first app.js \
-c /etc/synapse/irc-bridge.yaml \
-f /etc/synapse/appservice-registration-irc.yaml
......@@ -8,7 +8,7 @@ User=synapse
ExecStart=/usr/bin/node lib/index.js
ExecStart=/usr/bin/node --dns-result-order=ipv4first lib/index.js
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment