Kira

Thank you for this wonderful app For anyone who needs to keep specific Docker containers running on a backup server, I found a solution: I modified the backup.sh file. After the script stops all containers, I added a docker start (name) command for each essential container. This instantly restarts them. Be aware that this approach is hardcoded—you'll need to repeat the docker start (name) line for every container you want to restart.

is there still no solution to keep application that is already running on backup server to remain running?

Anyone know how to fix this "set_canon_ace_list: sys_acl_set_file on file [MacBookPro.sparsebundle/mapped/25d]: (Not supported)"? Update: its fixed using "zfs set acltype=posixacl <pool>/<dataset>"

[1687011499] unbound[1:0] warning: setrlimit: Operation not permitted [1687011499] unbound[1:0] warning: cannot increase max open fds from 40960 to 57568 [1687011499] unbound[1:0] warning: continuing with less udp ports: 5820 [1687011499] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning For anyone who would like to solve the above error, the main issue is actually "setrlimit: Operation not permitted" all you need to do on the docker is enable privileged and all warning resolve

i ran tailscale up --accept-routes --advertise-routes=xxx --accept-dns=false under info tab it will show Accept Route to Yes but if the plugin restarts, some how the Accept Route becomes No and Health shows " Some peers are advertising routes but --accept-routes is false" I then had to run the tailscale up command again, restart the service to get Accept Route to Yes and health no longer shows issues how to I make sure the settings are saved

Need some configuration help on admin portal i set nameserver to my pihole ip on the docker i set TS_ACCEPT_DNS to true, as exit node, and accept routes when i use the docker as exit node from other device it wont go through my pihole, if i dont use this docker as exit node, traffic goes through pihole previously i was using deasmi docker as exit node and it works fine please help update: i solve it by changing TS_USERSPACE to false. weird thing now is on tailscale admin, i see message "Unable to relay traffic" warning but everything seems working fine

Anyone got any recommendation for a new Unbound docker as I think this is no longer being updated? also how do you do this "As for "error: Could not open logfile /dev/null: Permission denied", I've sorted this by creating the "unbound.log" inside the chroot directory, which is the mapped appdata directory that I mapped the unbound docker to." ? not sure what is the steps to do "creating the "unbound.log" inside the chroot directory" .

Anyone know or manage to resolves the following warning and error? [1687011499] unbound[1:0] warning: setrlimit: Operation not permitted [1687011499] unbound[1:0] warning: cannot increase max open fds from 40960 to 57568 [1687011499] unbound[1:0] warning: continuing with less udp ports: 5820 [1687011499] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning [1687011499] unbound[1:0] error: Could not open logfile /dev/null: Permission denied

Hi All, Need some help custom network. I have 3 VLANs, 1 for Server, Docker and DMZ. Unraid Server - 192.168.1.2 PiHole - 192.168.2.2 OpenVPN - 192.168.3.2 My OpenVPN settings I setup as Routing with DHCP 192.168.4.0/24, allowed IP to 192.168.2.0/24 and DNS set to 192.168.2.2 Now on my device, I am able to connect to OpenVPN but when surfing the internet its not working. On PiHole, I can see Device IP - 192.168.4.2 Any ideas what steps I am missing? Thanks

i downgraded to 1.20.2-alpine and no longer face the apt error but now i have new issue whereby it cant connect to influxdb:1.18.4-alpine When writing to [http://192.168.xx.xx:8086]: database "telegraf" creation failed: Post "http://192.168.xx.xx:8086/query": dial tcp 192.168.xx.xx:8086: connect: no route to host No changes to my network was done

argo tunnel is established via UUID and not IP or Ports so your 2nd docker config will have a different UUID hence it may work

you can probably create another docker and just change the name of docker and app folder

I got the Argo Tunnel working to SWAG but now I have a problem As we have removed the A record where it points to IP. One of my CNAME for vpn.yourdomain.com no longer works Need help

Need some help to setup with SWAG In SWAG I setup subdomains to wildcard as I have multiple subdomains. So when I setup cname "xxx.com" > xxx.cfargotunnel.com, I encounter "ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: x509: certificate is valid for *.xxx.com, not xxx.com" cfRay=65afac1cfd390acc-NRT originService=https://192.168.xxx.xxx:443" If I removed the wildcard from SWAG subdomain options then I encounter another a new error. 2021-06-06T06:34:03Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.xxx.xxx:443: connect: connection refused" cfRay=65af9cda18a9205f-NRT originService=https://192.168.xxx.xxx:443 https://192.168.xxx.xxx:443 is my SWAG docker IP

anyone statping working? when i open the webui it just keep loading Edit: reinstalled docker fix it