Posts by aptalca

    My guess is, it's due to curl when trying to connect to the domain, trying to go out the wan and try to come back in through the router and into the letsencrypt container.


    Assuming the cron tasks are running inside the nextcloud container, see if you can curl "https://localhost/remote.php/dav/calendars/<username>/personal?export" instead, so it tries to connect directly

    Yes, you need a matching docker image for your arch. Some images (most of linuxserver.io ones) are multi-arch, meaning, when you pull an image, it automatically retrieves the correct version for your arch. But most of the random images you find on docker hub are x86_64 only.

    I honestly don't recommend running dhcp in a docker container, let alone on libreelec. Your dhcp should really be on a dedicated device like a router or pfsense.


    I use adguardhome as just a dns server for ad blocking, which is what it does best.


    With regards to the 172.x.x.x address, your correct that is an internal docker network ip. But, all the ports that you define in the addon settings should be mapped at the libreelec ip, so you need to use the libreelec lan ip and the ports you mapped to access adguardhome.


    For instance if you map port 53 for dns, on another device, you'd use "libreelec-lan-ip:53" as the adguardhome dns address

    You're following a really old article and making manual modifications to the docker service and of course it is breaking.


    Skip modifying the docker service. It works fine out of the box.


    Just install the docker addon and do "docker run hello-world" and you'll see.

    You did not say what method (nfs, smb, etc.) and you did not say how they are mounted (systemd?)


    If systemd, set its service to start before the docker service


    Also fyi, linuxserver does not recommend or support config files to reside on remote shares. Media folders however can be on remote shares.

    Linuxserver.io ones can be installed via addons for added convenience and ease of use but you can use any docker image via command line (docker run) or portainer on libreelec (assuming you're using the correct arch)

    Nextcloud has its own auto redirects for security purposes and you'll have to modify those in it's config file. You may have to do other stuff on the nginx side but I'm not sure.


    All of that automation was done for port 443, ymmv with a custom port

    One thing is an api key to identified application that consumes service... this is complete different... we are talking a personal (user) key that would enable google to track your privacy (searches, videos you reproduce, etc).
    This practice attempts freedom, I'm not sure why you try to make it looks as it were ok.

    It's a youtube/google restriction (iirc). You can't use their api without an api key. Apis use the api keys to make sure bad actors aren't abusing their api, and they throttle access via keys if needed.


    If you're worried about tracking, open a new Google account and get an api key for it. Or Google online to see if others like you are sharing anonymous api keys.

    You've misunderstood.


    Something must be wrong with my setup then. Libreelec with kodi and home assistant in a docker runs fine and smooth. When I restart libreelec, the HA docker (which I installed using command line) does not get destroyed and recreated.


    Nginx letsencrypt and duck dns gets destroyed and recreated.


    Docker addons are not the same as docker containers you manually create. Addons use systemd to manage the containers in an automated fashion. The destroy/create is part of the automation. It is perfectly fine as docker containers are ephemeral by design. It is how docker is meant to be used. If you ever want to update the homeassistant container you manually created, you will have to destroy and recreate it based on an updated image (manually). Addons do that automatically without user intervention.


    The validation is performed when the container is started for the first time. Nginx won't be up until ssl certs are successfully generated.

    "started for the first time" refers to starting it with no existing persistent data. The persistent data (including the certs) reside in the userdata addon_data folder by default. As long as it's there, certs are not regenerated until they get close to expiration.


    In any case, it sounds like this is a case of the xy problem. Let's focus on the boot delay. I assure you I'm running plenty of docker addons here on an rpi4 with no noticeable delay. The only delay I'm observing is "waiting for network" before kodi starts.


    Check the kodi log to see what's holding things up during boot. Also check the addon logs with journalctl -u docker.linuxserver.letsencrypt and journalctl -u docker.linuxserver.duckdns (you can also try journalctl -u docker.linuxserver.updater).


    With that said, make sure you update your addons and refresh the repos. There was a brief period of time where the addon updater caused a boot delay of about 10 minutes due to a bug in its systemd config. It was fixed shortly after.


    EDIT: As a test, I set up all three containers in question, two as addons and one manually. I even created homeassistant with the same docker run from your other thread, all on an rpi4 with le 9.2.3 and I experience no boot delay at all.