bmartino1

type diagnostic and this will make and add a file onthe usb that you can post to the form for the mod JorgeB to inspect... you typed teh comand worng its dhcpcd not dhcp...

The screenshot and pictures appear to be a QEMU VM spice connection / ipmi connection...

Here's some unraid web terminal things to check and double-check... Run these in Unraid terminal: # Show all IPs/interfaces ip -br addr # Show default gateway ip route # Show which gateway the server would use ip route | grep default *Find your main NIC, usually br0, eth0, or bond0. # Replace br0 if your interface is different IFACE=br0 Default should be br0... # Show IP on that interface ip addr show "$IFACE" # Show DHCP lease info if present cat /var/lib/dhcpcd/*.lease 2>/dev/null cat /etc/dhcpcd.duid 2>/dev/null Steps to Release/reacquire DHCP: IFACE=br0This will set the variable for future items targeting the necessary interface. default should be br0... # Drop current DHCP lease dhcpcd -k "$IFACE" # Request a fresh DHCP lease dhcpcd "$IFACE" Verify dhcp data received. # Recheck IP and route ip -br addr ip route Ping gateway: GW=$(ip route | awk '/default/ {print $3; exit}') echo "Gateway is: $GW" ping -c 4 "$GW" Ping the Internet IP and DNS: ping -c 4 1.1.1.1 ping -c 4 google.com Script One-shot full check: IFACE=br0 echo "=== IPs ==="; ip -br addr echo "=== Routes ==="; ip route GW=$(ip route | awk '/default/ {print $3; exit}') echo "=== Gateway: $GW ===" ping -c 4 "$GW" echo "=== Internet IP ===" ping -c 4 1.1.1.1 echo "=== DNS ===" ping -c 4 google.comIf DHCP renew fails, restart networking from the Unraid GUI or use: /etc/rc.d/rc.inet1 restartThen recheck: ip -br addr ip route ping -c 4 "$(ip route | awk '/default/ {print $3; exit}')"

The 169 is a DHCP address, meaning that it was unable to obtain a proper IP address from your router within the set time. When it went searching for IP.

docker extra parm option may be worth a try. --dns 8.8.8.8 https://docs.docker.com/engine/network/#dns-services

intel optanes 16GB ssd is where i go for a nvme interal boot now as ists a quick low strage long lasting althernative for usb access. bought a 10 pack a while back when usinga asrock b250 miners for hive and other. converting them into fedor bazite installs... there quite a few low end ssd that are great for the internal boot option. Was able to upgarde 1 system with out issues. suprsied to see kerneal panics after a update hard shutdown the machine and turned on then no issues... so something to be weary of in some old hardware on 5th gen intel baords potenal kerneal rip Could npt find a define cause at boot after upgrade. ram was good. usb boot... againa hard shutdown and power up no issues... but defint somthing to look for during the upgrade path...

only if you want to, unriad installs a template of your last setting, going to add a container and reselecting the name in the drop down will keep previous edits... I set this up where you can use the tempalte to run other operations as well. user script plugin to call the docker start command. then cron to run 1 a month. Thats more a a personal preference and space question. example cache clearing. I chagne automtic to xyz and run the docker. options explaind in 2nd post of this forum and on github. https://github.com/bmartino1/plex-dbrepair-docker#environment-variables setting automatic to prune will then see the default set 30 days whcih will delete old cache.

then this is not for you. the idea and goal was for this to be used for thoses who need help. idealy you shold run teh ca script maunaly inteh docker this is a side alternative due to to many useing having isseus and neding a quick fix... the docker logs tell you whats happening when it stops the operation is complete check the docker logs and see the secod post of this forum...

for a end user to run this docker and hav eit auto repair the pelx sql database due to coruption. the docker runs does its things and stops. its meant as a stop gap and a quick run this to help some not so tech savy users run teh needed sqlite comands to run the reapirs per plex to fix common database issues.

most likely a issues with the compose file database. have not had issues with the RAM disk plugin. so i can only assume based on the error reported. https://github.com/bmartino1/unraid-docker-templates/blob/main/Guides/Compose/Immich/ImmichReadme.md https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html The database needs a env line for pgdata and mapped to the same mount point due to changes and upgrades... My bet without seeing the compose is you are using the older Bitnami Redis that was removed from the Docker Hub. so the compose is calling a Docker that no longer exists.

yes as explained earlier in post: https://forums.unraid.net/topic/198745-unraid-730-stable-now-available/page/5/#findComment-1624234

I’m trying to understand the intended upgrade path here. 7.2.7 appears to include security package refreshes that are newer than what is listed in the 7.3.0 release notes. For example, 7.2.7 lists Docker 29.5.1, glibc 2.43, nginx 1.30.1, jq 1.8.1, and the Avahi CVE rebuild, while 7.3.0 lists Docker 29.4.3 and does not appear to list the glibc/nginx/jq/avahi security updates. Is 7.3.0 expected to receive a 7.3.1 update carrying these same 7.2.7 security package bumps? Or are the 7.3.0 binaries already patched in some other way not reflected in the package list? I’m not asking whether 7.2.7 is a branch-maintenance release... I understand that part. I’m asking whether a system already on 7.3.0 is currently behind 7.2.7 for the listed CVE-related packages.

https://docs.unraid.net/unraid-os/release-notes/7.3.0/#updated-packages-141 cross-referenced per docs still need to double check on usb... I would not describe 7.2.7 as “telling you to downgrade from 7.3.” It looks like 7.2.7 is a security/maintenance patch for the 7.2 branch, while 7.3.0 is the newer feature branch with internal boot / TPM licensing / newer kernel / newer ZFS stack. The uncomfortable part: 7.2.7 is newer than 7.3.0 in a few specific security package binaries. So my concern is valid. Cross-reference: 7.2.7 vs 7.3.0Package 7.2.7 7.3.0 Is 7.3 older? aaa_glibc-solibs 2.42 → 2.43 not listed as updated in 7.3.0 package list Likely yes / not shown updated avahi 0.8-3_SBo_LT → 20260508_3737842-1_SBo with CVE-2023-38469 through CVE-2023-38473 not listed in 7.3.0 updated packages Likely yes / missing from 7.3.0 list curl 8.19.0 → 8.20.0 8.19.0 → 8.20.0 No, same fixed version docker 29.3.1 → 29.5.1 29.3.1 → 29.4.3 Yes, 7.3.0 is older glibc 2.42-2_LT → 2.43 not listed in 7.3.0 updated packages Likely yes / missing from 7.3.0 list gnutls 3.8.12 → 3.8.13 3.8.12 → 3.8.13 No, same fixed version jq 1.6 → 1.8.1 not listed in 7.3.0 updated packages Likely yes / missing from 7.3.0 list libvirt-php 0.5.8-8.3.29 → 0.5.8-8.3.31 0.5.8-8.3.29 → 0.5.8-8.4.21 7.3 is different/newer PHP ABI build, not directly older nginx 1.27.2 → 1.30.1 not listed in 7.3.0 updated packages Likely yes / missing from 7.3.0 list php 8.3.29 → 8.3.31 8.3.29 → 8.4.21 No, 7.3 is newer major/minor zfs 2.3.4_6.12.82 → 2.3.4_6.12.90 2.3.4_6.12.82 → 2.4.1_6.18.29 No, 7.3 has newer ZFS + newer kernel build Sources: 7.2.7 lists the 11 updated security packages, including Docker 29.5.1, glibc 2.43, nginx 1.30.1, PHP 8.3.31, and ZFS rebuilt for kernel 6.12.90. 7.3.0 lists Docker 29.4.3, curl 8.20.0, GnuTLS 3.8.13, PHP 8.4.21, ZFS 2.4.1_6.18.29, and says “Downgraded packages (0).” Your pasted 7.3 package list matches the official 7.3.0 package section, including curl, docker, gnutls, PHP, and ZFS. The important conclusion7.3.0 does not appear to contain every package refresh that 7.2.7 contains. Specifically, based on the public release notes: 7.3.0 appears behind 7.2.7 on: docker: 7.3.0 has 29.4.3, while 7.2.7 has 29.5.1 nginx: 7.3.0 does not show the 1.30.1 security bump glibc / aaa_glibc-solibs: 7.3.0 does not show the 2.43 bump avahi: 7.3.0 does not show the 20260508 CVE bump jq: 7.3.0 does not show the 1.8.1 CVE bump7.3.0 is not behind on: curl: same 8.20.0 gnutls: same 3.8.13 php: 7.3.0 has 8.4.21, newer than 7.2.7's 8.3.31 zfs: 7.3.0 has 2.4.1 on kernel 6.18.29, newer than 7.2.7's 2.3.4 on kernel 6.12.90 kernel: 7.3.0 has 6.18.29, while 7.2.7 has 6.12.90

due to the recent https://forums.unraid.net/topic/198979-unraid-727-now-available 7.27 update can we get a confirmation that 7.3 has the updated binaries as well? are the same cve updated in 7.3? as repoprted in 7.2??? aaa_glibc-solibs: 2.42 → 2.43 avahi: 0.8-3_SBo_LT → 20260508 (CVE-2023-38469, CVE-2023-38470, CVE-2023-38471, CVE-2023-38472, CVE-2023-38473) curl: 8.19.0 → 8.20.0 (CVE-2026-4873, CVE-2026-5545, CVE-2026-5773, CVE-2026-6253, CVE-2026-6276, CVE-2026-6429, CVE-2026-7009, CVE-2026-7168) docker: 29.3.1 → 29.5.1 glibc: 2.42 → 2.43 (CVE-2025-15281, CVE-2026-0861, CVE-2026-0915) gnutls: 3.8.12 → 3.8.13 (CVE-2026-33846) jq: 1.6 → 1.8.1 (CVE-2024-53427, CVE-2025-9403) libvirt-php: 0.5.8-8.3.29 → 0.5.8-8.3.31 nginx: 1.27.2 → 1.30.1 (CVE-2025-53859, CVE-2026-1642, CVE-2026-27651, CVE-2026-27654, CVE-2026-27784, CVE-2026-28753, CVE-2026-28755, CVE-2026-32647, CVE-2026-40460, CVE-2026-40701, CVE-2026-42934, CVE-2026-42945, CVE-2026-42946) php: 8.3.29 → 8.3.31 (CVE-2025-14179, CVE-2026-6722, CVE-2026-6735, CVE-2026-7258, CVE-2026-7259, CVE-2026-7261, CVE-2026-7262, CVE-2026-7568) zfs: 2.3.4_6.12.82_Unraid → 2.3.4_6.12.90_Unraid are you telling us to down grade then move to this for CVEs or is a 7.3.1 soon to be release???...

are the same cve updated in 7.3? aaa_glibc-solibs: 2.42 → 2.43 avahi: 0.8-3_SBo_LT → 20260508 (CVE-2023-38469, CVE-2023-38470, CVE-2023-38471, CVE-2023-38472, CVE-2023-38473) curl: 8.19.0 → 8.20.0 (CVE-2026-4873, CVE-2026-5545, CVE-2026-5773, CVE-2026-6253, CVE-2026-6276, CVE-2026-6429, CVE-2026-7009, CVE-2026-7168) docker: 29.3.1 → 29.5.1 glibc: 2.42 → 2.43 (CVE-2025-15281, CVE-2026-0861, CVE-2026-0915) gnutls: 3.8.12 → 3.8.13 (CVE-2026-33846) jq: 1.6 → 1.8.1 (CVE-2024-53427, CVE-2025-9403) libvirt-php: 0.5.8-8.3.29 → 0.5.8-8.3.31 nginx: 1.27.2 → 1.30.1 (CVE-2025-53859, CVE-2026-1642, CVE-2026-27651, CVE-2026-27654, CVE-2026-27784, CVE-2026-28753, CVE-2026-28755, CVE-2026-32647, CVE-2026-40460, CVE-2026-40701, CVE-2026-42934, CVE-2026-42945, CVE-2026-42946) php: 8.3.29 → 8.3.31 (CVE-2025-14179, CVE-2026-6722, CVE-2026-6735, CVE-2026-7258, CVE-2026-7259, CVE-2026-7261, CVE-2026-7262, CVE-2026-7568) zfs: 2.3.4_6.12.82_Unraid → 2.3.4_6.12.90_Unraid are you telling us to down grade then move to this?

Is this for older kernels ? why go this over 7.3 the next reported lts?

root@The-Borg:~# uname -r 6.18.29-Unraid root@The-Borg:~# must be a typo somewhere unraid 7.3 is using kernel 6.18.29

Current Unraid Templates Repo List ✅ Active Maintained Netprobe - Python AIO of PlainPacket Project during Grafana Redis issues and needs for all in 1 docker... Ongoing support: https://forums.unraid.net/topic/195469-support-netprobe See original project: https://github.com/plaintextpackets/netprobe_lite SFTP-Fail2ban - Update and config setup for SFTP server via Docker Ongoing support: https://forums.unraid.net/topic/189050-support-sftp-fail2ban Unraid Samba Passwords - Feature Request for a non-admin way and site to change their network share password Ongoing support: https://forums.unraid.net/topic/198949-support-samba-web-portal/ ⚠️ Keeping in CA (Limited Support) Postgress Immich - Unriad CA template changes followed per v18 tag changes Limited support. see Unraid Support Forum: https://forums.unraid.net/topic/146106-immich-docker-self-hosted-google-photos-setup Valkey Redis Immich - template authing to setup valkey redis alternative with a password Limited support. see Unraid Valkey Support Forum: https://forums.unraid.net/topic/186953-support-valkey/ Unraid Immich Support Forum: https://forums.unraid.net/topic/146106-immich-docker-self-hosted-google-photos-setup PlexDBRepair - to get working, had to install plex. will watch but will most likely never update unless major CVE. Limited Support. Unraid Support Forum: https://forums.unraid.net/topic/196453-support-plex-db-repair-docker --Ideally one should attempt to run the chukpa scirpt in the existing Plex Docker due to Plex SQLite binary and database setup... No known plans to update Docker and continue support due to issues with deployment and script running. (may be better off as a user script and/or plugin...) ??? Maybe a future revamp when time permits... RetroAssembly - A Docker Request Discod Fully Supported. Application Site: https://retroassembly.com/ Images Repository: https://github.com/arianrhodsandlot/retroassembly#option-2-self-host-with-docker Mange Tempalte only. see Application site for support and there discord... 🧊 Removing From CA: (Project I no longer have time to monitor and work on.) Can still be used on USERS OWN RISK! Logmein Hamachi VPN - was a beta template to use hamachi logmein vpn via dokcer to make a unraid connection... Crowdstrike Security Bouncer for unifi - a feature request unifi proffpoint cheaper and the same thing... RejettoHFS3 - beta template hard to deploy ran greate dovker env still needs flush out a bit more form Maintainer Rejeto HFS. Unifi-OS-Server - Due to a Cease and Desist per Unifi I will no longer be able to support nor endourse this outside of a VM... Bitcoin Core - Debain VNC my use case for it is gone I have no plans to update. should still function. Bitcoin Knots - Debain VNC my use case for it is gone I have no plans to update. should still function. CKPool Solo Mine - Solo Pool setup with bitcoin wallet. Age of docker adn temaptles access prevented long term suppport after issues with getting it into CA. ClamAV-clamdscan - Debain rebuild to use clamdscan my use case for it is gone I have no plans to update. should still function. Avahi ZeroConf mDNS - atempted to fix and add vlan support on unraid for avahi before other advance workarounds due to config chagnes.. see https://forums.unraid.net/topic/178033-bmartino1-user-scripts/#findComment-1478661 for better config edit and implementation... ❌ End of Life (EOL): RocketChatAIO - Attempted to work with Support, cease and desist after atempt to git merg and setup with there support.. Removed project in favor of Jitsi and Matrix Synapse... *future errors as rocket.chat is merging and stack is aging while not mainting clear support and documentation... see guide fora better self-hosted replacement solution: https://forums.unraid.net/topic/127917-guide-matrix-synapse-w-postgres-db-chat-server-element-web-client-coturn-voice/page/4/#findComment-1611571 *Public archived matrix support due to to many movbing ports no plans to update... Due to agai lxc plugin and no roadmap plans to continue LXC on Unriad v7 moving forward... Old Bitnami Redis - Parent company was bought out, changing licensing and database access was replaced with valkey Privileged Unifi-OS-Server - rebuild with working with github users to run unifi os in Docker. There was a rebuild to go back for users having issues running the updated non-privileged version of the OG docker... Cease and desit destroyed ongoing support. icloudpd web - an attempt to get a web vnc ui to the iCloudPD project per a Docker feature request.

Reserved

Feature requested Docker https://github.com/bmartino1/smb-password-portal Non-admin website where end users can change their Samba account password.

Reserved

GitHubGitHub - bmartino1/unraid-docker-templates: Unraid CA XML...Unraid CA XML files. Contribute to bmartino1/unraid-docker-templates development by creating an account on GitHub. All encompuing support post for repo support limited, removed CA and changes.

Apologies for the late reply https://forums.unraid.net/topic/196453-support-plex-db-repair-docker/#findComment-1601211 most can be seen earlier in the post. Not aware of any YouTube videos and don't have time to make a screen share video of the process. Only the appdata path showing libray needs to be set. once it starts it will stop after some time, which depends on age of the hardware. In my testing, no more than 30 min on a bad repir on the healthy plex database, less then 10 min. refreshing the unraid docker tab will show the docker stopped. Click logs to see where it is at and to monitor progress. The log file can be found within the plex library path. data explained in the link posted above...

what I have found is uraid really wants ipv6 address via slack to enable ipv6 corectly via its inet scripting systems and if it doesn't get the correct response via the nic it will disable IPv6 as seen with Docker network inspect comands. more due to old and random data and issues with unraid moving away from macvlan to ipvaln due to a macvlan trace bug in early editions of unraid v6. as in order to use macvlan you need a network nic that supports promiscuous mode...

I run a systemctl user script which enables ipv6 forwarding. I've not had issues with unraid nor docker with ipv4/ipv6 due to issues. #!/bin/bash # Delay before starting sleep 10 # Apply sysctl settings apply_sysctl_settings() { echo "Applying sysctl settings..." sysctl -w net.ipv6.conf.all.forwarding=1 sysctl -w net.ipv6.conf.br0.accept_ra=2 echo "Verifying sysctl settings..." sysctl net.ipv6.conf.all.forwarding sysctl net.ipv6.conf.br0.accept_ra } #run loop apply_sysctl_settings script logs: Script Starting May 17, 2026 13:58.42 Full logs for this script are available at /tmp/user.scripts/tmpScripts/systemctl/log.txt Applying sysctl settings... net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.br0.accept_ra = 2 Verifying sysctl settings... net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.br0.accept_ra = 2 Script Finished May 17, 2026 13:58.52 Full logs for this script are available at /tmp/user.scripts/tmpScripts/systemctl/log.txt