stefan.tomko

OK, I figured this out. Perhaps it will help someone too. So my setup is - I run several instances of Nextcloud. Before using AIO, I used classic multi-docker install and never had such issues. It started when I switched to AIO. I am using Nginx Proxy Manager. My problem was that with default AIO setup, your nextcloud runs on port 11000 on the IP of your unraid server - this is where you have to forward your traffic to using reverse proxy (NPM in my case). My NPM is running on br0 and I typically assign specific IPs to docker. Whenever I would connect to either nextcloud instance, it would stutter, become unresponsive. Like - I would get to login pace, log in, but after that, it would not be responsive for few minutes. I figured, after reading other posts on NC forum, it has something to do with networking within unraid - perhaps that I am using br0 for my NPM, connecting to Nextcloud AIO... (I am using ipvlan for dockers, if that is of interest). To get this working - here is what I needed to do: 1) In NPM properties - enable advanced view and in "Post arguments" put this: ; docker network connect nextcloud-aio Nginx-Proxy-Manager-Official This will assing NPM also network adapter from internal nextcloud aio network through which all NC dockers communicate 2) Modify your proxy host so that instead of an IP and port 11000, it connects to docker name. Example: your.cloud.domain points to http://nextcloud-aio-apache:11000 That resolved connection issues for one of my servers (NC). However I have another unraid server, running different cloud instance, and I needed to figure out a way to pass connection to second NPM. I did not want to dedicate other external port for 2nd instance. Therefore since all my https is forwarded to primary NPM, that is the place where to distinguish connections based on domain accessed. To make this work: 1) Edit proxy host - configure for example your.second.domain to connect to https://ip_of_second_NPM:443 (assign proper SSL certificates) 2) In that proxy host, navigate to advanced settings and put this there: proxy_set_header Host your.second.domain; proxy_ssl_name your.second.domain; proxy_ssl_server_name on; 3) In secondary NPM, create proxy host that will actually connect to apache of your second instance. Follow same instructions as in first part of this post - assign internal interface to NPM and point connection to docker name instead of IP. That should do it. Now both your.cloud.domain as well as your.second.domain are firstly sent to primary NPM. From there, your.cloud.domain connects to apache docker running on that server, while your.second.domain is sent over to another NPM instance and configured there to connect to apache docker on internal nextcloud network. No more connectivity issues for me.

Thanks to other forum topic on NC forum where someone pointed out the issue is with the way how NPM connects, i managed to resolve it on my host, by attaching internal docker network from nextcloud to NPM and referring connection to docker container name instead of ip on bridged network. However I still face an issue since I host 2 NC instances behind my reverse proxy. While one is pointed to internal docker network, other NC instance is hosted on different machine in network where I need to access it via br. Any ideas on where the issue is, or how to overcome it, without needing to specify other port on wan and forward that over to 2nd npm instance?

There are no logs with or around the timestamp when that issue occurs.

I came here looking for help. I have Nextcloud AIO installed on 2 different servers. Pretty basic setup, nothing fancy. Before switching to AIO, I used regular docker install and was pretty satisfied, except trying to put multiple things together (+collabora, etc.) and AIO just made more sense. However my issue is - I set it up just fine, all works. But often, when I browse into NC (to upload/download/edit some files via web mostly), NC would just stutter - requests eventually ends with 504 Timeout error. That lasts for couple of minutes (3-5?) and then all comes back to life. Almost like there is some bottleneck or something that NC just can't digest and stutters. I tried checking obvious things - found nothing specific in apache logs, master container logs or NC logs at all. I am using Nginx proxy manager - if that matters. I know this is not much to start with, but I am hoping that someone encountered something similar and would be able to advise. Edit: for instance just now (3:21 PM) - i have deleted 3 files and tried to upload one, it just spins. If I refresh the page - i get 504 error Logs in apache/nextcloud/mastercontainer are only from the time of start, nothing recent. 3:26 PM and it is back working. Similar hiccup happened on other instance the other day where I just logged in, and that kicked it down.

If you navigate to where you edit your VM - top right, there is possibility to show XML view. Once you toggle it, it shows XML configuration. You should be able to just copy paste it, so when you need to recreate it, you can just paste it there. Truth is, unless you are doing something fancy, you really need to pick up just where your VM disk is (usually /mnt/user/domains/xxx), perhaps core assignment, network card type and perhaps MAC address (if you rely on DHCP)

When I faced libvirt issues, I could not start VM services at all. For me, it worked by deleting the libvirt.img (on settings - VM tab, once you stop VM service, there should be button to delete libvirt). It will be recreated upon VM service start. You can backup VM XML, since after libvirt deletition, VMs will be gone. But this is just VM definition, virtual disks are still there, you just need to create VM again, assign old disk, RAM, etc.

Did you delete it by checking this checkbox "Delete Image File" and hitting done? Because that is how I do it. On next disable/enable VM, file gets recreated again. By the way, I am still getting that. I run multiple unraid servers, and I am getting that on more of them. Basically when I disable VM service because I need to change something in settings, or when I reboot server for whatever reason, there is 50/50 chance that VMs won't work. Not sure what it really is related to, when I check libvirt logs, there are messages related to USB devices, how they could not be attached or something. But since I wasn't able to figure it out, I stopped bothering much. I just back up VM XML, and on next libvirt file creation, I just recreate VMs.

Coming here for help. I am trying to set up nextcloud-aio. I am using local DNS server (pihole) to resolve internal IP internally. I have added "--dns x.x.x.x" into extra parameters for mastercontainer, however this does not seem to be populating to other containers. As a result, apache container resolves my public IP, which is not working for me locally (can't do hairpin NAT, and I can't access my public IP from inside LAN). These sub containers don't allow to set DNS for each. So I am trying to find a way how to force it to use specific DNS server for name resolution.

Thanks. I managed to get it resolved, but your lead that USB is being passed to VM was valuable lead.

Thank you all for quick responses. I managed to find the issue - what was causing it, not the reason. It happened to me in the past when Unraid was not shut down cleanly, that my libvirt image would get corrupted. I tried backing it up daily in the past, but that did not help - when it got corrupted, regardless if I stopped VM, restored libvirt.img from backup, it just did not work. So instead i backed up xml for each VM (when you edit VM and switch to XML view, I copied the output). Seems something must have changed that caused device mappings to change. When I restored VM from XML, I had at least 2 USB devices listed that were "unknown". I did not attach any of them to VM in VM's settings, yet when I started VM restored from XML, it went nuts. So instead of doing that, I manually recreated all my VMs (I have some dependencies on various network cards, mac addresses, so it is bit of work). Anyhow, other things got messed up too (this is outside of this topic, but maybe someone finds it useful). I was using macvlan for docker despite few changes recently that actually recommended to change back to ipvlan. I did not have issues with macvlan, and i had several reboots recently and everything just worked. Today, after this "catastrophy", I figured that docker to docker access does not work anymore either despite having all settings set to allow that. I had to change to ipvlan and it started to work. Can't explain why all of sudden today, it stopped liking it. Also, all of my dockers were listed as stopped, and i could not start any of them (something like "container not found" error on start). I had to force update everyone (except for those using host/bridge access) (or would need to delete docker.img and reinstall all apps from previous apps) and then it could be started. Maybe server got a huge "kick" today and started disliking lot of things. But I managed to get if up and running. Again, thank you all.

there is nothing under /etc/libvirt I have not changed anything, just rebooted the server and this happened. Not aware of any USB mappings in vm itself. I guess I would need to remove libvirt image and try from scratch there.

OK this is strange, i have cleared all mappings from both patg and config. root@Tower:/tmp/usb_manager/config# ls remote_usbip.cfg usb_manager.cfg vm_mappings.cfg root@Tower:/tmp/usb_manager/config# more vm_mappings.cfg ******** vm_mappings.cfg: Not a text file ******** root@Tower:/tmp/usb_manager/config# root@Tower:/boot/config/plugins/usb_manager# ls packages/ remote_usbip.cfg usb_manager.cfg v2 vm_mappings.cfg vm_mappings.cfg.backup root@Tower:/boot/config/plugins/usb_manager# more vm_mappings.cfg ******** vm_mappings.cfg: Not a text file ******** root@Tower:/boot/config/plugins/usb_manager# As soon as i start array and VM gets started, unraid flash is passed to VM I can't go to VM settings to check it, as it does not show up after array start. Any ideas how to get out of this loop?

i am not sure I understand what you mean. Could you elaborate?

Is there a way to clear all mappings? I am having strange issue after I replaced one of array drives. When array is stopped and VM/Docker is not running, and I look at USB tab, all ports seem correct (eg. devices that are supposed to be passed to one VM are marked with that VM, and unraid flash drive is marked as unraid flash drive). But once I start VM service, unraid flash drive gets passed to the VM and I am done at that point, my only chance is to go and reboot and start over. I can't figure this out. I am getting typical "usb corrupted" message as soon as USB gets passed to the VM. edit: I tried renaming vm_mappings.cfg (or similar) under /boot/config/plugins and reinstalled USB manager plugin, then my historical mappings were gone, so I thought it would help, but as soon as I started VM service, 2 of my USB devices got mapped to VM automatically, unraid flash included.

Right. But the problem I have is that all USB mappings under USB seem OK. However as soon as I start VM service, flash drive gets passed to the VM. And once that happens, I am unable to enter docker/vm settings. My only chance then is to reboot the server and start again from scratch.