dbs179

I checked my back up and don't see it on there. I had a flash drive die last winter and for some reason that docker must not have made it into the backup and onto the new drive. Any other ideas how to fix it?

Correct, there is no edit option. How do I get the template back onto the unraid USB?

I have an issue with my Duplicacy Docker. It shows there is an update available, but when I got to apply the update I get an error message that says "Configuration not found. Was this container created using this plugin?". Anyone else run into this before? Thanks!

I thought it might be a firewall rule also, but the more I dig into it the less I think that is right. From my "Private" VLAN, I can reach my UnRaid GUI, which is on the "Core" VLAN even with the IP Addresses added to each VLAN in UnRaid Network Settings. As I mentioned, I can also get to the default SWAG webpage using my UnRAID IP address and the SWAG Port. I did do a tracert while on each VLAN. From the Core VLAN where everything works I only have one hop, right to the UnRaid Server. From my Private VLAN it takes two hops, one to the default gateway of that VLAN and then onto the UnRaid Server. While on the Private VLAN I can ping the UnRaid IP, as well as my Domain Name. I'm using a Unifi UDM Pro for my router. I've added a rule for WAN In, WAN Local, LAN In, and LAN Local to accept all traffic between my Private VLAN Network and my UnRaid IP Addresses and that still hasn't changed anything. This is really stumping me, but I don't know a ton about networking, Docker Containers, or Reverse Proxies to really sort out where the issue lies.

I normally access it from subdomain.domain.com from inside and outside my network. After changing the VLAN settings, I can no longer do that unless I'm on the "Core" VLAN or outside my network. I also can not access it from IPAddress:port either, but if I do IP Address:SWAG DOCKER PORT I can get to the default webpage of SWAG.

That makes sense what you are saying and is what I'm seeing when I add the IP's to VLAN's. What I don't understand is why I can't reach my SWAG/NextCloud once I do, unless I'm on the management LAN. I can ping my UnRaid IP Address from my Private VLAN and access the GUI with the IP Addresses added to the VLAN's, so I don't think it is a network/firewall issue.

I've done a bit more digging and discovered if I put my PC on the same VLAN as my UnRaid, I can still get to my NextCloud no problem. But from any other VLAN, I can't. I have four VLANS. If I'm not on my home network I can also reach my NextCloud. Interestingly enough, I can get to the default SWAG page by navigating to my UnRaid IP and the SWAG port I am using (1443), 1 - Core VLAN - UnRaid lives on this VLAN 2 - Private VLAN - For trusted devices - my PC normally lives here 3 - IoT VLAN 4 - Video VLAN

Hi all, I have an issue I'm not sure how to fix. I have NextCloud and Swag set up and running great using the latest Space Invader One tutorial. My network has several different VLAN's with my Sonos Audio gear on VLAN 20. I use a UDM Pro for my networking, but the UDM pro doesn't route/relay multicast traffic across VLAN's very well. i solved this using Sycto's Mutlicast relay. I used to run this in PodMan on the UDM Pro, but just moved it to Docker on UnRaid. In order to do so, I had to set up all of my VLAN's in Networking on the UnRaid, which I had already done, but I had the IP addresses for each VLAN set to none. This worked fine for NextCloud, but resulted in errors with the Multicast Relay container. Adding IP Addresses for the VLAN's fixes the Mulitcast Relay container and it runs as expected, but once I do that I can no longer access my NextCloud instance. Any ideas of why adding these IP's in the VLAN settings is messing with Nextcloud? If it matters any, my Swag and Nextcloud are running on a custom docker network. Thanks!

Hi all, I have a strange problem I've been dealing with for a while now. When I copy large amounts of data or even larges numbers of files from my Windows 11 machine to my UnRaid, the share becomes unavailable somewhere during the copy. If I wait several minutes, the share comes back and works just fine. I've tried limiting the amount of data and also the number of files, but can't seem to figure out what triggers the issue. I'm also not sure if it is an UnRaid issue or a Windows issue. I thought about trying to use FileZilla, or some other program, to do the transfer, but can't seem to find any that support Network Shares. Any ideas on how to diagnose this would be greatly appreciated! Edit: I enabled the UnRaid built in FTP and used WinSCP and that is working just fine. Not that it helps any, as it is a different protocol and a different application that windows explorer. Thanks

I was having an issue with my parity and one data disk always being spun up when NextCloud was started. If I stopped NextCloud the drives would spin down like they should. I followed SpaceInvaderOne's new guide and set NextCloud up from scratch. I have everything working again, but I still have the data drive the files are stored on and the parity drive not spinning down. When I look at the file activity plugin, it shows that the nextcloud.log file is being opened and modified. I have my appdata on my Cache Drive and only the folder for user files located on my array. Is this normal behavior and if not, how do i get the log file moved to the Cache drive?

Hi all, I have a question I'm hoping someone might be able to help with. I have a Unifi Dream Machine Pro for my home network. It is great, except when you have Sonos equipment on VLANs other than the controlling equipment. I have to run this multicast relay Git to allow my different VLANs to talk to my Sonos gear. Currently I run it directly on my UDMP, but it doesn't survive a reboot. I was hoping to move it to my UnRaid in a Docker Container if possible. The container has to have access to all VLAN's to listen for the multicast traffic, so I don't know if that is possible. Any ideas or suggestions? Thanks!

More than likely your .conf file is wrong. if you are using Swag there is an updated conf file a page or so earlier that worked great for me. I still don't have this fully sorted out yet, but that should get your reverse proxy working properly.

For anyone having issues upgrading to 22.2.3 or higher that is using ReDis, the linked thread below helped me get everything sorted out and upgraded using the manual upgrade method. You will have a security and setup warning that files have not passed the integrity check until the issue is fixed, which is supposed to be corrected in 22.2.4 https://help.nextcloud.com/t/redis-cluster-error-without-having-a-cluster/121589/21

I'm having an issue upgrading from 21.0.7 to 22.2.3. I'm using the Web Updater and it gets all the way to the last step of turning Maintenance Mode off and starting the update process and then I get an "Internal Server Error". I'm not quite sure where to go from here. Any suggestions? Upgrades up until now, including upgrading from 21.0.5 to 21.0.7 worked just fine.

Hi all, I have an issue that I'm not sure if it just started or if I've had it for some time. At any rate, I noticed that my parity and disk 3 won't spin down. I can click on them and spin them down, but they spin right back up. I've done some troubleshooting and it looks like it is my Nextcloud docker is causing the issue. I asked in the Nextcloud docker support thread, but didn't get an answer, so I thought I would make a new thread. With all of my dockers running except for Nextcloud, the disks all spin down as they should. As soon as I start Nextcloud, disk 3 and parity spin up and won't spin back down. Here is my configuration. Docker image is in the system share, which is set to Cache: Only. appdata share is set to Cache: Only. Nextcloud data share is set to Cache: Yes and set to Include disk: Disk 3 MariaDB docker has the /config mapped to /mnt/user/appdata/mariadb Nextcloud docker has /data mapped to /mnt/user/NextCloud/ and /config mapped to /mnt/user/appdata/nextcloud/ When I set this up a few years ago, I followed the SpaceInvader One video for it, so I don't think my config is wrong. Any ideas on why Nextcould is keeping my disks from spinning down? Thanks, Dave