This is required because the host name for SSL was not matching when connecting inter-server. So this PR opens a non-ssl port strictly within the container network. The alternative was having the bot use the external connection, which the firewall configuration was blocking and was not desired.
This is required because the host name for SSL was not matching when connecting inter-server. So this PR opens a non-ssl port strictly within the container network. The alternative was having the bot use the external connection, which the firewall configuration was blocking and was not desired.