Just for reference, here is the source of the ACME fix we cherrypicked.
https://github.com/Neilpang/acme.sh/releases/tag/2.8.3
Lonnie
> On Oct 2, 2019, at 4:54 PM, Michael Knill
> wrote:
>
> Thanks Lonnie. Looks like I might wait for the next Pre Release.
> Very annoying that its broken. Oh
Thanks Lonnie. Looks like I might wait for the next Pre Release.
Very annoying that its broken. Oh well!
Yes I will probably build my own image one day but that day has not arrived yet
__
Regards
Michael Knill
On 3/10/19, 7:47 am, "Lonnie Abelbeck" wrote:
Hi Michael,
> On Oct 2,
Hi Michael,
> On Oct 2, 2019, at 3:51 PM, Michael Knill
> 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 gen
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" wrote:
> On Oct 2, 2019, at 7:11 AM, Michael Keuter wrote:
>
>
>> Am 02.10.2019 um 14:07 schrieb Mi
It would be helpful, if you could provide separate checksums and GPG
signatures to verify fresh installs and to narrow down the current
issue.
___
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listi
Hi Michael,
When "Firmware verification failed!" there are a few possibilities.
1) The network got interrupted (beyond retries) and the 'curl' command gave-up,
the .sha1 failed to match the partial download.
2) If the upstream repository server enabled some kind of CDN-like file
caching, the "
> On Oct 2, 2019, at 7:11 AM, Michael Keuter wrote:
>
>
>> Am 02.10.2019 um 14:07 schrieb Michael Knill
>> :
>>
>> 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 ac
> Am 02.10.2019 um 14:07 schrieb Michael Knill
> :
>
> 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 acc
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.
Time for a rebuild I think. Thanks for y
> Am 02.10.2019 um 13:11 schrieb Michael Knill
> :
>
> I did forget to say that I have my own repository.
> The same download link for my repository works fine on another box but not
> this one.
That is strange. I would try do a clean build just to be sure.
> I then tried using the Astlinux r
I did forget to say that I have my own repository.
The same download link for my repository works fine on another box but not this
one.
I then tried using the Astlinux repository and it worked fine. Weird.
Regards
Michael Knill
On 2/10/19, 8:45 pm, "Michael Keuter" wrote:
> Am 02.10.
> Am 02.10.2019 um 12:34 schrieb Michael Knill
> :
>
> I cant seem to upgrade one of my sites (maybe others but I haven’t tried). It
> always comes up with “Firmware verification failed.“
> What could this be? I have downloaded the file again into the repository but
> it still does it.
>
> R
I cant seem to upgrade one of my sites (maybe others but I haven’t tried). It
always comes up with “Firmware verification failed.“
What could this be? I have downloaded the file again into the repository but it
still does it.
Regards
Michael Knill
___
13 matches
Mail list logo
