Certificate signed by unknown authority about adguardhome-sync HOT 4 CLOSED

I used the main tag as that has was built in the last hour, compared to latest which is 18 days. No joy.

I hadn't noticed the insecureSkipVerify: true flags, set them up and it's working with that currently.
I'll stick around though to get the TLS going properly.

from adguardhome-sync.

Hi

the image scr.io/linuxserver/adguardhome-sync is not maintained by this repository/me.

Dies the issue also consist if you used the images from this repo?
https://github.com/bakito/adguardhome-sync/pkgs/container/adguardhome-sync

from adguardhome-sync.

Yes, I mentioned that under the additional context.
The docker images seem interchangeable, so I've left this repo's one in place as this is figured out.

from adguardhome-sync.

Sorry, I didn't see that.
It might be, that lets encrypt uses a new ca cert that is not yet available in the base images used.

I rebuilt the latest image to use the newest base.
Can you try this image if it works.

Otherwise you can either configure the replica to use insecureSkipVerify=true ( or env REPLICA_INSECURESKIPVERIFY=true) to temporary ignore the cert.

Our you can mount the valid cert as volume to your container with path /etc/ssl/certs/ca-certificates.crt

from adguardhome-sync.