practicing-haunch2956

I've been struggling with this for weeks now and cannot figure out what I'm doing wrong and am going in circles. Every video, forum, search seems to point to the "Tailscale Allow LAN Access" setting inside the container but it's not working for me. I'm attempting to serve up https access to individual containers outside the house but still access them locally via 192.168.0.x. I'm on Unraid 7, with the Tailscale plug-in installed, not the container. I have Gluetun running and connected to my VPN and set to be an exit node and approved in my Tailnet admin. In my container(s), I have the "Use Tailscale:" turned on, and chose "Use a Tailscale Exit Node:" and from the drop-down, chose Gluetun. Once applied, a curl in the container console shows traffic is routing out the VPN thru Gluetun. Machines showing Connected in my Tailnet. While I can now access the container using its tailscale address, I cannot access it locally using 192.168.0.x.

I have tried everything in this thread after my setup stopped working recently. I'm on 7.2-RC2 (all was working fine after upgrading). I'm running SRIOV to pass virtual instances of my i3 12100 GPU to plex, VM's etc. So in my Plex transcoder drop-down I have multiple Alder Lake UHD 730's to choose from. So that tells me that Unraid is passing thru these instances to Plex. In the Plex container I have tried both /dev/dri and drilling down to the specific instance /dev/dri/renderD128 (this was the instance that was working fine before). The plex preferences.xml is also correctly matched to the device ID (2.1, 2.2, etc) I also have GPU Stats and ich777's Intel GPU Top installed. GPU stats, when displaying loads (from a container that's working), only show up under the GPU1 box. I have Dispatcharr with a specific ffmpeg string that calls for /dev/dri/renderD129 and when playback starts, I see loads show up. I expected those to show up under the "GPU2" box on the Dashboard, but at least it's working. I don't know if it's related, but when in unraid's console and I type intel_gpu_top, I get an error Failed to detect engines. Any help would be greatly appreciated.

I'm wondering if that recently changed? I didn't have that added before and I had been using qbittorrent just fine until that last update. Strange. Anyway, that did the trick. Thank you so much.

Here you go. Thank you for taking a look... docker_run+supervisord.log

Unfortunately, even after rolling back to 4.6.0-1-01, adding the VPN IP's to the LAN_Network, I'm still unable to access the Web GUI, let alone face the password issue that other folks are having. I've even completely removed and re-installed 4.6.0-1-01 to no avail. Log shows the VPN is connected and WebGUI listening on the port I specified. I've also dropped a torrent file in the watched folder and saw that the file finished.