Posts by aptalca

Yes, but make sure there is a space after -v and customize the paths accordingly

You shouldn't be editing the xml file. Use the addon settings on the gui

Quote from ferkator

One year later, but I have a question regarding this addon. I've been trying both Pi-Hole and AdGuard Home these past week to see how they worked. I kind of like AdGuard more, since I can use Cloudflare for DNS, but I have an important issue and it's that Chrome (or chromium based browsers) won't block ads on Android. I can see apps blocking ads, other browsers (the one that comes with MIUI) also do block ads, but Chrome and Samsung browser didn't.

I guess it's some kind of misconfiguration on my part? I'm using your Pi-Hole right now (which blocks everything) but I would really like to use AdGuard. Running this on some chinese TV box with libreelec installed, in case it helps.

Did you set up adguard with block lists?

You can add additional volume mappings in addon settings. You need to add them to additional docker arguments. And you need to use the full docker arg such as "-v /path/on/host:/custom/path/inside/container"

I'm not aware of a way to bring back dropped devices without a container restart with docker (unless you use the docker driver to mount them, such as nfs Use volumes | Docker Documentation )

You can also check out the status of the systemd service that mounts your drive to see if it failed and restarted or something like that and try and get to the root cause because an external drive shouldn't drop like that (smb maybe).

That likely suggests the mount is dropping or disconnecting temporarily. The issue is, after reconnect, docker doesn't detect it without a container restart.

I had a similar issue with a mounted smb share. Switched to docker mounted nfs, which doesn't drop (or maybe comes back properly).

While I have no idea why it may be happening, disabling and re-enabling the the addon will restart the container and the mount should come back (as long as it's reconnected on the host).

Can't you just do an upgrade through the gui?

You should probably do a backup first through libreelec settings and move it to a different device (perhaps flash drive)

The addon zip you downloaded is for kodi matrix and doesn't work on leia. You need to download the leia version

To use www as the nextcloud subdomain, edit the nextcloud proxy conf and change the server_name to www.* instead of nextcloud.*

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.

What do the logs show? Docker and systemd?

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)

Rpi is a low power device and nextcloud can be a bit heavy. Try to look through the logs to see what the bottleneck may be.

I should clarify, it was Rosetta@home's announcement that they would start handing out jobs for arm, but only for 64bit. Other projects on Boinc suppport 32bit arm.

Boinc's announcement about arm was a bit misleading. It got me excited at first as well. Turns out, they are now supporting arm64, not 32. Even though rpi4 has a 64bit chip, LE runs 32bit software on it (so does raspbian) and that's why it's a no go.

F@h is x86_64 only. Upstream doesn't support arm.

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).