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
There's a use case to set up a node behind a reverse proxy server that manages the SSL/TLS encryption.
In that case, the user would only want to announce the IP or domain of their proxy server. See issue #1797.
We raised a PR that adds a --ext-multiaddr-only CLI flag which if it's set to true, only the multiaddresses specified by the user through the --ext-multiaddr flag are published.
In that case, --nat and --dns4-domain-name options would not have any effect, as the announced addresses would be overridden by the user's list.
After the change introducing the new flag is merged, we can add instructions to the documentation for this use case which in short would be to set --ext-multiaddr-only=true and list the multiaddresses with the server's IP/domain through the --ext-multiaddr option.
The text was updated successfully, but these errors were encountered:
There's a use case to set up a node behind a reverse proxy server that manages the SSL/TLS encryption.
In that case, the user would only want to announce the IP or domain of their proxy server. See issue #1797.
We raised a PR that adds a
--ext-multiaddr-only
CLI flag which if it's set to true, only the multiaddresses specified by the user through the--ext-multiaddr
flag are published.In that case,
--nat
and--dns4-domain-name
options would not have any effect, as the announced addresses would be overridden by the user's list.After the change introducing the new flag is merged, we can add instructions to the documentation for this use case which in short would be to set
--ext-multiaddr-only=true
and list the multiaddresses with the server's IP/domain through the--ext-multiaddr
option.The text was updated successfully, but these errors were encountered: