4 ms·
I've addressed everything you've mentioned here. I would greatly appreciate it if you could take a look and offer any constructive feedback. Many thanks for yo
by JamesTheHacker 9y ago
I've addressed everything you've mentioned here. I would greatly appreciate it if you could take a look and offer any constructive feedback.
Many thanks for your time and help.
- stephenr 9y agoIn the words of Roy Trenneman.... Oh dear oh dear oh dear! I.. Um. It's different now but I'm pretty sure certs still won't renew, and if they did haproxy wouldn't know about them. I'm not sure what your motivation is for posting this article but honestly you need a better understanding before trying to give other people technical advice about something. Edit: also the weirdness persists. Why are you allowing inbound dns requests. Why is your firewall blocking first instead of last. Why are you using sudo for curl that gets piped. Jesus why are you curl|bash at all. I'm pretty sure your cron job is unnecessary and won't even work. <breathe>... There is still a lot wrong with this but I can't type easily so that will have to do for now
- detaro 9y ago- your HAProxy config expects certbot to listen at port 54321. You never configure certbot to do that, so it won't do it, and renewal will not work. - if renewal did work, the certs HAProxy is reading are never replaced. Really, there are already good tutorials for HAProxy and certbot out there, why muddy the water with another, broken attempt at one? If you are setting this up in a test environment and are writing it up as you go, I recommend having screen recording/shell logging so you can afterwards check exactly what you did and write it down (at least that has helped me in the past). If you don't, then you really should do a test run and verify what you do works. Writing up something you did a while ago without replicating it makes it really easy to miss crucial steps.