Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues related to self-signed certificates #500

Open
anselor opened this issue Oct 6, 2024 · 1 comment
Open

Issues related to self-signed certificates #500

anselor opened this issue Oct 6, 2024 · 1 comment

Comments

@anselor
Copy link

anselor commented Oct 6, 2024

I've run into a number of issues on my home LAN related to self-signed certificates. At a minimum these should be added to the documentation but, perhaps, may be desirable to have the defaults do something similar to this.

The node.js environment appears to have its own list of root CAs that is separate from the host environment it operates in.
To have node.js share the same list of root CAs as its host environment (on debian-based linux distros, at least), this environment variable needs to be added to the container:

NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt

In my specific case where I have self-hosted a certificate authority with a self-signed root cert in my LAN, I've registered this cert to the docker host environment and it just needs to be mapped into the hoard container's environment with this:

    volumes:
      - /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt:ro

Additionally, on the mobile app, it's unable to connect even when the root CA has been added to the phone's trusted store.

@anselor
Copy link
Author

anselor commented Oct 6, 2024

It appears this PR may address the last point: #416

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant