Sevan
Sevan
Hello @buchdag, I use a quick fix for the moment so it's ok. Yes, it's working on nginx-proxy end but it's not working for the standalone configs because they're not...
Both solutions are good but the first one might be better because we would have the same behavior between the two applications.
It's not very convenient, I think I'll stay with the manual way for now. Do you plan to add the feature one day?
Hello, It seems that the feature was introduced in [3.0.7](https://github.com/enix/x509-certificate-exporter/releases/tag/v3.7.0), it works well for me. The doc/readme was not updated though.
(cc. @arcln as its the one who implemented the feature)
This is not completed, I usualy find the stale-bot quite annoying but here it's lying to anyone following the thread, we have no indication from anyone that this has been...
Hello, We are hitting the issue after an upgrade from 2.7.5 to 2.8.5, is there any work around?
> Changing the value for ssl-redirect-port to 443 works, but I would have preferred a possible value of "none" to just redirect to https without any port. I agree on...
Yes, I'll try to fix that before the end of the week.
I've modified a little bit the vars, it should fix most of the failed actions but I' not sure about the OpenBSB fail