guyyst
Members
-
Joined
-
Last visited
-
If an Unraid server on the local IP 10.1.1.20 is behind a reverse proxy on example.com, the URL you get when attempting to open a VNC console to a VM looks like this: https://example.com/plugins/dynamix.vm.manager/vnc.html?v=1746576860&resize=scale&autoconnect=true&host=10.1.1.20&port=&path=/wsproxy/5700/ Opening this URL won't work, but just changing host=10.1.1.20 to host=example.com will make it load just fine, provided the reverse proxy is set up properly. I figured it should be possible for the context menu option VM Console (VNC) to use the host currently open in the browser as the parameter for the VNC URL.
-
Alright I figured it out, kind of. I did a grep through all the config files in the 'dockerMan' folder to find where '8080' might still be listed. It was still set as the default value for the WEBUI_PORT variable, so I changed that to 9090 as well. After that I could set the 'WebUI' to whatever I want. (Even a hard coded link like 'https://google.com', which... why was that previously prevented by an old default port in WEBUI_PORT ?) Also, changing the default value of WEBUI_PORT back to 8080 doesn't get me back into the broken state I was in before. So I really don't know what was going on there, but for anyone else having trouble with this, try changing the default value of WEBUI_PORT ¯\_(ツ)_/¯
-
From the description I feel like that's exactly what this setting is for: Again, my other docker containers behave exactly the way this description says they should, qbitorrent is the only outlier so far. Of course this isn't a huge deal, and a bookmark is an O.K. workaround, it's just a bit irksome when I know that 1 out of my 10 containers is always slightly wrong :p
-
I successfully changed the default web UI port to '9090' after adding a manual port configuration to set the new port on both the host and container side. The web UI is now available under 'http://<local-ip>:9090'. I also changed the actual 'WebUI' configuration field (hidden behind 'Advanced View') to match the new port, in order for the 'WebUI' option in the Unraid context menu on the qbittorrent container to point to the new location, but this change seems to just get ignored. I tried to change this option on some other containers and they update just fine. I can put in 'https://google.com' and they happily link to that. I rebooted the array/server a couple of times to make sure, but the qbitorrent container context menu always points to 'http://<local-ip>:8080'. The 'WebUI' option doesn't get reset and stays on whatever I last set it to, but it's just ignored.
