bat2o

The current version doesn't have an AppData path. You could setup your own share to manage the minetest config files. Below is my setup.

You download modes from: Mods - ContentDB (minetest.net) Place them in the /mods/ folder Restart the server Edit the 'world.mt' file (/worlds/world), by changing the value to 'true'

Use this syntax qemu-img resize --shrink vdisk1.img 60G

I have the same issue, where my router doesn't allow NAT loopback or hairpinning. To access nextcloud on my home network, type the localhost:444, which then redirects it to the nextcloud.mydomain.com (like you indicated). After that first redirect I change the "nextcloud.mydomain.com" with "localhost:444" in the url and it works.

I have been using GPU/HW passthrough, but at times these systems are not working. Thanks to these forums and Squid I've found out that my IOMMU is being disabled. If I go to Tools>System Devices it says "PCI Devices (No IOMMU Groups Available)". This is fixed by going into the bios and enabling IOMMU. However, for some reason my system will disable it, and I will have to go into the bios to re-enable the IOMMU. Does anyone know why my bios would change this setting? Especially without me making the change. I am using a X570 Phantom Gaming 4 motherboard.

Thanks @sonic6. I also found that this approach was recommended earlier in this forum too. Thanks for the pointer. Looks like I might need to get a new router, because I cannot see a way to set this up on my system and couldn't find any recommendations on the web. My setup is a Deco TP-Link mesh network behind a technicolor C2100T modem/router. Both of these are quite limited. I'll keep searching. I had to use this setup for SWAG because centurylink's routers don't let you change the incoming WAN port to a different LAN port (443 -> 1443), unless you can identify the incoming/remote IP. For my SWAG setup I forward 443 (C2100T) to the mesh network (Deco TP-Link) router, and there I'm able to port forward 443 to 1443. Since I couldn't find a way to turn on NAT Loopback on either router, I tried a different approach. I assigned all the dockers to a specific LAN IP (192.168.0.xx) so I can do local DNS records through Pi-hole. I had to assign them their own LAN IP since it wouldn't let me use ports. This worked for some dockers, but not for nextcloud. It gave an internal error.

I'm using swag for nextcloud. It works great when I connect via an external network. When I'm on the same network the connection times out. I followed the tutorial by spaceinvader one (https://youtu.be/I0lhZc25Sro) and am using duckdns.org for my WAN IP. I have used the subdomains approach with duckdns.org and then setup my own domain. Both work externally, but time out when I'm on the same LAN as my unRAID server. I'm guessing it is a DNS issue, but that is beyond me. I haven't been able to find anything to fix this issue, nor have I seen anything in the logs to troubleshoot. Let me know what other information you need to diagnose this issue.