Can the websocket server chance certificate once started? lets encrypt + expiration.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I'm currently using the websocket library and it's working well, but after a a few months my letsencrypt certificate doesn't get update and connection failed to continue working. Is there a way to change the certificate without have to close the websocket and all connection/events ?
I've tried to assigned:
SslConfiguration.ServerCertificate = [new certificate here]
but the websocket still served the original one when it was created.
Thanks
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
Start by tracing how the websocket server uses SslConfiguration.ServerCertificate when it is created, since the issue reports that later assignment does not affect the served certificate. Determine whether certificate renewal can occur without closing existing connections, and verify that subsequent connections use the renewed certificate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100