Duckbuster

I think it is written back to the file, just the wrong parameter name? I can test this and check it. EDIT: Ok maybe not and I was wrong. Wow wonder how I never noticed this then...

I literally never touched the rtorrent.rc file before. I always used the GUI to configure stuff. But yes, same thing happened to me on my dedicated server. Lot's of old parameters got depricated. Took me a while to find out which and where... (the documentation of both rtorrent and rutorrent is kinda bad)

I had the same issue. download_rate = 10000 upload_rate = 5000 is deprecated now or something? I replaced them with: throttle.global_down.max_rate.set_kb = 10000 throttle.global_up.max_rate.set_kb = 1000 And now it uses those every restart. Haven't tried update yet but so far so good.

@phil1c What I did to fix my UNMS a while back was to not host it using the host ip bridge, but giving it a new private IP address (its somewhere under main docker settings, that you need to enable the private ip range, then you can assign ip's on the docker interface) Then just made it so it doesn't use the 6443 ports but the actual 443 ports in the docker port mappings. Didn't have any PostgreSQL errors as far as I can tell. Will check the logs when I get home.

+1 from me too.

I tried UNMS (I own an EdgeRouter) The webgui runs, everything seems fine. But when try to connect to my EdgeRouter it fails, and I think I know why. I tries to connect back to UNMS but using port 443, not 6443. You can see this by looking into the EdgeRouter System config, there you see the UNMS url is pointed at port 443. I will try to look into this more tonight, maybe by changing the UNMS port in the software to 6443 and then changing the docker mapping to 6443 -> 6443 Or maybe I am just doing something wrong