mraneri

Well, that folder is empty. If I go to reinstall the container from community apps and just hit save it makes a new template. Still not sure what caused it though, and I'll need to check those corruption warnings. Thanks

Haven't touched the flash drive or run memtest lately. Scrub shows no file errors.

If I try to create a container all of the user templates are gone except for the recently installed grav container.

It's actually all of the project links as well. Everything was running perfectly fine. I rebooted the system via the button on the Main screen and when it came back all of my containers looked like the Emby screenshot. I tried rebooting again and the same thing. Emby has an update available, but trying to apply it gives me this "Configuration not found. Was this container created using this plugin?". I can still access all containers by IP:Port manually. I tried installing a container that I have never used before (grav) and WebUI, edit, all project links are there and working. Does anyone have any idea what happened, or how to fix this? Thanks tower-diagnostics-20220716-1925.zip

Setting > Display, very last option

Favorite: How easy it is to use and get started for 2020: maybe some way for the VM GUI to not reset custom xml. I don't know if having a separate area for custom entries that could be merged to the GUI generated xml on VM boot could work?

Do you remember what specifically you did for iMessage/Facetime? The Appstore and iCloud work fine for me, but not the other two. edit: This vm has two EFI mountable partitions, the top one has the CLOVER directory in it, the bottom one looks similar to the partitions mentioned in every tutorial but only has an APPLE folder. I'm a little lost.

16GB DDR3, works fine for a home NAS/media server. I am planning on upgrading next year to be able to run a couple VMs and reduce the number of computers I have running 24/7.

So for this to work you would need a router that supports vLANs as well? It doesn't look like the stock ASUS firmware has that functionality.

That works. I can use my router as the client DNS just fine, that doesn't solve the problem of not being able to access Dockers with custom IPs.

You most certainly need to be able to access it to use it. What are you talking about? You haven't added anything to this thread except say that it works for you and you don't know why.

Unraid is 10.0.2.6 The pi-hole container is on br0 with a custom ip of 10.0.2.3. If I connect through wireguard I can't see 10.0.2.3 to use it as a DNS.

I cannot figure out how to get my phone to see the pi-hole docker container on 10.0.2.3. I have the DNS configured on the client side. Setting NAT doesn't seem to change anything either. I can see other physical nodes on the network, just not the docker assigned a custom IP.

I just installed the docker and the only settings I changed were setting network type to custom and the time zone to America/New_York. When I go into the admin UI I can't change anything because of this. Does anyone have any insight? Edit: It looks like running chmod 0777 -R /mnt/user/appdata/pihole/pihole/ from the terminal fixed it. After hitting save I changed it back to 0755 and everything seems to be working normally. What would cause the permission issue in the first place?

Pinging 10.0.2.3 I get this: