Andiroo2

Same here.

Did you ever resolve this? I found this thread while looking for information on pinning VM CPUs and I see that you have pinned CPU 0/1 to your VM. Everything I read says that you should not pin these, but you should ISOLATE these cores so that Unraid can use them exclusively for system management.

As suddenly as it started, my issue has disappeared. The container is working as expected again.

Docker Inspect QDirStat.txtQDirStat Logs.rtf Logs attached. I updated the container, no change. I also installed another QDirStat container and have a similar issue (not exactly, but similar). Something is wonky in my display driver perhaps?

Unclear...I opened it up like I usually do and it's just not working for me. Perhaps it's just me then if nobody else is reporting issues. It's been a few months since I last used it.

This container is suddenly not working for me (after many years). I get a black screen when I load the WebUI, and I see this in the logs: [xvnc ] Underlying X server release 12101021 [xvnc ] MESA-LOADER: failed to open iris: Error loading shared library /usr/lib/xorg/modules/dri/iris_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open kms_swrast: Error loading shared library /usr/lib/xorg/modules/dri/kms_swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open swrast: Error loading shared library /usr/lib/xorg/modules/dri/swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open iris: Error loading shared library /usr/lib/xorg/modules/dri/iris_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open kms_swrast: Error loading shared library /usr/lib/xorg/modules/dri/kms_swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open swrast: Error loading shared library /usr/lib/xorg/modules/dri/swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open iris: Error loading shared library /usr/lib/xorg/modules/dri/iris_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open kms_swrast: Error loading shared library /usr/lib/xorg/modules/dri/kms_swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] MESA-LOADER: failed to open swrast: Error loading shared library /usr/lib/xorg/modules/dri/swrast_dri.so: No such file or directory (search paths /usr/lib/xorg/modules/dri, suffix _dri) [xvnc ] Fri Feb 20 09:33:45 2026 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900 [xvnc ] vncext: Created VNC server for screen 0 [xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x1510c2e4f0bd for event 2 [xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x1510c2e4f0bd for event 3 [supervisor ] starting service 'openbox'... [supervisor ] starting service 'xcompmgr'... [supervisor ] starting service 'dbus'... [supervisor ] starting service 'xrdb'... [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [supervisor ] starting service 'app'... [supervisor ] all services started. [supervisor ] service 'xrdb' exited (with status 0). [app ] Logging to /config/log/qdirstat.log [xvnc ] Fri Feb 20 09:35:45 2026 [xvnc ] Connections: Accepted: /tmp/vnc.sock [xvnc ] SConnection: Client needs protocol version 3.8 [xvnc ] SConnection: Client requests security type None(1) [xvnc ] VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 [xvnc ] VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr888 I reinstalled the container and have the same issue...thoughts?

Where do I add this? Is this in the flash drive config page, under Syslinux config?

Update: It was my router. I changed from a Bell Giga Hub v1.0 to v2.0 and then all this started happening with my qBit access on VPN. I switched back to the Unifi Dream Machine Pro as my main router and all issues went away. Lesson learned -- ISP modem/routers are terrible.

Confirmed with PIA support that there is no limit to the number of connections or devices. Surely there IS a limit, but I am not hitting it. I did another test today though that (I think) eliminates the VPN as the issue. I set VPN_Enabled=No, loaded the WebUI and loaded a torrent. I then made sure it started transferring. I stopped the container, set VPN_Enabled=Yes and restarted the container. The torrent resumed and completed, because i was able to see it move from the in-progress folder to the completed folder. So, the VPN is connecting just fine, the app is loading, and it’s just the WebUI that isn’t loading. Where do I go from here? I don’t know, but now I will look at the network and IPTables.

No errors...see attached for a fresh restart and log file. supervisord.log

I have tried multiple different endpoints in different countries. I have also used the same OVPN file from the working container in the non-working containers, but that doesn’t help. I have copied the whole openvpn folder from the working container to the non-working one, but still the same result. Tried changing the IP of the container. Changing the WebUI port, changing my PIA password, port forwarding… I noticed that on my iOS app, I can connect but I don’t gat a VPN IP displayed on screen:

Been working on this one all day. Still no progress. I have gone through all 30 FAQs and added/removed/updated things to no avail. I can’t explain why one container works and another does not. The minute i disable VPN_ENABLED, it works immediately. Could there be an issue with PIA? Keep in mind this is affecting my binhex and non-binhex qbit containers (except one that inexplicably started working??)…

We’ll, one of my older qbit instances just started working again like nothing happened. No additional lines in the logs. Other instances are still down. It’s got to be an issue connecting to VPN somewhere.

I just went to the house, got on local network, disabled Tailscale in Unraid, restarted docker containers, same issue. As I was walking back I thought, maybe I should have rebooted the server with Tailscale disabled before trying again…I will try this next time I am back at the house.

Yes, I use Tailscale baked into Unraid to access my server remotely. I don’t want to turn this off for fear of losing access while troubleshooting. EDIT to add, I am NOT using Tailscale in the Docker container.