Opened 3 years ago

Last modified 3 years ago

#3475 new bug

Deluge in Podman Pod Won't Download

Reported by: Quantum Owned by:
Priority: blocker Milestone: needs verified
Component: Unknown Version: 2.0.3
Keywords: podman pod vpn wireguard Cc:


Fedora SilverBlue34 deluge-daemon - 2.0.3 : 13.fc34 deluge-web - 2.0.3 : 13.fc34 libtorrent - not installed

Created a podman image using buildah, installing deluge-daemon and deluge-web with dnf and started with systemd, and saved image to private registry.

Then created podman pod, which listens on 8112/tcp, 58744/tcp, and 58744/udp.

Spun up a container with podman run, drawing image from private registry, and setting volumes for torrents subdirs, and deluge config, and placing container in the pod.

Both daemons start fine in the container with no errors in the deluge log nor the podman log. I can access all aspects of deluge using Firefox and the web interface. I've set the correct incoming port in the daemon as well as a range of outgoing ports.

With a pod it must be set up to listen for incoming, but allows all outgoing from the pod. Then set firewall rules on the host for incoming and outgoing in nftables. In the (SilverBlue) router I've set the deluge incoming port to nat to the deluge virtual machine, and allowed outgoing ports to be masqueraded and forwarded.

From the router *all* LAN traffic goes out through a Wireguard interface to an AzireVPN PoP in Switzerland and then to the general internet.

All appears to be fine in the web interface except there are 0 connections, and IP is n/a (attached), and Tracker Status instantly goes to "Error: Connection Refused". There are no firewall errors in the deluge virtual machine nor the router virtual machine (regarding the deluge machine).

Attachments (1)

snap.jpg (125.1 KB ) - added by Quantum 3 years ago.

Download all attachments as: .zip

Change History (1)

by Quantum, 3 years ago

Attachment: snap.jpg added
Note: See TracTickets for help on using tickets.