Posts by aptalca

    That's a restriction documented in the readme. Duckdns validation results in a cert with only one address covered. That's because duckdns only allows one TXT record set.


    So it can cover only one of the following at a time:

    domain.duckdns.org

    *.domain.duckdns.org

    nextcloud.domain.duckdns.org


    The readme recommends using the second option so it covers all (sub)subdomains, and using the www endpoint instead of the naked domain.

    If you're gonna reverse proxy, it doesn't matter what port nextcloud is set to as it won't be used. The addons already attach to the lsio network and advertise themselves with the dns host names "nextcloud", "mariadb", "letsencrypt", etc.


    Don't overthink it. Don't modify anything in the proxy conf, just follow the directions at the top and make the necessary changes to nextcloud config.php file so it allows reverse proxy access.

    I can't help you with your domain name or cnames, but if you want a reliable ddns address, look into duckdns. All subdomains to your custom domain automatically forward to your ip. With that, you can do nc.customname.duckdns.org


    For certs, you need to check the logs to see what went wrong. The commands are in the pinned thread about linuxserver docker addons

    In the config folder, you can find the nginx and php logs


    http would require modifying the default nginx site conf, which you can do, but we don't support it. We recommend reverse proxying (potentially via our letsencrypt image)

    If you map the port correctly in your docker run, the port will be accessible on the libreelec lan ip. Then you port forward on your router to make it accessible on wan (internet).

    Docker containers are sandboxed. They only have access to things that you specify. Go into addon settings, turn on additional parameters and input "--device /dev/ttyACM0” and see if that works

    It looks like jeedom doesn't create its database automatically. It expects you to first create a database, and set up a user with access to it.


    So you need to use the mariadb docker addon to create it. But keep in mind that the db and user creation only happens during first start. Once the databases are set up, we no longer touch it, because we don't want to break your stuff. If you want to start over, you need to uninstall the mariadb addon and tell LE to remove user data as well. If you changed the data folder location in the addon settings, you'll need to manually delete that folder.


    Then you can install mariadb addon again. It will open the settings page, allowing you to enter the user and database details. Once that's set up, then you can enter that info into jeedom.


    In jeedom, use the libreelec lan ip as the mariadb address (localhost refers to inside the container).

    Hey guys, I just wanted to let you know that the LinuxServer team recently published two docker images to help scientists with COVID-19 research.


    The images are for [email protected] and BOINC, both of which distribute compute jobs to the machines of users from all over the world in order to crowd-source scientif1c research related computations. They are both currently prioritizing COVID-19 related research such as "predicting the atomic-scale structure of an important coronavirus prote1n (spike)" and "understanding how it binds to the ACE2 receptor required for viral entry into cells".


    We also just published docker addons so you can easily install them on your LibreELEC devices to help out.


    That's right, you can help out COVID-19 researchers by donating your unused cpu cycles.


    Here's a blog article we published about the images: COVID-19: How it's affected us, and how you can help


    Here's some LibreELEC specific info on the images:


    Both addons are avaliable through the Linuxserver.io repo. Go to addons, install from repository, Libreelec addons, Addon repository and install the Linuxserver.io repo.

    Then go to addons, install from repository, Linuxserver.io addons, services and you can find Boinc and [email protected]


    When you install either addon, it will first download and unpack the docker images, which can take some time. Be patient. You can watch the logs via the following commands

    Code
    journalctl -u docker.linuxserver.boinc -f
    journalctl -u docker.linuxserver.foldingathome -f


    Boinc: GitHub - linuxserver/docker-boinc

    Fairly heavy image, because the app has no webserver, instead we run guacamole to display the gui app in a browser. Once installed, you can access it at http://libreelecIP:8088

    Switch to Advanced view in the menu, because some settings windows aren't displayed properly in the simple view.

    Add the [email protected] project for COVID-19 research.

    Works on x86_64, arm and aarch64. But not all projects support arm and aarch64


    [email protected]: GitHub - linuxserver/docker-foldingathome

    Lighter image, as it has its own webserver. Once up, you can visit its relatively simplistic webgui at http://libreelecIP:7396

    For more fine grained control, you can access it remotely from another machine that has FAHControl installed. The default port for that is 36330 and there is no password auth.

    Unfortunately, [email protected] is x86_64 only


    Now, get folding!! ;)

    It's not an iptables issue, it's a docker thing. You're likely putting the containers in the default bridge network, which doesn't allow them to connect to each other via container name as dns host name.


    The link you provided uses docker compose, which by default creates a "user defined bridge" network, which allows containers to connect to each other via container name.


    What you should do is, create a user defined bridge network via "docker network create mynet"

    Then when you're creating the containers, select "mynet" as the main network.


    Here's a detailed explanation: Using Docker networks for better inter-container communication