Wrappers should set their local address when connecting to the master #213

juliarn · 2019-10-30T19:42:55Z

The wrapper verification works through the comparison of the address of the connected wrapper and the address of the wrapper in the services.json.
If a server has multiple public ips, this can lead to issues when trying to connect to the master, because the wrapper doesn't set the local address when connecting to the master, so the ips might not be the same.
The wrapper should set the address in the config.yml as its local address.

issue-label-bot · 2019-10-30T19:42:57Z

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.81. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

to the one configured as the internal IP Closes #213

issue-label-bot bot added the bug Something isn't working label Oct 30, 2019

GiantTreeLP self-assigned this Nov 13, 2019

GiantTreeLP added a commit that referenced this issue Nov 20, 2019

Set the local address for the connection of the wrapper to the master

cb6e85e

to the one configured as the internal IP Closes #213

GiantTreeLP added the done This issue has been dealt with and will be closed with the next pull request into master label Mar 25, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Wrappers should set their local address when connecting to the master #213

Wrappers should set their local address when connecting to the master #213

juliarn commented Oct 30, 2019 •

edited

Loading

issue-label-bot bot commented Oct 30, 2019

Wrappers should set their local address when connecting to the master #213

Wrappers should set their local address when connecting to the master #213

Comments

juliarn commented Oct 30, 2019 • edited Loading

issue-label-bot bot commented Oct 30, 2019

juliarn commented Oct 30, 2019 •

edited

Loading