Problem/Motivation

Access to files stored on NAS only with SMB 1 possible
With SMB 1 deactivated on NAS console reports “error opening file” … “stale file handle (116)”

Expected behavior

Use cifsversion according to setting in configuration - e.g. cifsversion: ‘3.0’

Actual behavior

Access to files on NAS only with SMB 1 activated on NAS possible.
Looks like Addon is set to SMB 1 permanently.

Steps to reproduce

???

Proposed changes

???

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

My environment:

Add-on version: 2.4.2-dht2
You are running the latest version of this add-on.
System: Home Assistant OS 5.10 (armv7 / raspberrypi3)
Home Assistant Core: 2021.1.5
Home Assistant Supervisor: 2021.01.7
NAS: Firtzbox AVM 7490 latest firmware

Problem/Motivation

Installed the Plex add-on, turned off the Protected mode. The install is on a RaspPi4, under 2021.12.07. When starting the Add on, I get the error:
"Failed to start add-on
Port '1900' is already in use by something else on the host."

My router is a Unifi Dream Machine. I also have Plex server running on a Mac Mini on my network, but it is disabled as I set up the HomeAssistant instance.
I has also previously installed the main Plex Add-on, but when I discovered that I could not get it to work with my NAS, I uninstalled and rebooted the HA instance.

Expected behavior

No Error

Actual behavior

Error message on start of the add on:
"Failed to start add-on
Port '1900' is already in use by something else on the host."

Steps to reproduce

1. Point to the repro.

2. Install Plex and NAS
3. Configure the yaml
4. Turn off Protected mode
5. Press start button
   Result: Error

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I have a old NAS which only connects through classic CIFS/SMBv1 protocol and because of that I can't connect on add-on.
Allow configure SMB protocol version on add-on config

Expected behavior

Connect successfully with SMBv1 servers using vers=1.0 on mount arguments.

Actual behavior

I can't set Samba protocol version using current config options

Steps to reproduce

• Configure a v1.0 Samba Server
• Try to connect
• Check logs for mount error(13): Permission denied

Proposed changes

• Add an option for cifs version on plex/config.json

"options": {
  "cifsversion": "3.0"
},
"schema": {
  "cifsversion": "str"
}

• Get config on plex/rootfs/etc/services.d/plex/run and use it on mount

CIFS_VERSION=$(bashio::config 'cifsversion')
mount -t cifs -o username=$CIFS_USERNAME,password=$CIFS_PASSWORD,vers=$CIFS_VERSION $disk /$disk && \

Addon had no updates for a very long time.
In HassOS I have "Plex Media Server with NAS Current version: 2.4.2-dht3 (Changelog)"

Currently, the Plex version in the addon is 1.21.3.4046, but the newest Plex is 1.25.9.5721

hi there
first: thanks a lot for this addon, mounting some network folder is what I missed in offical addon
question: if I do a snapshot by HA of this addon all network folder will be backup too. is there a way to exclude them?
thanks for any hints.

Problem/Motivation

First of all, thank you for your work. I am a very grateful user of Samba NAS and Plex Media Server with NAS addons.

I am running in an issue with Plex Media Server with NAS. The addon can't mount a network disk anymore. It worked well before. As far as I can tell, this problem started appearing with the Core 2021.2.3.

Expected behavior

[12:45:00] INFO: Starting the Plex Media Server...
[12:45:00] INFO: Network Disks mounting.. //192.168**/pms
[12:45:00] INFO: Mount //192.168**/pms
[12:45:00] INFO: Success!

Actual behavior

[12:45:00] INFO: Starting the Plex Media Server...
[12:45:00] INFO: Network Disks mounting.. //192.168**/pms
[12:45:00] INFO: Mount //192.168**/pms
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[12:45:00] WARNING: Protection mode is ON. Unable to mount external drivers!

Steps to reproduce

Start the addon with a networkdisks set up. The //192.168**/pms is mounted using your SambaNAS addon.

claim_code: **
webtools: true
networkdisks: - //192.168**/pms
cifsusername: **
cifspassword: **
cifsversion: '3.0'

Proposed changes

I used docker exec -it addon_**_plex /bin/bash to investigate the problem:

• The folder /192.168**/pms is correctly created and the permissions are correctly set up.
• I tried to execute the mount request and ran into the same problem, even when trying to use a different directory.

The same request (mkdir -p /192.168**/pms && chown -R root:root /192.168**/pms && mount -t cifs -o username='**',password='**',vers=3.0 //192.168**/pms /192.168**/pms) runs perfectly in the homeassistant container. This makes me think that the problem comes from the docker container running the addon missing some permissions or capabilities.

Same as with the Samba NAS addon problem you solved by adding a apparmor.txt, my guess would be to add something similar so the mount capability is added to the docker container running plex.

Context (Environment)

Rpi4
Core Version: core-2021.2.3
Supervisor Version: supervisor-2021.02.11
Operating System: Home Assistant OS 5.11
Addon version : 2.4.2-dht2

Problem/Motivation

I get "Mount Error 13 = Permission denied" when trying to connect. I can connect to the disk share without problem from any other PC. This worked perfectly until I upgraded the Samba NAS Server add-on, but it doesn't seem to be a problem with that add-on.

Steps to reproduce

Plex addon config:
claim_code: claim-*******************
webtools: false
networkdisks:

• //192.168.0.2/ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E7XY9YSL-part1
  cifsusername: username
  cifspassword: password
  cifsversion: '3.0'

Port 1900 is changed to 1901

Problem/Motivation

If i start the add-on with every configuration the problem are the same:

WARNING: Protection mode is ON. Unable to mount external drivers!

All my media are on the nas (qnap with nfs, cifs and smb activate)...

Expected behavior

After disable protection mode the add-on works

Actual behavior

here the entire log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Plex Media Server with NAS
 Recorded media, live TV, online news, and podcasts ready to stream.
-----------------------------------------------------------
 Add-on version: 2.4.2-dht2
 You are running the latest version of this add-on.
 System: Home Assistant OS 5.10  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.1.5
 Home Assistant Supervisor: 2021.01.7
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] plex.sh: executing... 
[cont-init.d] plex.sh: exited 0.
[cont-init.d] webtools.sh: executing... 
[cont-init.d] webtools.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[20:36:54] INFO: Starting the Plex Media Server...
[20:36:54] INFO: Network Disks mounting.. \172.20.57.253\Multimedia
[20:36:54] INFO: Mount \172.20.57.253\Multimedia
mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[20:36:54] WARNING: Protection mode is ON. Unable to mount external drivers!

this the config:

claim_code: mycode
webtools: false
networkdisks:
  -  \\mynasip\multimedia
 (No need share user and password)

for the networkdisks i have try some option like using:

• \\mynasip\multimedia

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Plex Media Server with NAS
 Recorded media, live TV, online news, and podcasts ready to stream.
-----------------------------------------------------------
 Add-on version: 2.4.2-dht2
 You are running the latest version of this add-on.
 System: Home Assistant OS 5.10  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.1.5
 Home Assistant Supervisor: 2021.01.7
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] plex.sh: executing... 
[cont-init.d] plex.sh: exited 0.
[cont-init.d] webtools.sh: executing... 
[cont-init.d] webtools.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[00:30:37] INFO: Starting the Plex Media Server...
[00:30:37] INFO: Network Disks mounting.. \\172.20.57.253\Multimedia
[00:30:37] INFO: Mount \\172.20.57.253\Multimedia
mount.cifs: bad UNC (\\\172.20.57.253\Multimedia)
[00:30:38] WARNING: Protection mode is ON. Unable to mount external drivers!

• //mynasip/multimedia

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Plex Media Server with NAS
 Recorded media, live TV, online news, and podcasts ready to stream.
-----------------------------------------------------------
 Add-on version: 2.4.2-dht2
 You are running the latest version of this add-on.
 System: Home Assistant OS 5.10  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.1.5
 Home Assistant Supervisor: 2021.01.7
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] plex.sh: executing... 
[cont-init.d] plex.sh: exited 0.
[cont-init.d] webtools.sh: executing... 
[cont-init.d] webtools.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[00:32:10] INFO: Starting the Plex Media Server...
[00:32:10] INFO: Network Disks mounting.. //172.20.57.253/Multimedia
[00:32:10] INFO: Mount //172.20.57.253/Multimedia
mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[00:32:14] WARNING: Protection mode is ON. Unable to mount external drivers!

Plex server update

(Plex server out if date)

to be able to manually install the Plex media server.spk

(Have a button in hassio add-on to install spk)

can't find how to update

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(Add upload/install spk button)

Problem/Motivation

Can't install

(Why the issue was filed)
Failed to install add-on
Can't install ghcr.io/lbouriez/addon-plex/amd64:dev: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=dev&fromImage=ghcr.io%2Flbouriez%2Faddon-plex%2Famd64&platform=linux%2Famd64: Internal Server Error ("manifest unknown")

Expected behavior

Failed to install add-on

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I set Protection Mode Off.

Expected behavior

Connects to Drive.

Actual behavior

Shows in Log that Protection Mode is ON and that cannot connect.

Steps to reproduce

I installed, set Protection Mode OFF but in Log shows it's On

Proposed changes