peace-keeping-villa8590

has anyone got element-web working on unraid?

I'm trying to install element-web container and the container logs show this: 2025/08/03 06:32:49 [notice] 1#1: start worker process 67 2025/08/03 06:32:49 [notice] 1#1: start worker process 68 2025/08/03 06:32:49 [notice] 1#1: start worker process 69 /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh /docker-entrypoint.sh: Launching /docker-entrypoint.d/18-load-element-modules.sh /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh 20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh /docker-entrypoint.sh: Configuration complete; ready for start up ::1 - - [03/Aug/2025:06:32:54 -0700] "GET /config.json HTTP/1.1" 200 1894 "-" "Wget" "-" ::1 - - [03/Aug/2025:06:33:24 -0700] "GET /config.json HTTP/1.1" 200 1894 "-" "Wget" "-" ::1 - - [03/Aug/2025:06:33:54 -0700] "GET /config.json HTTP/1.1" 200 1894 "-" "Wget" "-" The last line keeps repeating and webui fails to connect. Maybe it's a ipv6 isssue?

I guess the fix was easier than I thought. Thank you... zfs snapshots. I'm glad I have it the script to turn folders into datasets and the script for auto snapshots. Saved me a lot of pain. Still have to reprocess all the files but saved me from going through the process of uploading the files remotely.

I got paperless up and running and then, after processing 2,000 + documents, the documents were still in the consume folder. So...... I deleted them. This happened a few days ago. For an unrelated reason, I had to restart the container and every time I start the container, it completely crashes my server. The logs say File "/usr/src/paperless/src/documents/consumer.py", line 148, in _fail raise ConsumerError(f"{self.filename}: {log_message or message}") from exception documents.consumer.ConsumerError: T93271.pdf: Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,539] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[7924107e-32c7-4baf-95ae-76757047cafe] received [2025-07-31 08:27:26,546] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[4a0e1579-57f3-40f2-8542-014482815659] received [2025-07-31 08:27:26,552] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[a59a85a7-4aea-49f1-b152-222694fca0b2] received [2025-07-31 08:27:26,558] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[a9ff1658-1414-4403-93e4-a9f238d39278] received [2025-07-31 08:27:26,564] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[13cdf592-2e15-44b5-a2d6-c6d6268e2f77] received [2025-07-31 08:27:26,571] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[cc8df2bf-556c-4d5d-824f-b94bbedbc869] received [2025-07-31 08:27:26,575] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,577] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[6c9453de-8d0f-4409-bb05-ec1e1fda1dfb] received [2025-07-31 08:27:26,573] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,573] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,574] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,576] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,577] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,579] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [2025-07-31 08:27:26,584] [INFO] [celery.worker.strategy] Task documents.tasks.consume_file[e787a14d-4df0-4905-8a7c-2c502a1e167d] received [2025-07-31 08:27:26,579] [ERROR] [paperless.consumer] Cannot consume /usr/src/paperless/consume/"radacted": File not found. [INFO] Shutting down granian Is there an easier way to resolve this issue? I managed to get my server back up and running by disabling paperless-ngx container.

In case someone else comes across this thread with the same question. I was overthinking it it pretty bad. In my case, I forwarded all the ports the container needed directly to the container except http and https. Those ports are forwarded to my proxy manager. This way worked for me.

No one?

Currently I have cloudflare routing my email traffic to my external IP and then ports are forwarded directly to my email servers local IP. This works great because everything else that's hosted on my server, is served with cloudflare tunnel. This has worked for a several years but I want to not use CF tunnels for a few other services due to the upload size limit. Is there a service I can use to chunk these uploads/downloads? I know I need to rout all the traffic to a reverse proxy (I have used NginXProxyManager in the past) but I'm lost when it comes to reverse proxy'ing a mail server. I'm not very experienced using a reverse proxy manger since CF tunnels is, to me, a giant EASY button when it comes to hosting services. What I'm looking for: What proxy manager can accomplish this? (I'm hoping NginXProxyManager can since it has a GUI) How to secure services with SSL? I know I can get different certificates from cloudflare to do this but It's a little confusing to set up. In the past, I used pfsense to route specific traffic to specific containers. i.e. service1.mydomain.xyz to container 1 and service2.mydomain.xyz to container 2 and so on. I'm no longer using pfsense; now using a unifi but I don't know if this is possible with unfi hardware?

Update on this issue. When i contacted a Unraid support a while ago, they told me this issue I’m having could potentially be resolved in future versions of Unraid due to newer kernel’s being added. I installed Unraid 6.1 beta 1 yesterday and did another speed test on the drives and…… they were right. It seems linux kernel 6.12.19 might have been what I needed all along. It could have been something else I guess.

I'm aware of the 32k hour firmware issue. All the drives I have are functional. Some of them have over 32k hours and some don't. They all report good health.

Thanks for the pointers. I looked at the link and found the 5067-6869 cable should be the correct cable. Two of these cables should give me 8 lanes to each SFF-8654 connection on the backplane. Quick question; Since I already have a 9400-16i and a Dell H300 (not sure if this one is compatible with NVME drives), is there a NVME enabler cable that will use two of the HBA's SFF-8643 connections into one SFF-8654 (slimSAS) for the backplane? This would use two ports (each with 4 lanes) of the HBA and combine them to give 8 lanes to one SFF-8654 connection. Using two of these cables would provide 16 total lanes to the backplane. I was going through the documentation for the 9400-16i and it only references cables for direct attaching NVME drives and not backplanes. There no sense in buying an HBA if I can use the one I already have. *Fingers crossed* I was really hoping to hear what people are already using in their servers. I'm sure I won't be able to afford the "most reliable" drives on the market. I'm more concerned with compatibility with Unraid. Reason being, last year I bought several PM1633 SAS drives and when I installed them, they were terribly slow and I still haven't been able to figure out why. I'm essentially replacing these drives with NVME U.2 drives.

I'm looking into installing some NVME U.2 drives into my server and wanted to ask the community on lessons they may have learned along the way? I'm in the planning phase and I'm mostly wanting to know what drives are popular among Unraid users? Current plans are: 9500-16i HBA I haven't picked out the cables yet but I would like some advice since I think I will need TRI-Mode SFF-8639 cables that are 1M? Silverstone backplane RAC-BP-304N to support U.2 NVME storage As for drives, I was hoping other users chime in as to what drives to avoid and what drives are popular to use with Unraid. I'm not sure if there are any know issues with certain drives. i.e. Dell EMC or other OEM branded drives Model:Custom M/B:Supermicro H12SSL-I Version 1.02 s/n BIOS:American Megatrends Inc. Version 3.0 Dated 07/22/2024 CPU:AMD EPYC 7302P 16-Core @ 3000 MHz HVM:Enabled IOMMU:Enabled Cache:L1 Cache: 1 MiB, L2 Cache: 8 MiB, L3 Cache: 128 MiB Memory:128 GiB DDR4 Multi-bit ECC (max. installable capacity 2048 GiB) Network:eth0: 10000 Mbps, full duplex, mtu 1500 Kernel:Linux 6.6.68-Unraid x86_64

/dev/sdd, /dev/sde and /dev/sdn

lshw -class disk *-disk:0 description: SCSI Disk product: X356_S16333T8ATE vendor: NETAPP physical id: 0.0.0 bus info: scsi@21:0.0.0 logical name: /dev/sdd version: NA04 serial: S2JVNA0H907615 size: 3576GiB (3840GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=528cfac9-d657-4817-9fa1-4808d340e9fe logicalsectorsize=512 sectorsize=4096 *-disk:1 description: SCSI Disk product: P1633N38 EMC3840 vendor: SAMSUNG physical id: 0.1.0 bus info: scsi@21:0.1.0 logical name: /dev/sde version: EQPC serial: NZNCAH204684 size: 3577GiB (3840GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=2adfb6d4-63f6-477e-be88-c2db15dce638 logicalsectorsize=512 sectorsize=4096 *-namespace:0 description: NVMe disk physical id: 0 logical name: hwmon2 *-namespace:1 description: NVMe disk physical id: 2 logical name: /dev/ng0n1 *-namespace:2 description: NVMe disk physical id: 1 bus info: nvme@0:1 logical name: /dev/nvme0n1 configuration: logicalsectorsize=512 sectorsize=512 wwid=eui.e8238fa6bf530001001b448b4857021a *-namespace:0 description: NVMe disk physical id: 0 logical name: hwmon1 *-namespace:1 description: NVMe disk physical id: 2 logical name: /dev/ng1n1 *-namespace:2 description: NVMe disk physical id: 1 bus info: nvme@1:1 logical name: /dev/nvme1n1 size: 931GiB (1TB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: guid=b06441ae-fba1-43cb-ab6d-e9b9403fada4 logicalsectorsize=512 sectorsize=512 wwid=eui.e8238fa6bf530001001b448b497bd861 *-disk:0 description: SCSI Disk product: HSCAC2DA2SUN1.6T vendor: HGST physical id: 0.5.0 bus info: scsi@22:0.5.0 logical name: /dev/sdk version: A29A serial: 001703J9P9WA 09WYP9WA size: 1490GiB (1600GB) capabilities: partitioned partitioned:dos configuration: ansiversion=6 logicalsectorsize=512 sectorsize=4096 signature=9f2f9b60 *-disk:1 description: SCSI Disk product: HSCAC2DA2SUN1.6T vendor: HGST physical id: 0.7.0 bus info: scsi@22:0.7.0 logical name: /dev/sdl version: A29A serial: 001701J9E3BA 09WYE3BA size: 1490GiB (1600GB) capabilities: partitioned partitioned:dos configuration: ansiversion=6 logicalsectorsize=512 sectorsize=4096 signature=9f2f9b66 *-disk:2 description: ATA Disk product: ST18000NM000J-2T physical id: 0.8.0 bus info: scsi@22:0.8.0 logical name: /dev/sdm version: SN02 serial: ZR55L6F3 size: 16TiB (18TB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=820606a4-a4df-432d-882e-f80bdb7fb866 logicalsectorsize=512 sectorsize=4096 *-disk:3 description: SCSI Disk product: P1633N38 EMC3840 vendor: SAMSUNG physical id: 0.9.0 bus info: scsi@22:0.9.0 logical name: /dev/sdn version: EQPC serial: NZNCAH205439 size: 3577GiB (3840GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=511e76fd-ca0d-485e-921b-2de651c3292b logicalsectorsize=512 sectorsize=4096 *-disk:4 description: SCSI Disk product: ST18000NM005J vendor: SEAGATE physical id: 0.a.0 bus info: scsi@22:0.10.0 logical name: /dev/sdo version: ET02 serial: ZR549KZF0000C227AU2U size: 16TiB (18TB) capacity: 44TiB (49TB) capabilities: 7200rpm gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=7 guid=f57d7207-7875-4137-b594-452dbfcc9953 logicalsectorsize=512 sectorsize=4096 *-disk:5 description: ATA Disk product: WUH721818ALE6L4 physical id: 0.b.0 bus info: scsi@22:0.11.0 logical name: /dev/sdp version: W660 serial: 5DG6TH9J size: 16TiB (18TB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=3b53efe2-f614-4f72-879a-f7e587c41903 logicalsectorsize=512 sectorsize=4096 *-disk:6 description: SCSI Disk product: HSCAC2DA2SUN1.6T vendor: HGST physical id: 0.0.0 bus info: scsi@22:0.0.0 logical name: /dev/sdf version: A29A serial: 001520J9J2ZA 09VEJ2ZA size: 1490GiB (1600GB) capabilities: partitioned partitioned:dos configuration: ansiversion=6 logicalsectorsize=512 sectorsize=4096 signature=9f2f9b9e *-disk:7 description: ATA Disk product: ST18000NM000J-2T physical id: 0.1.0 bus info: scsi@22:0.1.0 logical name: /dev/sdg version: SN01 serial: ZR52H1YM size: 16TiB (18TB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=00bc9d74-7b24-4657-b418-d8f98d64655c logicalsectorsize=512 sectorsize=4096 *-disk:8 description: SCSI Disk product: X356_S164A3T8ATE vendor: NETAPP physical id: 0.2.0 bus info: scsi@22:0.2.0 logical name: /dev/sdh version: NA03 serial: S5JFNE0N307472 size: 3576GiB (3840GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=7 guid=7850f3cd-99a0-4ebb-9c47-49642a1727b6 logicalsectorsize=512 sectorsize=4096 *-disk:9 description: SCSI Disk product: X356_S164A3T8ATE vendor: NETAPP physical id: 0.3.0 bus info: scsi@22:0.3.0 logical name: /dev/sdi version: NA03 serial: S5JFNA0R102890 size: 3576GiB (3840GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=7 guid=e5f14e89-a3a5-45f0-9692-2b46ad7c55a8 logicalsectorsize=512 sectorsize=4096 *-disk:10 description: SCSI Disk product: HSCAC2DA2SUN1.6T vendor: HGST physical id: 0.4.0 bus info: scsi@22:0.4.0 logical name: /dev/sdj version: A29A serial: 001635J9YZ4A 09WXYZ4A size: 1490GiB (1600GB) capabilities: partitioned partitioned:dos configuration: ansiversion=6 logicalsectorsize=512 sectorsize=4096 signature=9f2f9b62 *-disk description: SCSI Disk product: ProductCode vendor: VendorCo physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sda version: 2.00 size: 117GiB (125GB) capabilities: removable configuration: ansiversion=4 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sda size: 117GiB (125GB) capabilities: partitioned partitioned:dos *-disk:0 description: ATA Disk product: SV9SAT6B480GLM21 physical id: 0 bus info: scsi@6:0.0.0 logical name: /dev/sdb version: .1.A serial: 800A072B100802358271 size: 447GiB (480GB) capabilities: removable configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sdb size: 447GiB (480GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: guid=58bbd4c0-cc7f-49ab-adce-3a1fbe15de8c *-disk:1 description: ATA Disk product: WDC WDBNCE0010P vendor: Western Digital physical id: 1 bus info: scsi@7:0.0.0 logical name: /dev/sdc version: 20RL serial: 214026800847 size: 931GiB (1TB) capabilities: removable configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sdc size: 931GiB (1TB) capabilities: partitioned partitioned:dos configuration: signature=9f2f9b6e

While I was in my bios configuring it to boot into TrueNAS, I noticed that the slow drives appear differently in this area of the BIOS. I'm not sure what it means and it could be normal but maybe you know. Maybe the drives aren't being passed through the host the same way as the rest of the drives are.

I did the test twice writing 100G to fill the ARC cache then I did the test I posted.