Posts by Thormir84

For hardware transcode with Plex, you need a license (Plex Pass); what model of GPU are installed in your NAS?

In Docker, the syntax for Intel's GPU (for example) is:

devices:
  - /dev/dri

Probably, if you dont need any type of transcode, there's no particular requirements.

Plex Media Server Requirements | Plex Support

Whether you want to run your Plex Media Server on your every-day computer, you’re looking to use a dedicated computer,...

support.plex.tv

La sezione ACL, se non sai bene cosa fai, è meglio non toccarla; per gli utenti usa la sezione privilegi o si rischiano danni.

La mia installazione è su un "normale" PC e conosco poco dei Raspberry; che guide hai seguito per l'installazione? L'errore sembra indicare che qualcosa a livello di sistema non funziona come dovrebbe.

Ah ok.

No, when you create a RAID from scratch, you have to re-initialize the disks; all data will be lost during the operation.

NOTE: Make attention with a RAID0; if one of the two disks fail, all data will be lost.

Mmmm but if the "Backup-Box" have only a 1x16TB, how you had created a RAID0?

Quote from carlo.coin

Good morning,

in the attempt to install the plugin in question there is an error situation that prevents the procedure from being completed. See attached image.

Can you help me solve the problem?

Thank you

It seems a problem with the DNS, "could not resolve etc...".

Quote from Soma

You still haven't answered the main question: what is the reason to have a RAID1 ?

If you want to have a full disk copy of your DATA on "disk1" to "disk2", just mount "disk2" on OMV and run a scheduled job (every x time depending on the amount of writing/increase of volume DATA) as simple as rsync -a /path-to-disk1/ /path-to-disk2/

This is a nonsense for me.

If you have a rsync's copy of a whole disk and the main disk fail, all services like, for example, docker's containers, will go down cause the path will not be reachable anymore.

With a RAID1 config the "/srv/dev-disk-by-uuid/" is the same for the 2 disks, 'cause they will merge in a "unique device" so, if one of them fail, the system stays up.

Yes, if something goes wrong the error will replicate throught the 2 disks, but backups are here for a reason.

With Owncloud i have a scheduled task in OMV that works perfectly.

Quote from tomspatz

thx for u fast answer

Would u please explain this a little bit more?

I use compose.

On my nc machine i stop any docker container.

Om my fav. machine i should first copy my files there are used or created from my nc machine. f.e.

/srv/dev-disk-by-uuid-4e8222c0-3b1e-48cc-9dce-4fa7182095b1

Then install docker. And not pull any container?

and then?

Or am i on the completely wrong way.

Display More

You only need to copy all files of the container you want to move, then update the compose according to the new path and re-deploy it.

For example, if the old path of "./data/" was "/srv/dev-disk-by-uuid-4e8222c0-3b1e-48cc-9dce-4fa7182095b1/data/" you have to change this with the new "/srv/dev-disk-by-uuid......../" of the new server.

The UID in use does have R/W permissions?

This is an example of a stack:

version: "2.1"
services:
  plex:
    image: lscr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: bridge
    devices:
      - /dev/dri        #For Intel QuickSync's transcode
    ports:      
      - 32400:32400
      - 1901:1900/udp
      - 3005:3005
      - 5354:5353/udp
      - 8324:8324
      - 32410:32410/udp
      - 32412:32412/udp
      - 32413:32413/udp
      - 32414:32414/udp
      - 32469:32469
    environment:
      - PUID=1005
      - PGID=100
      - VERSION=docker
      - PLEX_CLAIM=MY_PERSONAL_TOKEN
      - ADVERTISE_IP=http://SERVER_IP:32400
    volumes:
      - /srv/dev-disk-by-label-DATI/AppData/Plex/config:/config
      - /srv/dev-disk-by-label-DATI/AppData/Plex/transcode:/transcode
      - /srv/dev-disk-by-label-DATI/Media:/media
    restart: always

Yes, it's possible.

After the hardware's change you have to run omv-firstaid from console, and re-initialize the lan adapter.

With the adapter configured as MAC_VLAN the container cannot access the host or other containers with bridge or host adapter and vice-versa.

If i remember correctly, is for security reasons.

Quote from haemburg2021

I delete the old ip in the fritzbox. the mainboard get a new ip. but if I go to webbrowser with this new ip, I see the authentication page of the mainboard.

I see the authentication page of the mainboard.

What!?

Quote from Mptek

I also got a message on my phone. The remote address is 192.168.1.223. User agent: Mozilla/5.0 (Windows NT 10.0 Win64;x64) AppleWebkit/537.36(KHTML, like Gecko)Chrome/105.0.0.0 Safari/537.36.

I can no longer login to OMV and can not ssh into my pi.

But in this case, the "remote address" is a local address of your LAN.

There's no public IP like 192.168.1.X.

I think that is a "copy&paste" problem.

Try to delete the blank spaces between "70" and "P" of "PAPERLESS_FILENAME_FORMAT".

After this, with the cursor between "70" and "P", press backspace; make sure that there's no space between the "P" and the "b" of "db".

Now, press enter and press space until "PAPERLESS_FILENAME_FORMAT" is align with the others variable.

You cannot use disks not formatted.

In "Storage" -> "Disks" you have to select the disk then click on "Reset to factory" (on OMV6); WARNING: All data will be permanently erased.

After this, you can select the disk and make a new file system.

My compose:

version: "2.1"
services:
  plex:
    image: lscr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: bridge
    ports:      
      - 32400:32400
      - 1901:1900/udp
      - 3005:3005
      - 5354:5353/udp
      - 8324:8324
      - 32410:32410/udp
      - 32412:32412/udp
      - 32413:32413/udp
      - 32414:32414/udp
      - 32469:32469
    environment:
      - PUID=1005
      - PGID=100
      - VERSION=docker
      - PLEX_CLAIM=MY_SECRET_TOKEN
      - ADVERTISE_IP=http://OMV_IP:32400
    volumes:
      - /srv/dev-disk-by-label-DATI/AppData/Plex/config:/config
      - /srv/dev-disk-by-label-DATI/AppData/Plex/transcode:/transcode
      - /srv/dev-disk-by-label-DATI/Media:/media
    restart: always

Bridge network instead of host to avoid ports conflict.

Quote from FragoulisNaval

you use tautuli with jellyfin? How have you managed to make them work together?

Nah, Tautilli works with Plex; i use bot Jellyfin and Plex, because the first one is more "flexible" when i'm not at home.

I prefer Plex, but with a dynamic public IP i can't reach the server even with a reverse proxy (with the app, but work fine with the web ui).

My list:

What kind of image is "lscr.io/linuxserver/plex" ?

What is "/Server" path?

I use this compose that works without any issue:

version: "2.1"
services:
  plex:
    image: ghcr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: bridge
    ports:      
      - 32400:32400
      - 1901:1900/udp
      - 3005:3005
      - 5354:5353/udp
      - 8324:8324
      - 32410:32410/udp
      - 32412:32412/udp
      - 32413:32413/udp
      - 32414:32414/udp
      - 32469:32469
    environment:
      - PUID=1005
      - PGID=100
      - VERSION=docker
      - ADVERTISE_IP=http://SERVER_IP:32400
    volumes:
      - /srv/dev-disk-by-label-DATI/AppData/Plex/config:/config
      - /srv/dev-disk-by-label-DATI/AppData/Plex/transcode:/transcode
      - /srv/dev-disk-by-label-DATI/Media:/media
    restart: always