ACME Client: Automations - Sync SSL certificate changes into running HAProxy not doing anything?
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:
- [X ] I have read the contributing guidelines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- [X ] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
Describe the bug
I'm using ACME client automations and noticed that the Sync SSL certificate changes into running HAProxy automation does not seem to do anything.
Checking ACME Client: Certificates I can see that my LE certificates has been renewed, but viewing the certificate being served by HAProxy it's clear that it's from the previous iteration.
I have these automations configured:
Manually clicking "Run automations" for the certificate in question does not solve anything, it's still the old certificate in HAProxy.
However if I stop HAProxy and start it again then the new cert is served.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
New cert being served after running the automation.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 26.1.8_5-amd64 (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 at the ACME Client certificate automation entry point and trace the “Sync SSL certificate changes into running HAProxy” action, then compare it with the stop/start HAProxy path. Reproduce by renewing a certificate and using “Run automations”; done when the new certificate is served without manually restarting HAProxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- devops, networking, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100