wgstarks

Yeah, I checked mine after I saw your post and had the same issue. I was able to get mine working by whitelisting the local network in the qbittorrent settings>webui. This avoids authentication.

Looks like 4.6.0-1-01 was the most recent previous version.

I think perhaps you misunderstood. You would set the shares primary storage to “cache” and mover action to “array>cache” and mover will not move it off the cache disk. This setting will be in the share settings page.

Try manually setting the port in Plex.

Also, the LSIO dockers aren’t provided by Ubiquiti.

The old LSIO Unifi Controller docker is being deprecated and replaced by the Unifi Network App docker which requires a separate instance of MariaDB for the database. This docker is another Unifi Controller docker which will avoid the need for two dockers.

Are you saying you had to use the set-inform command?

I haven’t ever needed this but in the past many people have had to use set-inform. https://lazyadmin.nl/home-network/unifi-set-inform/

Mine didn’t need to be adopted after I went through the restore procedure. They were already connected.

Strange. I have exactly the same setup and no conflicts over port 1900.

What do you have set for “network type”? Should be bridge.

I would suggest posting this in the Radarr forum. There will be many more Radarr users there. I really think this is an issue related to the app rather than the container.

When I run FCP I see the log entries in the system log. Of course this support thread isn’t related to CA. The CA thread is here if that’s what you need help with.

You can see the logs in the system log. The icon is near the top of your browser window.

I think your best bet would be to start over with just the default configuration described in the first post in this thread.

Did I ever get what to work? If you’re referring to this docker then yes. It’s been working for me for several years.

Looks like a network issue. You have DNS errors repeating in your log.

Quote from the LSIO docker page If you search you’ll probably find a few discussions about the change but the basic reason LSIO is giving is that maintaining the Unifi Controller docker has been too much trouble. The complaint that I’m seeing most often regarding the new Unifi Network Application docker is that you also need to run a separate MongoDB docker. It’s not an all-in-one image. I did a little how-to post in the Controller support thread for switching to UNA. It’s really not very complicated to setup but it does add an extra point of failure.

I’m not a coder and wouldn’t be able to contribute in any productive way. Thanks though.

Use the dockerhub link on the first post to view tags. Once you decide which tag you want to use just add it to the repository field in the docker container configuration in the format binhex/arch-radarr:4.6.4.7568-1-01. No spaces. Replacing the tag in this example with the one you want. Then click “Apply” at the bottom of the page.

Worked properly. 👍

Update went smoothly. No issues. Didn’t test the permissions for appdata configuration though since that was already setup manually. Support link still directs to the project page though.

The docker never stopped as far as I could tell. I guess it’s possible that the docker restarted while I was watching the webUI and I didn’t notice. I had to manually restart the docker to gain access to the webUI after restoring.

Yes. There is actually a confirmation popup showing that a reboot is required and asking if the user wants to continue the restore process. If you select continue a notification will popup showing a restoring message. It doesn’t seem to ever go away. I waited a few minutes and then refreshed the window. IIRC I got a failed to connect message. Restarting the docker corrected the issue. I think this is probably a unifi issue. Just posting this in case anyone else has issues with the restore.

Another minor issue, if you have already installed the docker then the mkdir command will fail with directory already exists. Only the commands after that are needed. Also, I never got a popup window with the necessary commands to modify the appdata directory. Maybe you have done away with that??? I see that the instructions have been added to the pane in the Apps tab. Overall the install was unevenful because I knew what was required. I think many people won't though and will be posting for help with the install until you can get the initial permissions issue resolved (hopefully). There also seems to be an issue (probably with Unifi) where restores never complete. I noticed the same thing when installing UNA. The page just sits with a notification that the app is restoring. I had to refresh the page and in the case of this docker restart the docker.