jazzymc/infrastructure
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Unraid: restore authentik and the stopped services, fix IP/port conflicts

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kaloyan DanchevandClaude Opus 5.5 committed 2026-10-10 18:42:38 +03:00
1 parent e45d48c0e2
commit a48647a0fa
1 file changed
+1
Download Patch File Download Diff File Expand all files Collapse all files
docs/CHANGELOG.md
+1
View File
@@ -9,6 +9,7 @@
- **[DOCKER]** After the 13:20 reboot only 14/66 containers were running. 24 containers had been recreated but not started (Traefik, AdGuard, Gitea, PostgreSQL 17, Redis, Nextcloud and others). Started them in dependency order. Now 36/66 running.
- **[DOCKER]** Nextcloud upgraded 33.0.3 → 34 → 35.0.1 (one major per step). Backup in `/mnt/cache/appdata/nextcloud/backup-2026-10-10/`. `custom_apps` chown → 33:33.
- **[DOCKER]** Updated: arcane, immich (server + ML), obsidian-livesync, rdt-client, zurg, zurg-rclone, unimus, woodpecker-agent.
- **[DOCKER]** Second pass: started authentik (forward-auth OK), vaultwarden, Uptime Kuma, *arr, transmission, speedtest, kasm and others. traefik-manager → 172.18.0.65 (IP conflict with homarr). kasm host port 3000 → 3002 (conflict with karakeep). NetAlertX: docker-label router turned off, the file router with authentik stays.
- **[NOTE]** `dockge` and `Home-Assistant-Container` are in autostart but do not exist. authentik, vaultwarden and *arr are stopped since 2026-10-08 and wait for a decision.
---