Open alexosugo opened 3 months ago
You can try ignoring TLS certificate validation.
e.g. export NODE_TLS_REJECT_UNAUTHORIZED=0
before launching the user management tool?
Thanks @derickl. That and adding it appending it to the .env files work. I expect that some people have experienced a similar issue so this should help.
You probably don't need to do both. Does adding it to the env file (without exporting) work?
@derickl Not both. Either works. Even without exporting.
CHT instances installed via Docker have may have an optional TLS certificate installed to bypass the 'Your connection is not private' error that shows on the browser when you try to access it. When the CHT management tool is ran with the following env variables:
login fails with an
invalid certificate error
. See log below: