Support manual TLS certificate/key for custom domain WSS listeners
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
## Context
Kubo's [`AutoTLS`](https://github.com/ipfs/kubo/blob/master/docs/config.md#autotls) feature (introduced in #10521) automatically obtains TLS certificates for `/wss` listeners via [p2p-forge](https://github.com/ipshipyard/p2p-forge), but only for `*.{peerid}.libp2p.direct` domains.
There is currently no built-in way to use WSS with a user-supplied TLS certificate for a custom domain (e.g., `example.net`). Operators who want WSS on their own domain must run a reverse proxy (nginx, Caddy, etc.) in front of kubo.
This was originally raised by @lidel in #8740:
> What if we do the same thing we did for private swarm and if one adds `/dns/example.net/.../wss` addr, check if `$IPFS_PATH/example.net.crt` and `$IPFS_PATH/example.net.key` exist and use them if present? (and if not, do ACME)
## Proposal
Add support for manual TLS certificate/key files for custom domain WSS, following the convention used for private networks:
- When a `/dns/example.net/.../wss` (or `/tls/sni/example.net/.../ws`) address is configured in `Addresses.Swarm`, check for `$IPFS_PATH/example.net.crt` and `$IPFS_PATH/example.net.key`.
- If both files exist, use them as the TLS certificate for that WSS listener.
- If not, fall back to AutoTLS (for `*.libp2p.direct` domains) or skip WSS.
This would allow operators to use WSS with their own domains and certificates (e.g., from their own ACME client, or a commercial CA) without a reverse proxy.
## Related
- #8740 (original PR, superseded by #10521)
- #10521 (merged: AutoTLS via p2p-forge)
- #10560 (epic: enabling AutoTLS by default)
Contributor guide
Research direction
Start by tracing how Addresses.Swarm entries for /wss and /tls/sni are handled alongside the AutoTLS implementation introduced in #10521. Verify the existing private-network certificate-file convention and determine where custom-domain certificate and key paths should be resolved. Done means valid paired files enable WSS, missing files preserve the stated AutoTLS or skip behavior, and coverage verifies these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100