-
[Support] binhex - rTorrentVPN
@binhex Did you see my post from sunday ? Is there anything more I can test to sort things out?
-
[Support] binhex - rTorrentVPN
For another test I configured and started your arch-qbittorrentvpn container. Everything works. 0.8s on first start to do the chmod -R. docker-compose.yml: https://textuploader.com/1ddox log of the first start: https://textuploader.com/1ddog OK, Understood. So if I want to disable the authentification for the webui I have to edit the /config/nginx/config/nginx.conf?
-
[Support] binhex - rTorrentVPN
Thanks for this explanation. But the stange thing is... Your deluge container starts instantly (same environment... same puid pgid, same storage driver). This is from the log of your arch-delugevpn container: 2019-04-28 10:59:32.499692 [info] ENABLE_PRIVOXY defined as 'no' 2019-04-28 10:59:33.321485 [info] Starting Supervisor... What is different with the chmode/chown -R on die deluge docker? Maybe this consideration helps. I mean the rutorrent webui on port 9080. What du you mean with different?
-
wcd joined the community
-
[Support] binhex - rTorrentVPN
First of all: Thank you @binhex for all your hard work on the vpn-torrent containers. These are great! Only this rtorrent docker gives me headache. When I'm starting the docker for the first time it always takes around ten minutes to start. The log is stopping in every case at the same point. Full log: https://textuploader.com/1dd0u After: "2019-04-28 19:23:59.988292 [info] ENABLE_RPC2_AUTH defined as 'no'" and before: "2019-04-28 19:33:08.525499 [info] Starting Supervisor..." And nothing in between. Even with debug:yes there is not more information. My environment: OMV / Debian 9 Docker version 18.09.5, build e8ff056dbc I have tried docker-compose (prefered) but even with a plain docker command as mentioned here https://github.com/binhex/arch-rtorrentvpn (airvpn example) Further I have tried with all extra services off (even vpn). But everytime with the same result. Can you please help me out with this one? Edit: Ahhh, and by the way: ENABLE_RPC2_AUTH: "no" does nothing. I have to authenticate nevertheless.
wcd
Members
-
Joined
-
Last visited