William Knak

I think can be related to the Log4J upgrade. Take a look at the [manifest.mf](https://github.com/imTigger/webapp-hardware-bridge/blob/master/src/main/java/META-INF/MANIFEST.MF) file, check if the Log4J versions were also upgraded there.

Take a look at this pull request #73 to allow one or more parameters, without need to create a route for every method. I think can be useful for most...

As I can see looking on source code, if you don't provide any callbacks, this is already the behavior, as you can see on the lines below (YesButton also sets...

It's working for my scenario: despite the ChainFile issue #7 I was able to install LetsEncrypt + ISPConfig-LetsEncrypt on a headless (slave, no UI) ISPConfig. Changes made on the master...

If you don't want to rsync certificates between servers, yes, you will need to install on any server, they need to create the table field too.

I've found this response from LE engineer: Certificate for public IP without domain name I think the current Baseline Requirements norm is not to issue certificates for private (RFC 1918-reserved)...

I've just got a response¹ at LE community, that clarifies the questions a little bit... maybe for some cases with low new domains creations, let's say, one or two new...

changed the question. A single cert for all vhosts on the same server eliminate problems with non SNI browsers.

Another suggestion is to allow generation of a single cert to all domains and aliases of the same client.

It was implemented in fail2ban in this commit here: https://github.com/fail2ban/fail2ban/commit/54b2208690e3c2fff00fbd9b197984d880e29a02?diff=unified&w=0#diff-b4fbc111cce5736af3c42e545e0db9dcff9606c1b72dbbc50fe7bb7ff620fd92