PR #56 (MeshMonitor connection, v0.22.0) was merged from f6b884d, but a follow-up commit 25f99f0 that removes the NODE_TLS_REJECT_UNAUTHORIZED=0 workaround was only ever committed locally and was never pushed before the merge — so it is not in main yet.
The MeshMonitor gateway (https://meshmonitor.kkhost.pl) uses a valid Let's Encrypt certificate (issuer O = Let's Encrypt, CN = YE1), verified with a normal (no -k) request → HTTP 200. So the NODE_TLS_REJECT_UNAUTHORIZED=0 flag is unnecessary and a security downgrade (it disabled TLS cert verification for all outbound connections in the container, including the LLM and opencode services).
This PR brings in that single commit: drops the flag + 'self-signed' comments from docker-compose.yml and src/main.ts, and corrects the v0.22.0 CHANGELOG wording. No version bump — it completes the v0.22.0 MeshMonitor connection work.
Verified: npm run build clean; npm test 245/245 green.
## What
PR #56 (MeshMonitor connection, v0.22.0) was merged from `f6b884d`, but a follow-up commit `25f99f0` that **removes the `NODE_TLS_REJECT_UNAUTHORIZED=0`** workaround was only ever committed locally and was never pushed before the merge — so it is **not** in `main` yet.
The MeshMonitor gateway (`https://meshmonitor.kkhost.pl`) uses a **valid Let's Encrypt certificate** (issuer `O = Let's Encrypt, CN = YE1`), verified with a normal (no `-k`) request → HTTP 200. So the `NODE_TLS_REJECT_UNAUTHORIZED=0` flag is **unnecessary** and a **security downgrade** (it disabled TLS cert verification for *all* outbound connections in the container, including the LLM and opencode services).
This PR brings in that single commit: drops the flag + 'self-signed' comments from `docker-compose.yml` and `src/main.ts`, and corrects the v0.22.0 CHANGELOG wording. No version bump — it completes the v0.22.0 MeshMonitor connection work.
Verified: `npm run build` clean; `npm test` 245/245 green.
The MeshMonitor gateway uses a valid Let's Encrypt certificate, so
standard TLS certificate verification already works — no workaround
needed. The flag was a security downgrade: it disabled cert verification
for ALL outbound connections in the container (including the LLM and
opencode services), not just the gateway.
- docker-compose.yml: drop NODE_TLS_REJECT_UNAUTHORIZED env line + comment
- src/main.ts: drop process.env.NODE_TLS_REJECT_UNAUTHORIZED + comments
- CHANGELOG.md: correct the v0.22.0 Docker bullet wording
Part of the already-open MeshMonitor connection work (PR #56): no version
bump, no new changelog section.
Co-Authored-By: OpenCode <noreply@opencode.ai>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
PR #56 (MeshMonitor connection, v0.22.0) was merged from
f6b884d, but a follow-up commit25f99f0that removes theNODE_TLS_REJECT_UNAUTHORIZED=0workaround was only ever committed locally and was never pushed before the merge — so it is not inmainyet.The MeshMonitor gateway (
https://meshmonitor.kkhost.pl) uses a valid Let's Encrypt certificate (issuerO = Let's Encrypt, CN = YE1), verified with a normal (no-k) request → HTTP 200. So theNODE_TLS_REJECT_UNAUTHORIZED=0flag is unnecessary and a security downgrade (it disabled TLS cert verification for all outbound connections in the container, including the LLM and opencode services).This PR brings in that single commit: drops the flag + 'self-signed' comments from
docker-compose.ymlandsrc/main.ts, and corrects the v0.22.0 CHANGELOG wording. No version bump — it completes the v0.22.0 MeshMonitor connection work.Verified:
npm run buildclean;npm test245/245 green.