KrypticKahos

I have used unbalanced in the past but now anytime I try to login I only get the "Something went wrong" error. This last attempt was after a reboot, and then also tried by removing and re-adding the plugin. I have also attempted with different ports and with/without authentication. Also checking the logs I don't see any error being thrown. Any idea on this? I'm not even sure where else to check for other issues causing this problem. May 28 13:33:06 Apollo plugin-manager: unbalanced.plg removed May 28 13:35:59 Apollo plugin-manager: creating: /boot/config/plugins/unbalanced/unbalanced-2026.05.17.tgz - downloading from URL "https://github.com/jbrodriguez/unbalance/releases/download/2026.05.17/unbalanced-2026.05.17.tgz" May 28 13:36:03 Apollo plugin-manager: checking: /boot/config/plugins/unbalanced/unbalanced-2026.05.17.tgz - MD5 May 28 13:36:03 Apollo plugin-manager: creating: /boot/config/plugins/unbalanced/unbalanced.cfg - from INLINE content May 28 13:36:07 Apollo plugin-manager: creating: /boot/config/plugins/unbalanced/unbalanced.env - from INLINE content May 28 13:36:07 Apollo plugin-manager: executing inline script: /bin/bash '/tmp/inline4-unbalanced.sh' May 28 13:36:07 Apollo plugin-manager: creating: /tmp/unbalanced-chkconf - from INLINE content May 28 13:36:07 Apollo plugin-manager: running: /bin/bash /tmp/unbalanced-chkconf May 28 13:36:07 Apollo plugin-manager: unbalanced.plg installed May 28 13:36:52 Apollo ool www[173617]: /usr/local/emhttp/plugins/unbalanced/scripts/start May 28 13:36:52 Apollo sudo: root : PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c 'set -a; source "/boot/config/plugins/unbalanced/unbalanced.cfg"; source "/boot/config/plugins/unbalanced/unbalanced.env"; set +a; "/usr/local/emhttp/plugins/unbalanced/unbalanced" --port "7090"' May 28 13:36:52 Apollo sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 28 13:38:11 Apollo ool www[173617]: /usr/local/emhttp/plugins/unbalanced/scripts/stop May 28 13:38:11 Apollo sudo: pam_unix(sudo:session): session closed for user root May 28 13:38:18 Apollo ool www[173181]: /usr/local/emhttp/plugins/unbalanced/scripts/stop May 28 13:38:23 Apollo ool www[173617]: /usr/local/emhttp/plugins/unbalanced/scripts/start May 28 13:38:23 Apollo sudo: root : PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c 'set -a; source "/boot/config/plugins/unbalanced/unbalanced.cfg"; source "/boot/config/plugins/unbalanced/unbalanced.env"; set +a; "/usr/local/emhttp/plugins/unbalanced/unbalanced" --port "33104"' May 28 13:38:23 Apollo sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)

I was also starting to receive a EHOSTUNREACH error when attempting to connect Overseer to radarr or sonarr. I was running the docer in host mode, but have sense changed it and gave it a custom IP address. This has sense resolved my issues.

If anyone else is having issues with the stun-turn server here is how I set mine up. The one issue I really found is that nextcloud never gave me a good test for the turn server, however I was able to test my instance and verify it was working with my settings. Here is everything I did to make it work. Unraid Stun-Turn-Server With NextCloud Talk Instructions This assumes that you already have a working nextcloud installation with correctly working reverse proxy. 1. Install and configure the Stun-Turn-Server Docker Container a. Install Stun-Turn-Server from community applications b. It is suggested to use a custom IP address for this docker container. This will make port forwarding easier and. you don’t have to worry about conflicting IP addresses and ports. c. Read through the different options when installing, but you will need to change the following. i. Static Secret – follow the instructions as listed. Keep this value as it will need to be used later in the. nextcloud instance. ii. Realm – In most cases this should be the same as your reverse domain name for you nextcloud instance that points to your public IP. In my example it is: turn:nextcloud.yourdomain.com iii. Certificate Generation – Country – Put in your two character country code. For United States it will be: US iv. Certificate Generation – State or Providence– Put in your state or providence v. Certificate Generation – Locality – A more specific location than state or Providence vi. Certificate Generation – Origination – What the nextcloud instance is called d. Those should be all of the required values. Apply the config and allow the docker to pull down 2. Port forward UDP and TCP port 5349 from your firewall to the custom IP used for the Stun Turn server. It is suggested to use this port but it can be changed if needed. The exact steps to port forward depend on your network configuration and firewall. I won’t cover the specific steps for this. 3. Test the server is working correctly a. Visit the website below to test the server: https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ b. Click on the default stun server and remove it. c. In the STUN or TURN URI input the following values individually then click add server. Note for my instance I’m using the default stun server. I was not able to get the installed server stun option to work. i. stun: stun.nextcloud.com:443 ii. turn:nextcloud.yourdomain.com:5349 d. Scroll down to ICE options, and use all IceTransport Values e. Click gather candidates f. If successful you should see multiple hosts listed for UDP and TCP as well as your public IP address as srflx type. The hosts indicate a working turn server and srflx with IP address indicates a working stun server. 4. Nextcloud Integration a. Login to your nextcloud account as admin. b. Go to admin > administration settings > Under administration go to talk c. Scroll down to STUN and TURN server settings d. For Stun I’m using the default: stun.nextcloud.com:443 e. For TURN fill out the fields as follows: i. Turn and Turns: ii. Turn server URL: 1. nextcloud.yourdomain.com:5349 iii. Turn Server Secret: 1. The value from step one that was generated with a terminal command. iv. UDP and TCP f. NOTE: During my setup I was not able to get a successful test using the button next to the UPD and TCP selection. There may be a bug with how it operates. I was able to verify correct operation through various tests. There is a good chance I did something wrong but I will update this as I get feedback. In the mean time I hope it helps others with confusion they may have.

Did some more testing and C-states were already disabled, and setting PCIe generation didn't help either. Turns out it was because I had an odd hardware configuration. I had my GPU in the secondary PCIe slot, and my HBA card in the primary GPU slot. I did this previously because I wanted maximum bandwidth to the hard drives. Turns out that my motherboard didn't like that setup. I put the GPU in the primary slot, and HBA in the secondary and now the GPU is showing up and everything is working as expected.

BIOS was updated, and you were correct. The notes for the new version had fixes for 40 series card compatibility. This however didn't resolve my issues. I will also go and attempt disabling C-states, and forcing the PCIe generation.

I previously had a 1050Ti GPU installed without issues being used with dockers for transconding. I just put in a 3050 and get no device found. nvidia-smi output gives "No Devices were Found" VFIO is unbound. Graphics card seems functional as I have video out on the card during bootup. Diagnostics are attached. I have also tried multiple driver versions, allowing it to fully download and install and rebooted. Have any other input on why it may not be visible? sv1-diagnostics-20230829-1543.zip

Sure enough. Didn't even think of that as a possibility but its correct.

So it would appear that I may have found a bug regarding Key_3 VNC Password, and am not sure if this could be an issue on the docker image side or the noVNC side. I setup a password for Key_3, but when accessing the webgui I can get in with 70% of the password correct, or any combination of characters after the correct password. I have also attempted to change the password with similar results. For example if I set Key_3 to Password123, I am able to get to the gui with Password or Password1234567890. This isn't critical for my application and I haven't seen anyone else on here or the noVNC github with a similar issue. But it might be something to look into. If it's likely more of an issue with noVNC I'll post an issue on github.

Correct. I have tried with somewhere between 5-10 DVDs and I am not using a CC track. makeMKV will report a disk read speed of between 2.5-3x but it will still take the 2+ hours to complete. Connecting the optical drive to a windows OS or Mac OS computer will give the expected speed with about 15min to complete in makeMKV.

First off great work on this docker. For the most part I've had great success with blu-ray and 4K. I am now having issues with ripping DVDs. I will initially get quick speeds but then it quickly slows down where the rip time will go up to 2 hours a disk. The optical drive setup works fine with blu-ray and will finish in about 30min. Rips are going to an external unassigned devices drive and I have attempted privileged mode with same results. Same result with any DVD I attempt to rip. I also have both devices passed through in docker advanced. Any idea what could be going on?