Open suranc opened 5 years ago
I figured this out, if you set the environment variable ROCKETCHAT_USESSL
to true
, then version 2.0.0 is able to connect over https. Still hitting problems with newer versions of Rocket.Chat related to #338, but that's due to the @rocket.chat/sdk
which has a few PRs pending that can fix the issue. This environment variable fixes this specific issue.
I'm leaving it open because the repo still needs some documentation updates to make this clear, or a fix so it's no longer required. However, for the time being that environment variable works around this issue.
I am trying to update the package.json in my base image to use 2.0.0 instead of 1.0.8, however it is unable to connect when I switch to 2.0.0. It seems that it might not be parsing the ROCKETCHAT_URL right or something, as my environment variable is set to use https, but useSsl is false in the logs.
Here is what I see when I try to run a container from my 2.0.0 image:
Looking at the code in
./@rocket.chat/sdk/dist/lib/driver.js:52
it seems that useSsl should be true, however it is false in the above log.My environment variable definitely has https in it:
I have tried it without the
:443
but that made no difference, and I am using exactly the same environment configuration between 1.0.8 and 2.0.0. I am launching this container via a Kubernetes helm chart I manage and using the same values file for each, just bumping my image version. The image using 1.0.8 works, but the one using 2.0.0 does not.Here is the dependencies section from my new package.json using 2.0.0: