Stefan Agner
Stefan Agner
This should indeed be fixed with #3714.
I wasn't able to reproduce the issue, and at least when looking at this log it seems to work with the linked config (v1.0.1)? :thinking: https://github.com/ChrisRomp/addon-ecowitt-proxy/actions/runs/9816631174/job/27107067878
> @agners Have you run into this before? This image no longer builds on armhf because of a `SIGSEGV` during bytecode compilation of `python3-async-timeout`. This exact image built a few...
> This PR won't cause any new version to be released and just update the addon store listing, right? I think it's good to merge in that case. It will...
This needs a newer ACME version. Let's update Certbot first before adding more DNS challenge options.
Maybe I was a bit unclear: mijn certbot plug-in requires ACME 2.11.0, but we ship with 2.7.4 currently: ``` 31.83 certbot-dns-mijn-host 0.0.3 depends on acme==2.11.0 ``` Maybe you could ask...
@shubhamku044 with #3751 merged, you can now rebase/merge this PR and move forward.
Hm, seems there is still a merge conflict: ``` #7 35.42 The conflict is caused by: #7 35.42 The user requested cryptography==43.0.1 #7 35.42 certbot 2.11.0 depends on cryptography>=3.2.1 #7...
FWIW, PR #3776 reverts Cryptography to 42 also for another reason, so you can rebase on this instead.
> Im pretty sure that i will manage to do this somehow by using the silabs firmware builder and building a container image with otbr-posix but i would like to...