[GH-ISSUE #5046] [Question] wss certificate validation behavior

gitea-mirror commented

2026-05-05 14:31:35 -06:00

Owner

Copy link

Originally created by @undirectlookable on GitHub (Nov 4, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5046

Describe the feature request

I have successfully connect my frp server behind a nginx with ssl via wss transport mode.
Just a question: when my server certificate is invalid(eg. expired, common name doesn't match), will frpc ignore this error or refuse to connect?

according to this line of code, InsecureSkipVerify will be true when certFile is not provided, it that correct?

If possible, it's nice to have a transport.tls.InsecureSkipVerify option to handle this behavior.

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @undirectlookable on GitHub (Nov 4, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5046 ### Describe the feature request I have successfully connect my frp server behind a nginx with ssl via `wss` transport mode. Just a question: when my server certificate is invalid(eg. expired, common name doesn't match), will frpc ignore this error or refuse to connect? according to [this line of code](https://github.com/fatedier/frp/blob/v0.65.0/pkg/transport/tls.go#L148), `InsecureSkipVerify` will be true when `certFile` is not provided, it that correct? If possible, it's nice to have a `transport.tls.InsecureSkipVerify` option to handle this behavior. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:31:35 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:31:39 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Nov 19, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Nov 19, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:50:26 -06:00

[PR #3971] [MERGED] Update README.md - add note for public purpose #4877

gitea-mirror referenced this issue

2026-05-05 14:50:54 -06:00

[PR #4056] [MERGED] bump version #4902

No Branch/Tag specified