Hi Michael, > On Oct 2, 2019, at 3:51 PM, Michael Knill <michael.kn...@ipcsolutions.com.au> > wrote: > > Ah so my ACME problem is another issue then. Darn. > Is there a workaround without building my own image?
Building your own image is the most straightforward fix, but if you are not setup to do that, then ... We plan on generating new pre-release beta in the next couple days, does that help you ? Else, the file that needs to be patched is at /stat/etc/acme/acme.sh , but it is best not to edit that file directly. Example fix: -- vultr ~ # mkdir /tmp/acme-fix vultr ~ # cd /tmp/acme-fix vultr acme-fix # curl -o fix1.patch https://raw.githubusercontent.com/astlinux-project/astlinux/master/package/acme/acme-0900-upstream-new-LE-CDN-curl-fix.patch % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 689 100 689 0 0 3497 0 --:--:-- --:--:-- --:--:-- 3479 vultr acme-fix # curl -o fix2.patch https://raw.githubusercontent.com/astlinux-project/astlinux/master/package/acme/acme-0910-upstream-fix-curl-error-code-2.patch % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3589 100 3589 0 0 49164 0 --:--:-- --:--:-- --:--:-- 49164 vultr acme-fix # cp /stat/etc/acme/acme.sh . vultr acme-fix # ls -l total 188 -rwxr-xr-x 1 root root 180871 Oct 2 16:26 acme.sh -rw-r--r-- 1 root root 689 Oct 2 16:25 fix1.patch -rw-r--r-- 1 root root 3589 Oct 2 16:25 fix2.patch vultr acme-fix # patch acme.sh < fix1.patch patching file acme.sh vultr acme-fix # patch acme.sh < fix2.patch patching file acme.sh vultr acme-fix # ls -l acme.sh -rwxr-xr-x 1 root root 181837 Oct 2 16:26 acme.sh -- So, this new "acme.sh" needs to be located at /stat/etc/acme/acme.sh ... while copying it will work for today, you will be fixed in time with future upgrades. The unionfs overlay version will need to be removed in the future. Clear ? Lonnie > > Regards > Michael Knill > > On 2/10/19, 10:26 pm, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote: > > > >> On Oct 2, 2019, at 7:11 AM, Michael Keuter <li...@mksolutions.info> wrote: >> >> >>> Am 02.10.2019 um 14:07 schrieb Michael Knill >>> <michael.kn...@ipcsolutions.com.au>: >>> >>> 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 > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. > > > > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
