search

truecharts / public

Community Helm Chart Repository
https://truecharts.org
GNU Affero General Public License v3.0
1.15k stars 619 forks source link

Deluge does not expose the daemon port, making it impossible to connect to it from the gui #7868

Closed gordallott closed 1 year ago

gordallott commented 1 year ago

App Name

deluge

SCALE Version

22.12.0

App Version

2.1.1_13.0.13

Application Events

2023-04-04 23:52:46
Add eth0 [172.16.0.87/16] from ix-net
2023-04-04 23:52:46
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:52:46
Container image "tccr.io/truecharts/deluge:v2.1.1@sha256:580631efe42039df06ce28e90e59a6a2e4a23a1970eaa24a4b2f783166e74b36" already present on machine
2023-04-04 23:52:46
Created container deluge
2023-04-04 23:52:46
Started container deluge
2023-04-04 23:52:45
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:52:45
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:52:44
Created pod: deluge-5d45dbd5c4-mx5qc
2023-04-04 23:52:44
Successfully assigned ix-deluge/deluge-5d45dbd5c4-mx5qc to ix-truenas
2023-04-04 23:52:43
Job completed
2023-04-04 23:52:43
Ensuring load balancer
2023-04-04 23:52:43
Ensuring load balancer
2023-04-04 23:52:43
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-5568d58c
2023-04-04 23:52:43
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-b83b3e6f
2023-04-04 23:52:43
Ensuring load balancer
2023-04-04 23:52:43
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-udp-ac9b886f
2023-04-04 23:52:36
Add eth0 [172.16.0.83/16] from ix-net
2023-04-04 23:52:36
Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:6d6e0e50f28b961ed1c1c6a9c140553238641591fbdc9ac7c1a348636f78c552" already present on machine
2023-04-04 23:52:36
Created container deluge-manifests
2023-04-04 23:52:36
Started container deluge-manifests
2023-04-04 23:52:35
Created pod: deluge-manifests-gtvfg
2023-04-04 23:52:35
Successfully assigned ix-deluge/deluge-manifests-gtvfg to ix-truenas
2023-04-04 23:50:42
Readiness probe failed: dial tcp 172.16.0.82:8112: connect: connection refused
2023-04-04 23:50:33
Deleting load balancer
2023-04-04 23:50:33
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-098909f3
2023-04-04 23:50:33
Deleted load balancer
2023-04-04 23:50:33
Deleting load balancer
2023-04-04 23:50:33
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-19a2c331
2023-04-04 23:50:33
Deleted load balancer
2023-04-04 23:50:33
Deleting load balancer
2023-04-04 23:50:33
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-udp-d62f213f
2023-04-04 23:50:33
Deleted load balancer
2023-04-04 23:50:33
Deleted pod: deluge-5d45dbd5c4-bqpvr
2023-04-04 23:50:33
Stopping container deluge
2023-04-04 23:50:04
Started container deluge
2023-04-04 23:50:04
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:50:03
Add eth0 [172.16.0.82/16] from ix-net
2023-04-04 23:50:03
Container image "tccr.io/truecharts/deluge:v2.1.1@sha256:580631efe42039df06ce28e90e59a6a2e4a23a1970eaa24a4b2f783166e74b36" already present on machine
2023-04-04 23:50:03
Created container deluge
2023-04-04 23:50:03
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:50:03
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:50:01
Job completed
2023-04-04 23:50:01
Ensuring load balancer
2023-04-04 23:50:01
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-19a2c331
2023-04-04 23:50:01
Ensuring load balancer
2023-04-04 23:50:01
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-098909f3
2023-04-04 23:50:01
Ensuring load balancer
2023-04-04 23:50:01
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-udp-d62f213f
2023-04-04 23:50:01
Created pod: deluge-5d45dbd5c4-bqpvr
2023-04-04 23:50:01
Successfully assigned ix-deluge/deluge-5d45dbd5c4-bqpvr to ix-truenas
2023-04-04 23:49:53
Add eth0 [172.16.0.78/16] from ix-net
2023-04-04 23:49:53
Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:6d6e0e50f28b961ed1c1c6a9c140553238641591fbdc9ac7c1a348636f78c552" already present on machine
2023-04-04 23:49:53
Created container deluge-manifests
2023-04-04 23:49:53
Started container deluge-manifests
2023-04-04 23:49:52
Created pod: deluge-manifests-hh7w7
2023-04-04 23:49:52
Successfully assigned ix-deluge/deluge-manifests-hh7w7 to ix-truenas
2023-04-04 23:49:20
Readiness probe failed: dial tcp 172.16.0.77:8112: connect: connection refused
2023-04-04 23:49:15
Deleting load balancer
2023-04-04 23:49:15
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-695156c1
2023-04-04 23:49:15
Deleted load balancer
2023-04-04 23:49:15
Deleting load balancer
2023-04-04 23:49:15
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-udp-ff303cad
2023-04-04 23:49:15
Deleted load balancer
2023-04-04 23:49:15
Deleting load balancer
2023-04-04 23:49:15
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-134f839e
2023-04-04 23:49:15
Deleted load balancer
2023-04-04 23:49:15
Deleted pod: deluge-5d45dbd5c4-6gwlx
2023-04-04 23:49:15
Stopping container deluge
2023-04-04 23:48:11
Add eth0 [172.16.0.77/16] from ix-net
2023-04-04 23:48:11
Container image "tccr.io/truecharts/deluge:v2.1.1@sha256:580631efe42039df06ce28e90e59a6a2e4a23a1970eaa24a4b2f783166e74b36" already present on machine
2023-04-04 23:48:11
Created container deluge
2023-04-04 23:48:11
Started container deluge
2023-04-04 23:48:11
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:48:11
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:48:11
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:48:09
Job completed
2023-04-04 23:48:09
Ensuring load balancer
2023-04-04 23:48:09
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-134f839e
2023-04-04 23:48:09
Ensuring load balancer
2023-04-04 23:48:09
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-695156c1
2023-04-04 23:48:09
Ensuring load balancer
2023-04-04 23:48:09
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-udp-ff303cad
2023-04-04 23:48:09
Created pod: deluge-5d45dbd5c4-6gwlx
2023-04-04 23:48:09
Successfully assigned ix-deluge/deluge-5d45dbd5c4-6gwlx to ix-truenas
2023-04-04 23:48:09
Scaled up replica set deluge-5d45dbd5c4 to 1 from 0
2023-04-04 23:48:01
Add eth0 [172.16.0.73/16] from ix-net
2023-04-04 23:48:01
Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:6d6e0e50f28b961ed1c1c6a9c140553238641591fbdc9ac7c1a348636f78c552" already present on machine
2023-04-04 23:48:01
Created container deluge-manifests
2023-04-04 23:48:01
Started container deluge-manifests
2023-04-04 23:48:00
Created pod: deluge-manifests-87zzp
2023-04-04 23:48:00
Successfully assigned ix-deluge/deluge-manifests-87zzp to ix-truenas
2023-04-04 23:47:12
Readiness probe failed: dial tcp 172.16.0.72:8112: connect: connection refused
2023-04-04 23:47:05
Deleting load balancer
2023-04-04 23:47:05
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-udp-bc1d8b96
2023-04-04 23:47:05
Deleted load balancer
2023-04-04 23:47:05
Deleting load balancer
2023-04-04 23:47:05
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-884b2f44
2023-04-04 23:47:05
Deleted load balancer
2023-04-04 23:47:05
Deleting load balancer
2023-04-04 23:47:05
Deleted LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-2f998a5d
2023-04-04 23:47:05
Deleted load balancer
2023-04-04 23:47:05
Deleted pod: deluge-5d45dbd5c4-lppm5
2023-04-04 23:47:05
Stopping container deluge
2023-04-04 23:47:05
Scaled down replica set deluge-5d45dbd5c4 to 0 from 1
2023-04-04 23:43:03
Created container deluge
2023-04-04 23:43:03
Started container deluge
2023-04-04 23:43:02
Add eth0 [172.16.0.72/16] from ix-net
2023-04-04 23:43:02
Container image "tccr.io/truecharts/deluge:v2.1.1@sha256:580631efe42039df06ce28e90e59a6a2e4a23a1970eaa24a4b2f783166e74b36" already present on machine
2023-04-04 23:43:01
Successfully assigned ix-deluge/deluge-5d45dbd5c4-lppm5 to ix-truenas
2023-04-04 23:43:00
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:43:00
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:43:00
Updated LoadBalancer with new IPs: [] -> [192.168.1.108]
2023-04-04 23:42:59
Successfully provisioned volume pvc-11fadf9a-f203-4d46-b1f4-c20e2d39eb8a
2023-04-04 23:42:59
0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
2023-04-04 23:42:57
Job completed
2023-04-04 23:42:57
External provisioner is provisioning volume for claim "ix-deluge/deluge-config"
2023-04-04 23:42:57
waiting for a volume to be created, either by external provisioner "zfs.csi.openebs.io" or manually created by system administrator
2023-04-04 23:42:57
Ensuring load balancer
2023-04-04 23:42:57
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-2f998a5d
2023-04-04 23:42:57
Ensuring load balancer
2023-04-04 23:42:57
Scaled up replica set deluge-5d45dbd5c4 to 1
2023-04-04 23:42:57
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-torrent-udp-bc1d8b96
2023-04-04 23:42:57
0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
2023-04-04 23:42:57
Created pod: deluge-5d45dbd5c4-lppm5
2023-04-04 23:42:57
Ensuring load balancer
2023-04-04 23:42:57
Applied LoadBalancer DaemonSet kube-system/svclb-deluge-884b2f44
2023-04-04 23:42:50
Add eth0 [172.16.0.68/16] from ix-net
2023-04-04 23:42:50
Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:6d6e0e50f28b961ed1c1c6a9c140553238641591fbdc9ac7c1a348636f78c552" already present on machine
2023-04-04 23:42:50
Created container deluge-manifests
2023-04-04 23:42:50
Started container deluge-manifests
2023-04-04 23:42:49
Created pod: deluge-manifests-22svr
2023-04-04 23:42:49
Successfully assigned ix-deluge/deluge-manifests-22svr to ix-truenas

Application Logs

--

Application Configuration

image

Describe the bug

deluge clients like deluge-gtk require the deamon to be exposed on whatever the daemon port is, the webui also uses this mechanism but it's launched by the server itself so doesn't need to route through k8s.

for deluge-gtk/flexget/others to be able to interact with deluge they need this port exposed however, the default value is 58846

To Reproduce

  1. install the deluge app
  2. open the webui
  3. click on preferences, select daemon and tick Allow Remote Connections
  4. attempt to connect deluge-gtk to your truecharts provided deluge server (it will fail as the port isn't exposed)

Expected Behavior

deluge-gtk should be able to connect to the webui

Screenshots

--

Additional Context

--

I've read and agree with the following

PrivatePuffin commented 1 year ago

We allow unlimited custom ports to be exposed.

closed, as enhancement requests are not bugs.

truecharts-admin commented 1 year ago

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists