Thanks @lc3t35
the connection was never opened, just got eitehr 502 or 400 ‘bad response’ …
that said, we have changed the NGINX settings and have had some success. I think we had a red-herring in our test environment that was blocking it even when the NGINX settings were in place. We’re going to dig into it deeper but I am suspecting some firewall/network related issue could have been masking/causing the issue.