Hi!

I did something stupid, I first tried to add VueTorrent-UI to binhex-qbittorrentVPN but failed somehow and got 

Quote

Unacceptable file type, only regular file is allowed

when trying to open the web-UI. Removed what files I added for VueTorrent to /appdata and thought I'd try to remove the container and re-add it. Here's when I f*cked up. I had a few other containers routed through binhex-qbittorrentVPN and now the Docker tab is stuck in a rebuilding loop. I can't add the container back either since the "add container" box is greyed out. 

 

Is there a way to kill the rebuild via terminal without having to nuke everything? Or anyone have any other way of solving this to return to normal so I could try out VueTorrent again?

 

 

 

 

Edited January 30, 20224 yr by kim_sv
Solved

Ok, managed to edit all the containers that was network dependent on (routed through) binhex-qbittorrentVPN and that got me out of the loop. I set them to bridge instead. I then re-added the binhex-qbittorrentVPN container using the user template. But the problem with "Unacceptable file type, only regular file is allowed" still persist. Is there a way to edit some .conf or .json file to undo my previous mistake with trying to add an alternative web-UI? This really isn't my territory so bare with me if this is super simple to fix..

YES!  I managed to solve it! It was a typo in the alternative web-UI file path.

 

The solution was, after the above to get out of the loop, to stop all docker containers and edit the path line in qBittorrent.conf found in the appdata folder.

This is the line to look for if anyone is wondering:

Quote

WebUI\RootFolder=

 

For a novis like me it's a great satisfaction to be able to solve something myself. 🥳

 

You saved my ass here. This loop was driving me absolutely crazy, I was about ready to nuke the whole system. Thanks so much and nice job figuring it out!

 

So this pops up for more people who might be searching for the issue:

 

Unraid server docker container was stuck in a loop rebuilding because its network was set such that it was dependent on another docker that no longer existed. Simply editing the Docker attempting to rebuilt itself and changing the network solved the problem!

Edited July 21, 20223 yr by Bulletoverload
Apostrophe

2 years later ! Saved my ass too ! Thanks.

OMG>> THANKYOU>.. I had this looping action for a week with all my "rr stuff(sonarr,radarr etc.). changed the network type from none to bridge and it finished uninstalling. 

On 7/21/2022 at 1:55 AM, Bulletoverload said:

Simply editing the Docker attempting to rebuilt itself and changing the network solved the problem!

How did you edit while the UI was stuck on "rebuilding"? On 7.2.1, under input is disabled while a big swirly logo in overlaid on the screen preventing me from editing (or removing) the docker it 7.2.1 broke.

Edit: I was able to recover by issuing cli commands to stop the container that owned the "rebuilding" container network, then remove the container that was forgotten. Then I was able to re-create the lost container.

docker stop container1

docker rm container2

Edited November 20, 2025Nov 20 by Griz