Dimtar

Hi all. Just installed the Matomo container, it started but if I try to access the web interface I get this: Unable to read INI file {/opt/bitnami/matomo/config/config.ini.php}: Syntax error in INI configuration: Your host may have disabled parse_ini_file().

Neither of those options are good, I will do a bit more testing and see what I find. Thanks for your time.

Yes, yes and yes. 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core P rocessor Host Bridge/DRAM Registers (rev 07) Subsystem: Gigabyte Technology Co., Ltd Skylake Host Bridge/DRAM Registe rs Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) DeviceName: Onboard IGD Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI Con troller Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series C hipset Family Thermal Subsystem (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H Thermal subsyste m 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chips et Family MEI Controller #1 (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H CSME HECI 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 C hipset SATA Controller [AHCI Mode] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H SATA controller [AHCI mode] Kernel driver in use: ahci Kernel modules: ahci 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1) Kernel driver in use: pcieport 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) Kernel driver in use: pcieport 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) Kernel driver in use: pcieport 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1) Kernel driver in use: pcieport 00:1d.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 (rev f1) Kernel driver in use: pcieport 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H LPC Controller 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Fami ly Power Management Controller (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H PMC 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H HD Audio 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (re v 31) Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H SMBus Kernel driver in use: i801_smbus Kernel modules: i2c_i801 02:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] Kernel driver in use: pcieport 03:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] Kernel driver in use: pcieport 03:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] Kernel driver in use: pcieport 03:02.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] Kernel driver in use: pcieport 03:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] Kernel driver in use: pcieport 06:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Rid ge] Subsystem: Device 2222:1111 Kernel driver in use: xhci_hcd 08:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Cont roller (rev 10) Subsystem: Gigabyte Technology Co., Ltd Killer E2400 Gigabit Ethernet Co ntroller Kernel driver in use: alx Kernel modules: alx 0a:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Cont roller SM981/PM981/PM983 Subsystem: Samsung Electronics Co Ltd Device a801 Kernel driver in use: nvme Kernel modules: nvme, rsnvme

Hi all. Just put a new unraid box together, I bought a 2nd hand 1050 TI to go with it. I'm running 6.8.3 and have installed the Nvidia drivers/version twice now incase I did it wrong the first time. I'm getting this: I've tried the two PCIE slots the box has but it doesn't seem to pick up the card at all? The fan on the side of the card is spinning so I know it at the very least has power. Not sure what to do next.

Make sure that bridging is turned on in your Settings > Network You will to stop the array to make the change.

Did you work this out or are you still stuck? This all looks right, did you try wiping the folder and starting it again?

So yours doesn't look like this?

That is the right one, it has a slightly odd name but it’s right.

This has been picked up by a new dev, not sure if we want to see this updated or not as an alternative.

The files are owned by another user which is why you don't have permission via the network. Given Nextcloud is a data storage tool, I would personally doing my moving etc. via the NC desktop sync tool or via the web interface. I realize its slower but I would want to do it officially so NC has a record of all the changes etc. If you're set on doing it via a network share you might have to muck with permissions and that break your NCP install so you'll have to research that yourself. Both port 80 and port 443?

Did you solve this?

You can upgrade through the web interface but I don't think NC themselves are allowing web upgrades yet, you may have to wait.

Is this a new install or a working installation that has broken?

I used a password generator with 20 characters, I think you might be on to something with that. Thanks, will remember that.

I re-did the mount but it didn't work. I deleted the user on the end SMB server and re-created them. It seems happy now, not sure what happened exactly as the user was enough to list the shares but I doubt this was the fault of the plugin. Its all working, thanks for a great plugin.

The Unraid log Tools->System Log. Dec 2 02:47:03 Tower kernel: CIFS VFS: Send error in SessSetup = -13 Dec 2 02:47:03 Tower kernel: CIFS VFS: cifs_mount failed w/return code = -13 Dec 2 02:47:03 Tower unassigned.devices: Mount of '//192.168.25.78/RalphBackup' failed. Error message: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) This confuses me but I will check the permissions again.

Whenever I click the log its empty.

I am running this plugin on the latest 6.8 RC7 I can connect to an SMB share but mounting doesn't work, not sure what I am doing wrong?

My understanding is that it allows a higher lever of access then a regular container so you should only do it for containers you trust. Others on this board would likely have more information.

I believe you need it for the container to work right but it seems I didn't make it the default in the template, i'll correct that now but you should turn it on and see what happens.

@Vesko I am not sure what you're trying to do specifically but you should be able to just read the files off the array from the folder you told the container to use. I wouldn't recommend trying to move the NCP folder, you're likely to just break the container. If you want to store the files elsewhere select another folder on the array to use, instead of the appdata folder (in the container template). Thats just something I setup as the default. I've never used the other Nextcloud docker container for long so I can't comment on performance sorry. Technically given this is docker you can run both side by side but I think you would just be adding complexity for no benefit. I would pick one and stick with it. If you're happy with the LinuxServer Container I would just stick with that.

@superslider it looks like not all the IPs match? You’re asking the container to run on 210 but telling NCP to allow it on 218, unless I am reading that wrong? Reading it back I see what you have done, you have followed the instructions but all the IPs need to match I think. I will update the wording in the template.

That’s correct, most containers in unraid allow you set two locations but in this container you can’t. I appreciate this approach doesn’t work for everyone.

Can you share a screenshot of your settings in the template?

You can change the location in the template when you're setting it up, I defaulted it to /mnt/user/appdata/nextcloudpi but you can pick anyway as with most docker containers.