Dent_

Been trying to get this docker going again and thought I would point out that the POSTGRES_PORT key has a space at the begining that causes startup to ignore port #. It does not appear to be a problem if you are using the default port but, if like me you are using a non default port number it ignores and uses default of 5432.

I had to add a variable in the mealie docker settings for BASE_URL with the url used to get to my instance.

Not right now. According to Photoprisms project roadmap multi user support is now in sponsored development but no current ETA that I have found.

Thanks, I figured it was probably a variable I missed. Didn't think about amount of php processes to DB connections. As for the increase in connections I did increase the shared_buffers memory as well as the worker and maintenance variables based on your template and explanation at the same time. Thanks again for your guide.

Thanks for this. Great help for those of us who like to play but do not have a lot of exp with the deeper end of servers. I have not used all the guides(yet) but got my way through some of them. I do have a couple questions. You said you have a larger Nextcloud server on your postgres DB. Did you have to substantially increase the max_connections? Once I installed max_connections was set to 100 (default). My nextcloud docker when running with the maps app installed would start throwing out Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[08006] [7] FATAL: remaining connection slots are reserved for non-replication superuser connections and Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[08006] [7] FATAL: sorry, too many clients already. One of the searches I found stated that it could be client connections are not closing on the backend side and as a temp measure to increase max_connections. I increased to 200 then hit the NC server with a maps refresh and it quickly rose from 8-9 connections to 127-129 connections to the DB (watched through the query tool in pgAdmin) but then dropped back down to 8-9 connections not long after. I ask this as I did not find much in my google search with this error related to Nextcloud so I assume I either misconfigured something or, everyone else is just smart enough to increase max_connections to begin with. Also, in the Nextcloud guide you referenced a "go" file for DB tuning. Where would one find this, or if I missed a guide that has this mentioned in more detail can you point me in its direction? Would like to read up on that some more. Attached image with the database errors. I know there are other errors as well (I think they are directly related to the maps app) that I will look into later but I am focused on the DB errors as those one bring Nextcloud to a halt.

Yup, this is all it was, thanks for the help.

CrushFTP Further playing around, I can access crush on my test server using the edge (chrome) browser, I cannot access crush on my main server through edge. The crushFTP.log looks fine until I try and access crush on my main server then it gets those long log entries. Confusing part, I can access crush on my main server and test server using chrome browser just fine.

Not sure what is wrong, but I am sure it is something with my server. I installed the crushftp docker on my test server with the same port assignments and network settings (stock) and seems to work great.

It is in bridge, I only changed a couple port numbers that were already being used by other dockers.

CrushFTP.log Here is the log, only thing I changed is the wan IP. Question, if I change the ports that I want to use in unraid during setup is there a config file somewhere that I also have to edit?

I probably did something to muck this up. Once installed and the container starts I cant access the ui. When looking at the log this is what I get. Is there a permission I am missing? Unzipping CrushFTP... Creating default admin... Admin user written to:./users/MainUsers/ cat: can't open '/etc/system-release': No such file or directory CrushFTP is not currently running... cat: can't open '/etc/system-release': No such file or directory Starting CrushFTP... OK

I clicked on vnc.html and it brought up the VNC page in the browser, then clicked connect and it started the rest of the install process.

Thanks for all the help

Yup, missed that some how, removed and recreated the SMB share but sailed right past the remotes folder instead of the disks folder. I think what got me is that the original folder under disks is still there so I just automatically thought there it is lol.

I seem to be having the same issue as cferra and squid. I can see the full network share if I click on the mount point, but I can only see one folder inside the docker (should be two) and none of the subfolders. I also updated UD to 2020.10.21. unraid-diagnostics-20201211-1710.zip

NVM, found out that remote access check does not work when using custom URLS on the plex forum.

After setting up plex behind the reverse proxy does the Remote Access always show the Red ! and say not avaliable outside your network? Or does it mean I still have a problem to sort out?

Did you ever figure out a solution to this?

I am working away from home right now but will try and remember when i get home, about three weeks but everything is stock. i actually just pulled the usb key out of the old server and resetup the array with the same drive order, changed the network options and it all just worked. I wanted stability so I never messed with overclocks besides setting memory to XMP profile(or AMP for AMD I think) to get it up to 3200Mhz. As for EFI or legacy I am positive it is set UEFI. The motherboard being used is the Asrock TRX40 creator. As for the network I have not capped that yet as so far I have been transferring to the array of spinning disks and have not been able to max out the 10Gbit connection, but it has maxed out the spinning disks. If I can remember anything else I will let you know.

I know it is a little different but I have a threadripper 3960x running for almost two months with no problems so far. The only minor issue I am having is getting temps from cpu and that is apparently a driver issue(or lack of driver) for the newer sensors.

Sorry it has been a while since I made this post but life has been getting in the way of playing with this new setup. I was recently asked a question about the Asrock board and I tried to answer as best I could and thought I would pate that answer here in case anyone else was curious. As stated in this reply if anyone has questions I will do my best to answer but I am no expert, just someone who like to play. So far (only really been running it for a week now) everything is looking very nice. I currently have multiple dockers (Unmaniac, unifi controller, tatulli, ombi, sickchill, radarr, nextcloud, and a few others, Plex will be migrated to it in the soonish future) as well as a VM with a 980 passed through to it, and one more lightweight VM running True Command for freenas and it has not faltered...yet, again it has only been a week. I did have problems getting the Gaming VM to start with the 980 and its audio passed through. I currently have an old amd card in slot one and the 980 in slot 3 (both full x16) which I did not want. I wanted only the 980 in slot one and no other vid card to save on the PCIe slots. In the end I had to add a line to a config file for the 980 to pass through. In the future I will probably try and make it work with just the one card again. As for the board I was a little concerned with the power phases as a lot of other boards have 16 and if I recall this one has 8, but so far no issue at all, and I don't plan to do any big overclocks as I want stability so should not be an issue. After I bought the board Wendell at Levelone techs did a review on it and set aside a lot of my worries. I will put the video at the bottom. I am by no means an expert in any of this, just some one who likes to play around so if there are more questions I will do my best to answer, but I may not always be right as a heads up. As for IOMMU groupings here is what I see under system devices IOMMU group 0:[1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 1:[1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2:[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 3:[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4:[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5:[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 6:[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7:[1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 8:[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 9:[1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 10:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 11:[1022:1490] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 0 [1022:1491] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 1 [1022:1492] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 2 [1022:1493] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 3 [1022:1494] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 4 [1022:1495] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 5 [1022:1496] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 6 [1022:1497] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 7 IOMMU group 12:[1002:68f9] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:aa68] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] IOMMU group 13:[1022:148a] 02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 14:[1022:1485] 03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 15:[1022:148c] 03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller IOMMU group 16:[1022:1482] 20:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 17:[1022:1482] 20:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 18:[1022:1482] 20:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 19:[1022:1483] 20:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 20:[1022:1482] 20:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 21:[1022:1482] 20:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 22:[1022:1482] 20:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 23:[1022:1484] 20:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 24:[1022:1482] 20:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 25:[1022:1484] 20:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 26:[10de:13c0] 21:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 980] (rev a1) [10de:0fbb] 21:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) IOMMU group 27:[1022:148a] 22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 28:[1022:1485] 23:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 29:[1022:1486] 23:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 30:[1022:148c] 23:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller IOMMU group 31:[1022:1487] 23:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller IOMMU group 32:[1022:1482] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 33:[1022:1483] 40:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 34:[1022:1483] 40:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 35:[1022:1483] 40:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 36:[1022:1482] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 37:[1022:1482] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 38:[1022:1483] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 39:[1022:1482] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 40:[1022:1482] 40:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 41:[1022:1482] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 42:[1022:1484] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 43:[1022:1482] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 44:[1022:1484] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 45:[1022:57ad] 41:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 46:[1022:57a3] 42:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 47:[1022:57a3] 42:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 48:[1022:57a3] 42:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 49:[1022:57a3] 42:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 50:[1022:57a4] 42:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:1485] 47:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:149c] 47:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 47:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 51:[1022:57a4] 42:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 48:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 52:[1022:57a4] 42:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 49:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 53:[1b21:3242] 43:00.0 USB controller: ASMedia Technology Inc. Device 3242 IOMMU group 54:[1d6a:07b1] 44:00.0 Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02) IOMMU group 55:[8086:2723] 45:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) IOMMU group 56:[10ec:8125] 46:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 01) IOMMU group 57:[8086:f1a8] 4a:00.0 Non-Volatile memory controller: Intel Corporation SSD 660P Series (rev 03) IOMMU group 58:[8086:f1a8] 4b:00.0 Non-Volatile memory controller: Intel Corporation SSD 660P Series (rev 03) IOMMU group 59:[1000:0072] 4c:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) IOMMU group 60:[1022:148a] 4d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 61:[1022:1485] 4e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 62:[1022:1482] 60:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 63:[1022:1482] 60:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 64:[1022:1482] 60:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 65:[1022:1482] 60:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 66:[1022:1482] 60:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 67:[1022:1482] 60:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 68:[1022:1484] 60:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 69:[1022:1482] 60:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 70:[1022:1484] 60:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 71:[1022:148a] 61:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 72:[1022:1485] 62:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

So far I have not found an option to select which pcie slot is used for the boot GPU on the Asrock Creator TRX40. It is possible that I overlooked something but I do not believe it is there.

So not being able to find much other than one site that compared the asrock creator and msi creator I decided to go with the asrock creator and see if it has the options I want, such as setting the GPU slot for boot. If not, well darn haha.

You bet I am, didn't even think of that so thanks for pointing it out.

I know they are still very new but I am wondering if anyone has info on the various trx40 boards and their compatability with unraid and hardware pass through, iommu groupings and such. I am currently looking at the asrock trx40 creator, or the msi creator trx. I already have all the other parts for my upgrade including the 3960x, but it seems the mobo is the hardest part to decide on, and find. Leaning toward the asrock because I believe that was a board that level1 had good luck with the iommu grouping in the past, but for the price difference I would also like that 4 x nvme to pcie card.