st1994

Yep that totally did it. Thanks a million for the quick response and even the fact you brought this over for us. Much appreciated.

Hi there, recently discovered this container, and i got it working and going. Now i'm trying to route this other unraid container thru it: https://github.com/crazy-max/docker-rtorrent-rutorrent My issue is: after i've pointed rutorrent to gluetun with the "--net=container:GluetunVPN" paramater, rutorrent will not load. I forwarded the other 3 ports the rutorrent container needed: 6881/50000 and i think it was 8080. But once rutorrent is started, it throws this error: 024/02/15 11:11:10 [emerg] 1084#1084: bind() to 0.0.0.0:8000 failed (98: Address in use) nginx: [emerg] bind() to 0.0.0.0:8000 failed (98: Address in use) It appears the HTTP_CONTROL_SERVER_PORT is conflicting with the rutorrent container, per this comment: https://github.com/crazy-max/docker-rtorrent-rutorrent/issues/184#issuecomment-1344582850 He suggests I change it; I did so in the docker container settings for Gluetun, but when i restart the container, it still binds to the same 8000 port -- any advice on how i can change it permanently to another port? Thanks!

searched the forums and saw nothing mentioning this, but i wanted to get this docker image installed in unraid: https://hub.docker.com/r/kannibalox/autotorrent2 i can get it installed, but it doesn't actually work. Alternatively, I can install the actual program itself, in the unraid OS https://github.com/JohnDoee/autotorrent2 And that works, but when i run the command needed to connect to my torrent client (binhex-qbittorrentvpn) for example, it can't connect because i dont know how to point it to a docker container? at2 test-connection No clients found I'm sure it's super simple, i'm just kinda new still and don't know how to overcome this. Thanks for your time.

Sadly this didn't fix the issue. Still having the same problem where NPM doesn't start properly after i back up the container nightly.

Thanks, i'll look into downgrading my container version.

My apologies -- I was wrong; it was in fact the backup plugin that i'm using to back up my docker containers nightly that's causing the restart. After the containers restart is when I encounter this issue.

Hi There, I use the auto-update plugin nightly to update my docker apps. For whatever reason, when the NPM docker container restarts, i'd say 6 out of 10 times, it won't actually work. I won't notice until later on in the day when i can't access any of my websites. If i manually shut down and start the container again, NPM works properly. The only error i get is "connection refused" and here's what's showing up in the logs: text error warn system array login s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service prepare: starting id: 'npmuser': no such user s6-rc: fatal: timed out /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. s6-sudoc: fatal: unable to get exit status from server: Operation timed out ❯ Configuring npmuser ... Hoping somebody can help me figure out why this is happening. Thanks,

Thanks for this -- one thing i've noticed. I'll create and customize my tmux.conf but after restart it's gone. How can I make it persist after restarting?

Hi, New to unraid and docker pretty much, i'm sure this is a config issue, but when i play a file in plex, it shows as WAN instead of the LAN? Not sure what's wrong, but would appreciate guidance and/or help. I can provide screenshots or configs, or whatever. But plex is on 192.168.1.4 and my device is 192.168.1.57 so it's the same subnet and everything, but tautulli shows it as WAN traffic instead of LAN traffic... thanks. edit: I messed with the network mode moved to the nic and then back to "host" mode and now it's showing up on LAN properly. Weird.

I'm encountering the same -- but also have the same question -- where are the conf files stored? Like where is tmux.conf etc when using this plugin?

Thanks for this. I just installed unraid and just joined the forums to say thanks. This helped me solve the same issue.