From: Michael K. <mic...@ip...> - 2019-10-02 20:52:15
|
Ah so my ACME problem is another issue then. Darn. Is there a workaround without building my own image? Regards Michael Knill On 2/10/19, 10:26 pm, "Lonnie Abelbeck" <li...@lo...> wrote: > On Oct 2, 2019, at 7:11 AM, Michael Keuter <li...@mk...> wrote: > > >> Am 02.10.2019 um 14:07 schrieb Michael Knill <mic...@ip...>: >> >> Hmm I managed to do a successful upgrade using the Astlinux Repository but I certainly have some concerns about the box. >> Seems to be working fine but I couldn't do an acme generate and it actually broke the SSL cert so I couldn't access the web interface. > > There was a very recent change in ACME, which is included into the latest beta: > > https://github.com/astlinux-project/astlinux/commit/731c694933659253e468470480241f2a8d1c6773 Actually this ACME fix is not in the pre-release betas yet as this fix was only a few days old. Generating new and updating ACME certs will hang without the fix. This is all due to a change in the Let's Encrypt CDN provider. If you build your own images, the commit above will fix it. Lonnie _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |