Hi guys, lol this is funny, but im having the same issue almost 2 years to the DAY from before, when i posted in this thread. The old "waiting for deluge to start on port xxxxx". WebUi doesnt work. What I have done probably to cause this, is replace my cache drive, following SpaceInvader's video guide. All my other dockers work but this one. I have tried multiple branches, going back as far as 1.3 from almost 5 years ago. Multiple restarts of the container, still no WebUI. I thought it would be the most recent pulldown that caused it, but at this point im lost. As well, while writing this comment, the error in the log has disappeared and looks normal. Ill paste below. Still no WebUI.
2021-11-13 19:05:23.674424 [info] Starting Supervisor...
2021-11-13 19:05:23,965 CRIT Set uid to user 0
2021-11-13 19:05:23,965 INFO Included extra file "/etc/supervisor/conf.d/deluge.conf" during parsing
2021-11-13 19:05:23,972 INFO supervisord started with pid 7
2021-11-13 19:05:24,974 INFO spawned: 'deluge-script' with pid 40
2021-11-13 19:05:24,975 INFO spawned: 'deluge-web-script' with pid 41
2021-11-13 19:05:24,980 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy
[info] Starting Deluge daemon...
2021-11-13 19:05:24,980 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-13 19:05:24,980 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)