证书验证失败
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.7k
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 2
Description
在某些情况下，TLS证书验证失败了，我们应该增肌一个检查证书的选项便于排查问题：
我尝试过修改服务器时间同步，但实际上并不是时间导致的验证失败问题
2024/09/06 19:34:16 [Warning] [3097967295] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (域名): > tls: failed to verify certificate: x509: certificate has expired or is not yet valid: ] > common/retry: all retry attempts failed
2024/09/06 19:34:16 [Warning] [1002476645] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (域名): > tls: failed to verify certificate: x509: certificate has expired or is not yet valid: ] > common/retry: all retry attempts failed
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the report. Start by locating the shell CLI entry point responsible for connection diagnostics and reproduce the logged x509 expiry or not-yet-valid failure. Done means the new certificate-check option helps distinguish certificate validity problems from server-time issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, networking, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100