casperse

Thanks! I already had it shared but it dosent show up un my "master pool shares" so I guess I have to map it by itself right? So whats the share name: /Flash (Sorry cant see anything right now because of the missing WAN so its hit and miss :-) UPDATE: Yes FLASH is it :-)

My new ISP is reporting earliest tech support on the 8/8 :-( Would it matter to keep it at "no" for the future? or could I make some custom DNS on my local router to access it? BTW: I have access through a master share, but I cant see the USB and config folder in that? Would would I have to do so I can edit and see that on the SMB share?

Hi All I find myself in a strange situation, after internet outage (Still no internet) I cant access my local UNraid UI on my loacal IP? Is there any special settings I need to define when using the unraid connect and needing local access? Example: If I go to my local IP: http://192.168.0.6/ main That would be translated to: 192-168-0-6.e7591da5b3c213bd7e17dc48d29fc9dcd1283498.myunraid.net:XXXX Or is this a Unifi problem? I am using a Unifi UDM router? And not provide any webpage, luckily I have a monitor to the server and I can access the UI from here This might just be a stupid configuration issue, that never have been a problem because internet haven't been down :-) (I have read similar posts but I am running a old Unraid I am on the latest off. version 7.1.4, and none of the posts have helped me)

Ok so UI is up and running and I was now ready to enable VPN and I am back to not having any UI again? I dont have the right port so I had to map it to 192.168.0.6:8485 but enabling VPN changes the port? Sorry been add this for 5 hours didnt want to give up this was working before (Some one said that strict could be tha cause it stopped working but I have tried everything) text error warn system array login /usr/lib/python3.13/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81. import pkg_resources Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2025-07-31 00:09:47.256368 [info] Host is running unRAID 2025-07-31 00:09:47.302288 [info] System information: Linux 534c55e0307f 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux 2025-07-31 00:09:47.348136 [info] Image tags: BASE_RELEASE_TAG=2025071102,INT_RELEASE_TAG=2025071401,IMAGE_RELEASE_TAG=5.1.2-1-05 2025-07-31 00:09:47.397848 [info] PUID defined as '99' 2025-07-31 00:09:47.478854 [info] PGID defined as '100' 2025-07-31 00:09:47.560750 [info] UMASK defined as '000' 2025-07-31 00:09:47.608647 [info] Permissions already set for '/config' 2025-07-31 00:09:47.662937 [info] Deleting files in /tmp (non recursive)... 2025-07-31 00:09:47.719647 [info] VPN_ENABLED defined as 'yes' 2025-07-31 00:09:47.764331 [info] VPN_CLIENT defined as 'wireguard' 2025-07-31 00:09:47.810474 [info] VPN_PROV defined as 'pia' 2025-07-31 00:09:47.865604 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf 2025-07-31 00:09:47.929131 [info] VPN_REMOTE_SERVER defined as 'nl-amsterdam.privacy.network' 2025-07-31 00:09:47.973006 [info] VPN_REMOTE_PORT defined as '1337' 2025-07-31 00:09:48.016355 [info] VPN_DEVICE_TYPE defined as 'wg0' 2025-07-31 00:09:48.055525 [info] VPN_REMOTE_PROTOCOL defined as 'udp' 2025-07-31 00:09:48.102349 [info] USERSPACE_WIREGUARD defined as 'no' 2025-07-31 00:09:48.144196 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' 2025-07-31 00:09:48.864169 [info] LAN_NETWORK defined as '192.168.0.0/24' 2025-07-31 00:09:48.934784 [info] LAN_NETWORK exported as '192.168.0.0/24' 2025-07-31 00:09:48.980961 [info] VPN_USER defined as 'p5864970' 2025-07-31 00:09:49.028590 [info] VPN_PASS defined as 'RtjX76NW28' 2025-07-31 00:09:49.078376 [info] STRICT_PORT_FORWARD defined as 'yes' 2025-07-31 00:09:49.128936 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports 2025-07-31 00:09:49.177176 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports 2025-07-31 00:09:49.225005 [info] ENABLE_STARTUP_SCRIPTS defined as 'no' 2025-07-31 00:09:49.270433 [info] ENABLE_SOCKS defined as 'no' 2025-07-31 00:09:49.316944 [info] ENABLE_PRIVOXY defined as 'yes' 2025-07-31 00:09:49.362483 [info] WEBUI_PORT defined as '8485' 2025-07-31 00:09:49.418638 [info] Starting Supervisor... 2025-07-31 00:09:49,852 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing 2025-07-31 00:09:49,852 INFO Set uid to user 0 succeeded 2025-07-31 00:09:49,865 INFO RPC interface 'supervisor' initialized 2025-07-31 00:09:49,865 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2025-07-31 00:09:49,865 INFO supervisord started with pid 7 2025-07-31 00:09:50,868 INFO spawned: 'start-script' with pid 391 2025-07-31 00:09:50,870 INFO spawned: 'watchdog-script' with pid 392 2025-07-31 00:09:50,870 INFO reaped unknown pid 8 (exit status 0) 2025-07-31 00:09:50,876 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2025-07-31 00:09:50,876 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2025-07-31 00:09:50,876 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2025-07-31 00:09:51,134 DEBG 'start-script' stdout output: [info] Adding 192.168.0.0/24 as route via adapter eth0 2025-07-31 00:09:51,137 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2025-07-31 00:09:51,372 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 192.168.0.0/24 via 172.17.0.1 dev eth0 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 local 172.17.0.7 dev eth0 table local proto kernel scope host src 172.17.0.7 broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.7 local ::1 dev lo table local proto kernel metric 0 pref medium -------------------- iptable_mangle 12288 1 ip_tables 32768 4 iptable_filter,iptable_raw,iptable_nat,iptable_mangle x_tables 53248 20 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,nft_compat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark [info] iptable_mangle support detected, adding fwmark for tables 2025-07-31 00:09:51,509 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2025-07-31 00:09:51,511 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -s 203.188.164.137/32 -i eth0 -j ACCEPT -A INPUT -s 181.214.206.102/32 -i eth0 -j ACCEPT -A INPUT -s 181.214.206.100/32 -i eth0 -j ACCEPT -A INPUT -s 104.18.40.93/32 -i eth0 -j ACCEPT -A INPUT -s 172.64.147.163/32 -i eth0 -j ACCEPT -A INPUT -s 172.64.150.50/32 -i eth0 -j ACCEPT -A INPUT -s 104.18.37.206/32 -i eth0 -j ACCEPT -A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT -A INPUT -s 104.18.159.201/32 -i eth0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -s 203.188.164.137/32 -i eth0 -j ACCEPT -A INPUT -s 181.214.206.102/32 -i eth0 -j ACCEPT -A INPUT -s 181.214.206.100/32 -i eth0 -j ACCEPT -A INPUT -s 104.18.40.93/32 -i eth0 -j ACCEPT -A INPUT -s 172.64.147.163/32 -i eth0 -j ACCEPT -A INPUT -s 172.64.150.50/32 -i eth0 -j ACCEPT -A INPUT -s 104.18.37.206/32 -i eth0 -j ACCEPT -A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT -A INPUT -s 104.18.159.201/32 -i eth0 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8485 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 8485 -j ACCEPT -A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i wg0 -j ACCEPT -A OUTPUT -d 203.188.164.137/32 -o eth0 -j ACCEPT -A OUTPUT -d 181.214.206.102/32 -o eth0 -j ACCEPT -A OUTPUT -d 181.214.206.100/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT -A OUTPUT -d 172.64.147.163/32 -o eth0 -j ACCEPT -A OUTPUT -d 172.64.150.50/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.18.37.206/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -d 203.188.164.137/32 -o eth0 -j ACCEPT -A OUTPUT -d 181.214.206.102/32 -o eth0 -j ACCEPT -A OUTPUT -d 181.214.206.100/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT -A OUTPUT -d 172.64.147.163/32 -o eth0 -j ACCEPT -A OUTPUT -d 172.64.150.50/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.18.37.206/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT -A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8485 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 8485 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o wg0 -j ACCEPT 2025-07-31 00:09:51,513 DEBG 'start-script' stdout output: -------------------- 2025-07-31 00:09:51,518 DEBG 'start-script' stdout output: [info] WireGuard 'peer' not found, attempting to cycle WireGuard interface... 2025-07-31 00:09:51,518 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'down'... 2025-07-31 00:09:51,531 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2025-07-31 00:09:51,535 DEBG 'start-script' stderr output: wg-quick: `wg0' is not a WireGuard interface 2025-07-31 00:09:51,536 DEBG 'start-script' stdout output: [warn] Failed to bring 'down' WireGuard kernel implementation 2025-07-31 00:09:51,536 DEBG 'start-script' stdout output: [info] Configuring WireGuard... 2025-07-31 00:09:51,789 DEBG 'start-script' stdout output: [info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' 2025-07-31 00:09:51,794 DEBG 'start-script' stdout output: [info] Successfully generated PIA token for wireguard 2025-07-31 00:09:51,795 DEBG 'start-script' stdout output: [info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'... 2025-07-31 00:09:51,874 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2025-07-31 00:09:51,886 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2025-07-31 00:09:51,897 DEBG 'start-script' stderr output: [#] ip link add dev wg0 type wireguard 2025-07-31 00:09:51,901 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2025-07-31 00:09:51,905 DEBG 'start-script' stderr output: [#] ip -4 address add 10.8.251.249 dev wg0 2025-07-31 00:09:51,915 DEBG 'start-script' stderr output: [#] ip link set mtu 1420 up dev wg0 2025-07-31 00:09:51,948 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2025-07-31 00:09:51,950 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2025-07-31 00:09:51,952 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2025-07-31 00:09:51,955 DEBG 'start-script' stderr output: [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 2025-07-31 00:09:51,960 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2025-07-31 00:09:51,963 DEBG 'start-script' stderr output: [#] iptables-restore -n 2025-07-31 00:09:51,967 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2025-07-31 00:10:23,173 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 203.188.164.137 from URL 'http://checkip.amazonaws.com' 2025-07-31 00:10:23,174 DEBG 'start-script' stdout output: [info] Script started to assign incoming port for 'pia' 2025-07-31 00:10:23,174 DEBG 'start-script' stdout output: [info] Port forwarding is enabled [info] Checking endpoint 'nl-amsterdam.privacy.network' is port forward enabled... 2025-07-31 00:10:23,175 DEBG 'start-script' stdout output: [info] Successfully brought Wireguard interface 'up' 2025-07-31 00:10:23,361 DEBG 'start-script' stdout output: [info] PIA endpoint 'nl-amsterdam.privacy.network' is in the list of endpoints that support port forwarding shown below:- 2025-07-31 00:10:23,529 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- 2025-07-31 00:10:23,529 DEBG 'start-script' stdout output: [info] de-berlin.privacy.network [info] aus-perth.privacy.network [info] france.privacy.network [info] zagreb.privacy.network [info] kualalumpur.privacy.network [info] fi.privacy.network [info] lu.privacy.network [info] kazakhstan.privacy.network [info] bo-bolivia-pf.privacy.network [info] greenland.privacy.network [info] uk-2.privacy.network [info] mexico.privacy.network [info] hk.privacy.network [info] macau.privacy.network [info] yerevan.privacy.network [info] ua.privacy.network [info] swiss.privacy.network [info] italy.privacy.network [info] spain.privacy.network [info] au-sydney.privacy.network [info] ba.privacy.network [info] nl-netherlands-so.privacy.network [info] sofia.privacy.network [info] de-frankfurt.privacy.network [info] monaco.privacy.network [info] rs.privacy.network [info] japan.privacy.network [info] de-germany-so.privacy.network [info] br.privacy.network [info] japan-2.privacy.network [info] au-brisbane-pf.privacy.network [info] es-valencia.privacy.network [info] mk.privacy.network [info] cyprus.privacy.network [info] philippines.privacy.network [info] israel.privacy.network 2025-07-31 00:10:23,529 DEBG 'start-script' stdout output: [info] sweden.privacy.network [info] nl-amsterdam.privacy.network [info] no.privacy.network [info] qatar.privacy.network [info] uk-london.privacy.network [info] lt.privacy.network [info] bogota.privacy.network [info] aus-melbourne.privacy.network [info] srilanka.privacy.network [info] za.privacy.network [info] ireland.privacy.network [info] np-nepal-pf.privacy.network [info] italy-2.privacy.network [info] gr.privacy.network [info] ca-montreal.privacy.network [info] mongolia.privacy.network [info] sweden-2.privacy.network [info] uk-southampton.privacy.network [info] in.privacy.network [info] ro.privacy.network [info] uk-manchester.privacy.network [info] santiago.privacy.network [info] panama.privacy.network [info] morocco.privacy.network [info] taiwan.privacy.network 2025-07-31 00:10:23,529 DEBG 'start-script' stdout output: [info] dz.privacy.network [info] al.privacy.network [info] ec-ecuador-pf.privacy.network [info] liechtenstein.privacy.network [info] saudiarabia.privacy.network [info] is.privacy.network [info] denmark-2.privacy.network [info] kr-south-korea-pf.privacy.network [info] montenegro.privacy.network [info] lv.privacy.network [info] bangladesh.privacy.network [info] austria.privacy.network [info] au-australia-so.privacy.network [info] gt-guatemala-pf.privacy.network [info] malta.privacy.network [info] sk.privacy.network [info] ca-ontario-so.privacy.network [info] ca-vancouver.privacy.network [info] nz.privacy.network [info] ad.privacy.network [info] vietnam.privacy.network [info] man.privacy.network [info] egypt.privacy.network [info] pt.privacy.network [info] ca-ontario.privacy.network [info] uy-uruguay-pf.privacy.network [info] slovenia.privacy.network [info] ca-toronto.privacy.network [info] au-adelaide-pf.privacy.network [info] jakarta.privacy.network [info] ee.privacy.network [info] hungary.privacy.network [info] fi-2.privacy.network [info] brussels.privacy.network [info] bahamas.privacy.network [info] georgia.privacy.network [info] ar.privacy.network [info] tr.privacy.network [info] md.privacy.network [info] sanjose.privacy.network [info] pe-peru-pf.privacy.network [info] sg.privacy.network [info] poland.privacy.network [info] denmark.privacy.network [info] venezuela.privacy.network [info] china.privacy.network [info] ae.privacy.network [info] czech.privacy.network [info] nigeria.privacy.network [info] cambodia.privacy.network 2025-07-31 00:10:23,995 DEBG 'start-script' stdout output: [info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' 2025-07-31 00:10:24,001 DEBG 'start-script' stdout output: [info] Successfully generated PIA token for wireguard 2025-07-31 00:10:24,181 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 2025-07-31 00:10:50,203 DEBG 'watchdog-script' stdout output: [info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.8.251.249 different, marking for reconfigure 2025-07-31 00:10:50,215 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2025-07-31 00:10:50,220 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2025-07-31 00:10:50,221 DEBG 'watchdog-script' stdout output: [info] qBittorrent incoming port 6881 and VPN incoming port 20674 different, marking for reconfigure 2025-07-31 00:10:50,222 DEBG 'watchdog-script' stdout output: [info] qBittorrent config file already exists, skipping copy [info] Removing session lock file (if it exists)... 2025-07-31 00:10:50,264 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2025-07-31 00:10:50,270 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8485... 2025-07-31 00:10:50,507 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8485 2025-07-31 00:10:51,063 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2025-07-31 00:10:52,072 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2025-07-31 00:10:52,082 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118

Found it another reboot!!

I ended up deleting the appdata and starting the docker again. Username:- admin Password:- randomly generated, password shown in /config/supervisord.log But I cant find the generated password anywhere?

Yes I had to write the port to get the webui (The webui in the menu whent to 8080) So now I have the login prompt but the password isnt working anymore some googleling and I found that its an error and I could add: WebUI\Username=admin WebUI\Password_PBKDF2=@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==) THis would give me: user: admin password: adminadmin BUT I am stuck here because when I am logged into the UI and want to change the UI passord I get an error: Since then I am running in circles - deleteing the conf and rebooting the docker but always the same I cant login anymore? Some say this happend during a upgrade, but if I need to roolback then to what ? version Sorry I really dont want to bother you with this but I am stuck....

I just discovered that my UI is also not available, but my PIA information is valid and the logfile shows its connected to my VPN provider. If I set VPN to "no" I get my UI back and can login. So reading the above I am not sure if I need to restart Tailscale or set it to protonvpn - Sorry I have read many of the post and did a Google and AI search :-) UPDATE: I removed the docker and pulled the new one (Better template) But even if I disable the VPN and enable debug lug I cant get the UI But according to the logfile its "running" I cant see any mistakes in my new config: Yes I know people keep telling me to use GlutenVPN but I really like my setup it has been rock solid for years!

Just a update I ended up taking it apart and placing the card on a windows PC to update the FW. On the positive, it didnt take long, and it fixed my card for encoding on Unraid, didn't work before

Intel ARC A380 - I keep seeing wrong dockers identified as using the GPU. Example FileFlows are using the GPU A380 but the icon shown on the dashboard is TDARR?

I was wondering how the GPU Statistics identify the docker using the GPU ? On mine it keeps showing TDARR even if the docker I have running and using the GPU is actually FileFlows? Is this something I can setup in the docker?

Hi All I just found this article: (Remember to) Update your Intel Arc Firmware on Linux! - Hardware Hub / GPU - Level1Techs Forums Has anyone managed to update the Intel Arc Firmware on your Unraid server? (I would love not to have to disassemble my server and place it in a winddows machine). If someone managed to do this then please share :-)

Seemed I wasnt really missing anything. I did have to go and manually point to the appdata folder (Sma eone) and save the conf again. Also the same for each of the MariaDB's and after a reboot it worked!

I am using the guyide to get AV1 encoding working in Unraid here: GitHub - plexguide/Unraid_Intel-ARC_Deployment: Unraid - Comprehensive Guide to Enabling AV1 Encoding, Plex Deployment & GPU Management with Tdarr on Unraid 7.0+ But I have found that even if I use the newest Docker container and Unraid version 7.14 I cant encode with the Intel Arc A380 The intel plugin sees the card but I cant transcode any files After spending 2 days with AI I get: According to the guide any Unraid above v.7 should support the A380. Does anyone have this working? Is there a FW update to the card I need? Really grasping for straws now.... Hope someone have the answer AI isnt cutting it :-) LOL

I have successfully restored my dockers to unraid BUT I wanted to copy them to my Unraid backup server. Same ports and username and DB names. But I keep getting the wordpress: Error establishing a database connection What have I forgot to do?

I did a restart of the unraid API on the backup server and I got the connect back but when I go to settings I now have the same problem as I started with on my main server: Just before doing the update I had the Flash back enabled and working

Update after my "backup Unraid server" did the connect update like my main server (My main server already had the update) This also happens here I now get the Please is this also happening to the rest of you?

Hi All After replacing my USB with a new USB I now cant set Flash backup? I have signed out and in to Unraid connect and I stopped the array and provided the url for the key to the new USB But I keep getting this: Any idea abot what to do next? Cheers Casperse - But I am up and running again :-)

Thanks! Okay finally got the prdered new USB sticks and I followed the transfer to new. But after loggeing into Unraid connect and selecting to transfer I got the input link to key? I ignored that because I did not receive any link to a new key? - Is that worng? everything is running fine now the sandisk started without problem (Took alittle longer seems it had to try different resolution ( I have my server attached to a monitor) But I guess its because its a first boot? Still a bummer I have a pile of the Samsung sticks that I can use. Anyone have alternatives to booting from a normal USB?

Sorry if this already have been covered somewhere in this thread! But I am having a problem removing old appdata folders after deleting dockers. They are all "greyed" out on ZFS master but when I select to destroy them I get permission denied. I have rebooted the server multiple times. I have stopped Krusader I heard that could cause issues... I havent stopped the server before destroying the dataset, should I?

No I am trying to do a new fresh install, I need to move my hosted sites back to my Unraid server (Migration is tuff). But I need to start up with a older version and then maybe build a new one later. For that I wanted to pull down a older version. But no matter what I write after wordpress in the docker repository it always fetches the newest version. wordpress:5.9.1 No effect? I get that maybee its so old that for security reasons they just drop it? Open webUI internally problem: Yes maybee its a DB issue with the open web UI (Its after a restore, so it might overwrite it

Also no matter what I try I cant downgrade this image to a older version? wordpress:5.9.1 does not work

This might be a stupid Q :-) But when I do open WebUI from the docker it always opens the Unraid UI. I have changed toe default port from 8080 to 8180 And I also tride to change the WebUI in the docker to http://[IP]:8180 But it always go to the Unraid UI any way around this? I have multiple Wordpress dockers and I would like not to remember all the different ports LOL

Ok got the error again replaced the USB with a brand new same model as existing one the Samsung USB: So created a new Unrad installation and copied all the config folder to the new stick, but it just hangs at: So I tried the old USB again and it boots up.... (I know it will fail again soon) Can anyone explain this? (I followed the recover guide, and also downloaded yesterdays Flash backup and restored the config folder) Thanks all

Ok I made the backup USB but before that I just moved the existing USB to another port and it worked? I have never in all my years of Unraid have this happen? Should I replace the USB (Its not that old and on the recommended list) or just keep the existing one? What do you recommend?