net/haproxy: Rules were reordered after adding a certificate
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- The title contains the plugin to which this issue belongs
Describe the bug
We added a new certificate and also set it as the default for the Public Service.
After that, our systems were no longer accessible. Some investigation revealed that the order of the rules had been completely reversed without our intervention.
The error could not be reproduced on a second machine.
Environment
Software version used and hardware type if relevant.
e.g.:
Version 26.1.10
Architecture amd64
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 certificate and default Public Service change in the net/haproxy plugin, comparing rule ordering before and after the update. Check the generated HAProxy configuration and compare it with the unaffected second machine. Done means rules retain their intended order and the affected systems remain accessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100