HPB check with invalid SSL certificate results in "Server responded with: 0"
Open
Nobody has claimed this yet.
bug
feature: api 🛠️
feature: frontend 🖌️
feature: settings ⚙️
Needs triage
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 17h 55m
- Merged PRs (30d)
- 350
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Have a self-signed certificate for your signaling server
- Run HPB test in admin settings with "Verify SSL certificate"
Expected behaviour
Correctly show that the SSL certificate is invalid
Actual behaviour
NC >= 28
NC <= 27
Contributor guide
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 reproducing the HPB test from the admin settings with a self-signed signaling-server certificate and SSL verification enabled. Trace how the test response is handled for NC >= 28 and NC <= 27, then ensure an invalid certificate produces a clear SSL error instead of "Server responded with: 0".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100