ijuarez

Hope you can RMA the drive.

Caddy is such an easy reverse proxy

Thank you for the clarification I've been looking for something as polished as this but with out connection to internet.

By adding AI you are now connecting to the web so its no longer No telemetry, no external connections, no cloud dependency Is this a correct statement?

Very cool, i presume that it will make it to the CA apps

so having the appdata on the cache not and option anymore?

Getting this error and authelia will not start time="2026-01-28T09:09:21-06:00" level=info msg="Storage schema is already up to date" time="2026-01-28T09:09:22-06:00" level=error msg="Error occurred running a startup check" error="the system clock is not synchronized accurately enough with the configured NTP server" provider=ntp time="2026-01-28T09:09:22-06:00" level=fatal msg="One or more providers had fatal failures performing startup checks, for more details check the error level logs" providers="[ntp]" stack="github.com/authelia/authelia/v4/internal/commands/root.go:93 (*CmdCtx).RootRunE\ngithub.com/spf13/[email protected]/command.go:1015 (*Command).execute\ngithub.com/spf13/[email protected]/command.go:1148 (*Command).ExecuteC\ngithub.com/spf13/[email protected]/command.go:1071 (*Command).Execute\ngithub.com/authelia/authelia/v4/cmd/authelia/main.go:10 main\ninternal/runtime/atomic/types.go:194 (*Uint32).Load\nruntime/asm_amd64.s:1693 I have been using this for along time using IbraCorps guide and NTP server was not define. I am going to add that to my config file to see if it helps. Update you will have to define a NTP server if did not have one before this fixed the error.

Latest update broke authelia for me any docker that has the docker mod to use authelia gets a 500 internal server error. Otherwise swag is working. Anyone else having this issue? Ive recreated the container not a swag issue its authelia issue but the update must have rooted the issue. Authelia is having the issue of time time="2026-01-28T09:09:21-06:00" level=info msg="Storage schema is already up to date" time="2026-01-28T09:09:22-06:00" level=error msg="Error occurred running a startup check" error="the system clock is not synchronized accurately enough with the configured NTP server" provider=ntp time="2026-01-28T09:09:22-06:00" level=fatal msg="One or more providers had fatal failures performing startup checks, for more details check the error level logs" providers="[ntp]" stack="github.com/authelia/authelia/v4/internal/commands/root.go:93 (*CmdCtx).RootRunE\ngithub.com/spf13/[email protected]/command.go:1015 (*Command).execute\ngithub.com/spf13/[email protected]/command.go:1148 (*Command).ExecuteC\ngithub.com/spf13/[email protected]/command.go:1071 (*Command).Execute\ngithub.com/authelia/authelia/v4/cmd/authelia/main.go:10 main\ninternal/runtime/atomic/types.go:194 (*Uint32).Load\nruntime/asm_amd64.s:1693 Incase anyone else is having issues

Is this docker an alternative to uptime Kuma?

Thank you, im looking more into it and I need to define the variable in the template, I am reading the docs and if you used an .env using docker compose it may be easier. Thanks for the help.

It worked , few things i reverse proxy this because I want to access from outside and setup the owl relay and ingestion folder. However in the share i created to store my docs all I can see s the SQ lite (not sure how that will work if you have a large org) any way I do not see the config files to modify some of theses things like letting people just register. Just an FYI For the time now its behind authelia

This is very sad, this community has lost a great resource he help me out several times. My condolences and prayers for his loved ones.

I don't use the onboard nic i use a intel quad nic, Rolled back to the binhex/arch-urbackup:2.5.33-2-01 and it operational

Will do an report back Thanks

The current install does not have a documents location defined.

this my setup, I will wait for an update

I have noticed from binhex repo he has several versions he updated in 24hrs ago. Hopefully he can let us know

Had an update for the app and once it applied its failing to start. Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2025-11-10 09:10:53.455264 [info] Host is running unRAID 2025-11-10 09:10:53.490462 [info] System information: Linux LahomaMediaCenter 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux 2025-11-10 09:10:53.526141 [info] Image architecture: 'amd64' 2025-11-10 09:10:53.560683 [info] Application name: 'urbackup' 2025-11-10 09:10:53.596440 [info] Base image release tag: '2025110901' 2025-11-10 09:10:53.634150 [info] Application image release tag: '2.5.34-1-01' 2025-11-10 09:10:53.676988 [info] PUID defined as '99' 2025-11-10 09:10:53.721146 [info] PGID defined as '100' 2025-11-10 09:10:53.997519 [info] UMASK defined as '000' 2025-11-10 09:10:54.035374 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data' 2025-11-10 09:10:54.075479 [info] Deleting files in /tmp (non recursive)... 2025-11-10 09:10:54.119648 [info] Starting Supervisor... 2025-11-10 09:10:54,268 INFO Included extra file "/etc/supervisor/conf.d/urbackup.conf" during parsing 2025-11-10 09:10:54,269 INFO Set uid to user 0 succeeded 2025-11-10 09:10:54,273 INFO RPC interface 'supervisor' initialized 2025-11-10 09:10:54,273 INFO supervisord started with pid 7 2025-11-10 09:10:55,276 INFO spawned: 'urbackup' with pid 57 2025-11-10 09:10:55,277 INFO reaped unknown pid 8 (exit status 0) 2025-11-10 09:10:55,295 DEBG 'urbackup' stderr output: /home/nobody/start.sh: line 20: 63 Illegal instruction /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime 2025-11-10 09:10:55,295 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22375946821920 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stdout)> 2025-11-10 09:10:55,295 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22375946478736 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stderr)> 2025-11-10 09:10:55,295 WARN exited: urbackup (exit status 132; not expected) 2025-11-10 09:10:55,296 DEBG received SIGCHLD indicating a child quit 2025-11-10 09:10:56,298 INFO spawned: 'urbackup' with pid 64 2025-11-10 09:10:56,317 DEBG 'urbackup' stderr output: /home/nobody/start.sh: line 20: 70 Illegal instruction /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime 2025-11-10 09:10:56,317 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22375946478736 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stdout)> 2025-11-10 09:10:56,317 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22375946317472 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stderr)> 2025-11-10 09:10:56,318 WARN exited: urbackup (exit status 132; not expected) 2025-11-10 09:10:56,318 DEBG received SIGCHLD indicating a child quit 2025-11-10 09:10:58,321 INFO spawned: 'urbackup' with pid 71 2025-11-10 09:10:58,340 DEBG 'urbackup' stderr output: /home/nobody/start.sh: line 20: 77 Illegal instruction /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime 2025-11-10 09:10:58,340 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22375946317472 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stdout)> 2025-11-10 09:10:58,340 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22375946738224 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stderr)> 2025-11-10 09:10:58,340 WARN exited: urbackup (exit status 132; not expected) 2025-11-10 09:10:58,340 DEBG received SIGCHLD indicating a child quit 2025-11-10 09:11:01,345 INFO spawned: 'urbackup' with pid 93 2025-11-10 09:11:01,363 DEBG 'urbackup' stderr output: /home/nobody/start.sh: line 20: 101 Illegal instruction /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime 2025-11-10 09:11:01,363 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22375946944864 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stdout)> 2025-11-10 09:11:01,363 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22375946947312 for <Subprocess at 22375946813856 with name urbackup in state STARTING> (stderr)> 2025-11-10 09:11:01,364 WARN exited: urbackup (exit status 132; not expected) 2025-11-10 09:11:01,364 DEBG received SIGCHLD indicating a child quit 2025-11-10 09:11:01,364 INFO gave up: urbackup entered FATAL state, too many start retries too quickly 2025-11-10 09:15:23,655 WARN received SIGTERM indicating exit request I have stopped the container for now

update no issues yes but I love this, My system is 12 years old with the same hardware (few drives changes) and it on its last legs if it manages to make to 2030 my ROI must have been the greatest ever!

unraid connect is needed to get the api key?

Will you still update the other container or is that dead?

What! my trusty usb stick of 10 years of 4GB is not longer capable, this needs to be fixes. but for real, never have gotten this message, there is only 675MB free what can I delete safely to make space?

So it seems I made this issue a bigger, i found my solution staring at me. Need to enable that and boom it worked.

Thank you for the links and the time to explain, I am still digesting the info. Just to clear a few things up. pfsense is my choice of poison and a cisco 3850 is the managed switch. vlans are managed on pfsense and work as intended. Unraid was not setup with vlans at all, after watching the two youtubes i see where the br whatever can be confusing in my post. My br do not have the i.e. br0.10 on my unraid 3 of the 4 ports are connected to a port on the switch that is on a assigned vlan, hence the 10 20 30. I used macvlan until one the of the updates for unraid stated it was better or more stable to use ipvlan with docker. I also noted that the two examples each user has only one network card and i can see if you have vlans on your network and want your containers or vm;s to have access you have to create the vlans. I may have to revamp my networking. thanks again for taking the time to reply.

I have been putting off asking this question because I wanted to find a solution but have not found one. Background unraid server has a 4 port nic, each port is connected to a different vlan. (10 br0),(20 br1), (30 br5). 10 for servers 20 vpn vlan 30 in house pc's 4th nic not in use Dockers are on either a proxynet, bridge, or brX Recently I've redone my media to follow the Trash guide, my issues was with the script that will stop qbit and move files and restart qbit. I posted about this and got help but i was ignoring the error, no route to host. I ignore it because "there's no way, it's on the same server" qbit is on (br1) or the vlan 20, no issues for the arrs that are on the proxynet, they can talk to it because each arr is also part of (br1) so basically they have an ip from proxynet so they can talk to each other and an ip from (br1) so they can talk to qbit (im sure there's a cleaner way but i like it this way) in the setup there's and api that talks to qbit and script that tells it to pause so mover can do its thing. All of that is working but its not talking to qbit. So when I did the most basic of tests (ping) qbit ip from the terminal ( on the dashboard i click the console button) and pinged qbit and no reply (hence the no route to host error). I thought easy fix add a route from unraids default network ( br0 or vlan 10) to qbit but that doesn't work because there's already routes to each brX network and it should work. Its not a firewall issue. I've added some visuals, the one highlighted is the proxynet for the dockers. I am sure if the was just a vanilla setup that only used bridge or host networking it would not be a problem. any help would be amazing