Posts by elonesna

This would work fine on CoreELEC and the system will boot with "storage" on the external drive:

systemctl stop kodi

e2label /dev/sda1 "STORAGE"

e2label /dev/mmcblk1p2 "EXT-STORAGE"

reboot

I don't know if it will work in LE.

Forget about mysteries, ghosts and hardware failures in your RPi. Go to settings and delete your WiFi connection, then connect again and enter your password again. If the first time doesn't work, delete the connection again and try again. If it continues to fail, it is most likely that your WiFi is subject to interference from other WiFi: Install a WiFi analyzer on your smartphone to find out what is happening and finally change the WiFi broadcast channel on your router.

I'm also waiting for a solution for your problem, meanwhile I'm still with LE 9.2.6. I have also seen that with a desktop x86_64 Linux distribution (Ubuntu or Mint) and compiling the drivers, and installing my entire collection of docker services, tvheadend works fine but I am too lazy to abandon LE because it works very well, it is very robust and I don't know corrupts, and backups work just fine.

This is the SSH command to install docker firefox. I tried this a year ago and it worked.

docker run -d \

--name=3000-firefox \

-e PUID=1000 \

-e PGID=1000 \

-e TZ=Europe/Paris \

-p 3000:3000 \

-v /storage/.config/dockers/firefox:/config \

--shm-size="1gb" \

--restart unless-stopped \

linuxserver/firefox

Using a wireguard client in LibreELEC with a DDNS server can cause a terrible headache. In CoreELEC it is very easy to do this in the following way:

1.- Install entware, command: installentware

2.- Install entware-wireguard, commands:

opkg install wg-quick

opkg install wireguard-tools

opkg install wireguard-go

3.- Create wg0 as file /opt/etc/wireguard/wg0.conf with the content similar to this:

[Interface]

Address = 10.10.10.5 # local-ip-of-wg-interface

PrivateKey = ... # private-key

ListenPort = 51820 # wg-port

[Peer]

PublicKey = ... # public-key

Endpoint = <dynamic-dns-of-server>:51820

AllowedIPs = 0.0.0.0/1,128.0.0.0/1 # instead of 0.0.0.0/0

4.- Start the wireguard service with the command: /opt/bin/wg-quick up wg0

Note.- If you don't want to redirect all traffic to wireguard interface and want to keep the default route, then you can use

AllowedIPs = 10.10.10.0/24, where 10.10.10.0 is the wireguard subnet

One thing is the setting of the virtual keyboard and another thing is the setting of the physical keyboard. Check out the settings!

What you say does not make sense, talk to the administrator of your zattoo service

(I run a pvr hts service for my family, and I automatically restart the server every day at seven in the morning to pick up any connected clients)

I don't know if I understood your problem, but if you add

-v /storage:/storage \

-v /media:/media \

to the installation command you will be able to access almost any LibreELEC directory, or your external storage, from within the docker transmission service

Tip: Forget about internal docker directories /storage/.kodi/userdata/addon_data/service.system.docker because you will never need them for anything

I use three protection systems on my home network: pihole with over 1.5 million domains blocked, skynet firewall with over 40,000 IP addresses (and over 1,700 ranges) blocked, and Trend Micro protection. Well, pihole protection system of my home network prevent me from accessing mullvad.net, and when I add this domain to the white list, then the Trend Micro protection of my router appears. In short mullvad.net is unsafe for me.

My "RTNETLINK answers:File exist" errors are fixed by replacing

AllowedIPs = 0.0.0.0/0

by

AllowedIPs = 0.0.0.0/1,128.0.0.0/1

This is explained at https://www.wireguard.com/netns but I do not know the reason for this error, perhaps there is someone here who is able to explain it to us.

I have been using X-Plore for many years, it supports SMB, FTP, WebDAV, and SFTP protocols

I think your solution is not good, LibreELEC shutdown already does this. I think the problem is in the execution code of the containers that fail because it is not taken into account that they are executed asynchronously in parallel to the execution of LibreELEC, which is the one that has control of the shutdown. For me, I am not a programmer, the solution consists of inserting commands that prevent or delay the shutdown until the most critical phases are completed within the containers.

I have understood what your RPi4 configuration is but I don't understand your questions.

As far as I know LibreELEC only manages a single user: root. Kodi can handle something it calls 'profiles' that allow you to configure media content for other users, for example children; the latter has nothing to do with data access permissions, because they are always from the root user.

If you connect your hard drives to a USB port it will be impossible for you to restrict permissions and assign read-only to local users. Even remote access to LibreELEC from SSH or SAMBA is done from the root user.

If you connect your hard drives to a network through a NAS then you may be able to create users and access permissions to the content of your hard drives.

Does this answer your questions?

The use of docker containers when they have hardware access can interfere with the operation of LE, for example, I would never install a tvheadend docker container with the LE tvheadend addon, the reasons are obvious.

Instead of redirecting the sound output from the docker container to the hardware, why not redirect the output to a port that can be captured, for example, by the LE player to send the output to the audio hardware? I am successfully using this technique with television content for complex playlist processing and it works very well.

Go back to studying the installation of the nextcloud server, when you have done this install the nextcloud client applications on your PC or on your smartphone or wherever you want. The nextcloud server is a data manager but you will not see anything because everything is encrypted. If you delete or lose a user's access keys, all storage for this user will be lost.

If you want to easily install the nexcloud server you can do it with 'docker' from the 'portainer' docker container, by creating a new 'Stack' named 'nextcloud' with the following content:

version: "3"
services:
  nextcloud:
    image: nextcloud
    container_name: 4080-nextcloud
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Paris
    volumes:
      - /storage/.config/dockers/nextcloud/config:/config
      - /media/<your-hard-disk>/nextcloud/data:/data
      - /media/<your-hard-disk>/nextcloud/var/www/html:/var/www/html
    ports:
      - 4080:80
  mariadb:
    image: linuxserver/mariadb
    container_name: 3306-mariadb
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=libreelec
      - TZ=Europe/Paris
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_PASSWORD=libreelec
    volumes:
      - /storage/.config/dockers/mariadb/config:/config
    ports:
      - 3306:3306
    restart: unless-stopped

(Note that web access is done via port 4080)

In short, also taking into account that the export of files for recovery is also laborious or very difficult if you have lost the access keys, for a home user I prefer a normal file manager. If you think of a method of data backup or synchronization, think of the power and simplicity of 'syncthing'.

Quote from marcusob

Is there a way to get write permissions, or even a better way to get write access to the hard drive on the libreelec Pi ?

I think the best solution for sharing a hard drive is to use a drakkan/sftpgo docker container. It is very easy to manage via web, it allows you to add and remove users and manage permissions and quotas, it has a problem: it is only compatible with x86-64 and arm64, but not with arm32v7. There is also the tabbyjun/sftpgo-arm32v7 container but I haven't tested it and the last update is four months ago.

The supported protocols of this server are: SSH/SFTP, FTP and WebDAV, and fail2ban protection can also be activated.

I use it on my LE x86-64 server, and WebDAV Remote Access from Kodi clients, File Manager from Linux, Cyberduck from Windows, and X-Plore from Android. It works very well.

For tvheadend to automatically recognize a SAT>IP tuner, it only needs to be turned on and on the same subnet or home network. You can also force the discovery of a SAT>IP tuner with the parameter "--satip_xml http://<satip-tuner-ip>:8080/desc.xml" for Digibit R1 or "--satip_xml http://< satip-tuner-ip>:38400/description.xml" for Digibit Twin, in the command line for tvheadend server startup.

The tuners, including Digibit R1, do not descrambling anything, this job is done by the tvheadend server and it is configured from the CAs section of this server.

I'm not sure but I think it's the only server that does this now besides the enigma2 systems.