ishcabittle

sorry it took a week to see this, but it was my understanding that the OP was going to change the way that this worked so it wouldn't conflict. My vnc.ini is now using environment variables as well: command=/usr/bin/x11vnc -display %(ENV_DISPLAY)s -frbport %(ENV_PORT_VNC)s -shared -forever I haven't touched this in a while, I set the networking to custom : br0 and have been playing things via a browser. I was going to check back and see if the template surfaced these variables but it doesn't look like that's the case.

Answered my own question: Open the Console of the container Edit: /etc/supervisor.d/vnc.ini Change both of the "5900" to "5909" or similar, your choice, just don't be the same port one of your VMs is running on.

Is there a way to change the port that noVNC is using? If you set the networking to "HOST", noVNC uses 5900 and that is already assigned to one of my VMs. I go to http://<unraidIP>:8083 and it brings up the noVNC connect page, when I click connect with audio enabled it bombs out, and when I click connect without audio I get to my pfSense VM.

Kudos for this, what an excellent surprise to find your container in the apps tab today! I didn't read "Option path to your games. This path will need to also be configured in Steam after the first boot." and installed a game to the /home/default/.steam directory, but that was fixed shortly thereafter. Thank you very much for this excellent container!

Thank you, glennv, that did the trick.

Could you describe this process? I am googling for this procedure and not finding anything significant.

Throwing my hat into the boot loop pile. At first I thought I was not following the directions precisely, but seeing others with the same experience I feel more confident I'm doing things correctly and it is just bugging out.