explosionhole

I have an HP Microserver Gen10, with a customised Intel Xeon class CPU installed and oodles of RAM. It only has a single HDD behind the main disk array, which will be added to when budgets allow... It is connected via a small LAN with all media playback devices (i.e. TVs) connected to it by ethernet. While watching something via the Infuse app on Apple TV, configured to use SMB shares, the performance becomes terrible if I try to upload a new video file at the same time. This could be local system file copying or via SSH, both using different protocols to SMB being used for streaming. I cannot believe this system is incapable of performing both tasks simultaneously, and also expect equal / opposition questions about the performance of the Infuse application, which I am pursuing separately. What and/or how should I direct either the performance or to get better diagnose in future?

Having an issue deploying this templated container. I am choosing to provide a Fixed IP (192.168.1.20) and setting the ServerIP to this Unraid server (192.168.1.1). This choice allows me to leave the required default ports. Otherwise, my other configs would block this, such as Nginx Proxy Manager for routing of multiple domain traffic. When I run this container and set my laptop's DNS manually to 192.168.1.20, the Bitwarden Safari extension (pointing to the Vaultwarden container on the same Unraid) no longer functions. The Unraid UI seems to change the server-side IP address, as in the screenshot below. It starts initially with 192.168.1.20:53/TCP <--> 192.168.1.1:53 and repeated for all rows. And my only fix is to restart all networking services (reboot is simpler!) What am I doing wrong?

Noticed the Unraid system's config was to use 443 for HTTPS. I changed this to 444, and restarted. Cannot recall if this was changed or replaced.

I have a typical NPM config, from the Unraid "Apps" browser

I have had this config running since I initially built it in January

6th July 2023 Updated Unraid to 6.12.2 last week. Upon reboot, I cannot start my core container, NPM. My other core containers do start, such as a database container, password vault container, etc. I see in the system logs, NPM wants port 443, but is in use. I never had this problem before. There is an O/S-level Nginx instance running that is using 443. If it isn't created by the Unraid UI, I do not know what it is. Nor why the config changed to take this port. This would affect anyone attempting to bind this port to a Docker platform running inside the core O/S. It is an O/S-native service, by my initial view. If I try to manually start the NPM container, it prompts "Execution error" Updated Unraid to 6.12.2 this past week. Upon reboot, I cannot start my core container, NPM. My other core containers do start, such as a database container, password vault container, etc. I see in the system logs, NPM wants port 443, but is in use. I never had this problem before. There is an O/S-level Nginx instance running that is using 443. If it isn't created by the Unraid UI, I do not know what it is. Nor why the config changed to take this port. This would affect anyone attempting to bind this port to a Docker platform running inside the core O/S. It is an O/S-native service, by my initial view. If I try to manually start the NPM container, it prompts "Execution error". Forum posts from many years ago suggest editing a `/config/go` but the parameter no longer exists. tower-diagnostics-20230705-2341.zip

bumping this, after submitting nearly a full day ago. why is a Nginx process starting up outside Unraid? Can I kill it? What created? I just want my containers back..... 😢

I clicked the Update notification in the UI for 6.12.2. It seemed to complete ok and rebooted. Docker is running. I have a core set of containers for data storage and network routing. The MariaDB container auto-starts. I use Nginx Proxy Manager for network routing between containers. This does not start and produces the error of this thread. If I drop into the Terminal, `netstat -anop | grep 443` returns: tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 2516/nginx: master off (0.00/0/0) tcp6 0 0 ::1:443 :::* LISTEN 2516/nginx: master off (0.00/0/0) Why is there a process outside of Unraid running, as it will block my ability to use this port within Docker? Can I stop it? If so, how? There aren't any config settings for this in the standard UI. If it is erroneous, how might it have got there? I am human, therefore prone to error. I can't rule it out.... I expect that freeing this port will allow NPM container to start, which in turn will allow the others. Is this sensible? Attached the diagnostics. tower-diagnostics-20230705-2341.zip

Got this up and running, as I had expected... The end-user request would look like `https://full.domain.name/webdav`, so for Seafile config of the WebDAV component is in a file (specified within the Seafile container config) `<seafile-data-location>/seafile/conf/seafdav.conf`: [WEBDAV] enabled = true port = 8089 share_name = /seafdav On the NPM side, as it is a "route" rather than an entirely separately hosted solution it needs a "Custom Location", inside the existing Proxy Host for the above site, that points my `full.domain.name` to the internal container's point, in my case" `http://tower:8082`: Location: `/seafdav` Scheme: `http` Forward Hostname/IP: `tower` Forward Port: `8089` (from above config file)

So the basis of choosing another proxy host, rather than redirection host, is the use of a different endpoint / port? Thanks for that nugget. Given that this is all hosted within a single container, which may have different ports exposed, I wasn't sure how NPM interacted with it. Their documentation states to not use "/" behind a proxy, as this is already configured for the main app routing. But I haven't tried it - querying the community if there is prior experience. So I will try with my existing path first. Can re-deploy the containers with the other config.

Can someone help with the best implementation for Seafile's WebDAV configuration please? https://manual.seafile.com/extension/webdav/ I have the seafdav.conf file in the right location, using "/seafdav" as my share name / path. I use Nginx Proxy Manager in-front of the Seafile container with my custom URL as a Proxy Host. How do I add in the extra Nginx config? Should this be: A "Custom Location" inside the Proxy Host config? A new Proxy Host? A new Redirection Host?

this is my `script` syntax: #!/bin/bash #foregroundOnly=true backgroundOnly=true arrayStarted=true #name=blah blah blah #argumentDescription=This is the description of the argument(s) #argumentDefault=defaultArg1 defaultArg2 etc docker exec mariadb sh -c 'exec mysqldump --all-databases -uroot -p"password" | gzip > /mnt/backups/unraid_`date "+%d-%m-%Y"`.sql.gz' find /mnt/user/data/Backups/mariadb/ -type f -mtime +15 | xargs rm

I cannot see any difference in punctuation from the default provided scripts. File permissions are the same. I had to debug it by re-running it while editing the script, but it executes now.

Installed the User Scripts plugin, and followed the usage / guides to populate the various files. After adding the script and executing it, I cannot now run in the background or schedule it for future runs. Is this a known issue? Is there a fix?

Installed the User Scripts plugin, and followed the usage / guides to populate the various files. After adding the script and executing it, I cannot now run in the background or schedule it for future runs. Is this a known issue? Is there a fix?