i'm trying to get HTTPS web interface for transmission. Currently i can access transmission web interface with http://myip:8081 and what i want is to connect with https://myip/transmission . i already setup my lighttpd with TSL/SSL so i can access to default index page at https://myip I enabled mod_proxy lighty-enable-mod proxy Therefore, in /etc/lighttpd/conf-enabled, i have a 10-proxy.conf which is actually a symlink to /etc/lighttpd/conf-available/10-proxy.conf, and this file contains : server.modules += ( "mod_proxy" ) then in lighttpd.conf i added : $SERVER["socket"] == "0.0.0.0:443" { ssl.engine = "enable" ssl.pemfile = "/etc/lighttpd/certs/cert.pem" ssl.cipher-list = "ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM" ssl.honor-cipher-order = "enable" } $HTTP["url"] == "^/transmission/" { proxy.server = ("" => ( ( "host" => "127.0.0.1", "port" => 8081 )) ) } Then I reloaded lighttpd config service lighttpd force-reload Conf Syntax is OK but when i want to access to https://myip/transmission/ I've got a 404 not found page.

I'm using transmission-gtk 4.1.0-beta.2 on Devuan GNU/Linux Excalibur. My dmesg log is spammed with the following kind of message:

[Jul 4 14:47] audit: type=1400 audit(1751629628.491:75895): apparmor="ALLOWED" operation="open"
class="file" profile="transmission-gtk" name="/proc/sys/net/ipv6/conf/all/disable_ipv6"
pid=20126 comm="transmission-gt" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

` (originally all in one line, I broke it here for readability.) My network connection does have an IPv6 address (along with IPv4), even though I'm not intentionally making use of it. Anyway, I would like to have transmission-gtk stop trying to mess with it. Is that possible? If not, can I at least silence the repeating log message? Or get to only show up just once? --- FYI, on my system, I have:

# ls -la /proc/sys/net/ipv6/conf/all/disable_ipv6 
-rw-r--r-- 1 root root 0 Jul  4 13:59 /proc/sys/net/ipv6/conf/all/disable_ipv6

I am running transmission-daemon version 3.00 on Debian Bookworm. I was messing around with permissions on my setup and I seem to have borked the transmission-daemon's ability to access its usual directory. As of a few days ago transmission can no longer find the torrents, occasionally tries to create the specified (already existing) directory, and can no longer download new media from magnet links. (Note that /home//Downloads is a symlink to /data/Downloads.) These are the relevant errors in the 'journalctl' log:

Couldn't create "/home//Downloads/tmp": Permission denied (file-posix.c:243)
 No data found! Ensure your drives are connected or use "Set Location". To re-download, remove the torrent and re-add it. (torrent.c:574)

Here are the permissions on the relevant directory tree:

permission : directory
777 : /data
777 : /data/Downloads
775 debian-transmission:debian-transmission /data/Downloads/tmp

Oh, and my user account is in the debian-transmission group, and the user debian-transmission is in my user group. EDIT: My home folder (/home/) had restrictive permissions (700). Feel so dumb for missing that. Changed to 775 and everything is back to normal. Gotta remember that namei -l command.

I'm using the following .. fping -c1 computer I get 0% packet loss when I run it manually from the terminal. I get 0% packet loss when I run it from a script, ~/scripts/torrent.done.script. But I get 100% packet loss when transmission-daemon triggers, and runs the script. computer : xmt/rcv/%loss = 1/0/100% I'm at a loss trying to figure this out. I tried specifying the IP address explicitly, I tried using only IPv4 but same results. I tried with a public IP address, same results. It tried with a VPN and without, same results. ping works, fping does not. So bizarre, to me.

> transmission 4.0.5-1 > Arch 6.8.5-arch1-1 I want to edit /var/lib/transmission/.config/transmission-remote/settings.json. Permissions on that file are 600 for transmission:transmission My user is in the transmission group so I run chmod 660 settings.json and make my changes I could make the changes as root but I prefer this approach. However Transmission resets permission on every stop/start so I have to do this every time I want to make a change to the file. I must be doing it wrong. What is the preferred approach here?

I need to read the output table of transmission-remote to determine if a download is taking place. This is currently achieved with trans="transmission-remote 0.0.0.0:9092 -n $user:$pass -l" [ "$($trans | awk '! /awk/ && /n[/]a/ {print $2}')" == "n/a" ] \ || [[ $($trans | awk '! /awk/ && /%/ {print substr($2, 1, length($2)-1)}' | sort -n | head -n 1) -lt 100 ]] It's looking for either the presence of string 'n/a' or a completion of <100%. The way it's written it must probe 'transmission-remote' twice for the same table. Sample table output: ID Done Have ETA Up Down Ratio Status Name 1 100% 3.38 GB Done 0.0 0.0 1.00 Finished Fish Documentary.mkv 2 100% 5.87 GB Unknown 0.0 0.0 0.00 Idle Ethical Coding.pdf 3 100% 1.33 GB Done 0.0 0.0 1.99 Finished Bacon.jpg 4 100% 1.26 GB Unknown 0.0 0.0 0.00 Idle Eggs.png 5 100% 10.89 GB Done 0.0 0.0 1.00 Finished Invest in gold.pdf Sum: 23.63 GB 0.0 0.0 Is it possible to combine the awk arguments into one, or perhaps someone could suggest an easier or cleaner way to achieve the desired outcome? The ultimate goal is to have the red LED on the NAS flash red when a download is taking place, and turn solid white when all downloads have completed. The original script is here: https://pastebin.com/tKXc8mFW

Trying to setup permissions for the plugins sickbeard / couchpotato. I’ve read almost every thread google / the forums have but haven’t really found a solution yet. I’m assuming it’s the data here: (Jail name)/usr/pbi/xxxxxxxxxx I tried: chown -R guest:guest /usr/pbi/sickbeard-amd64/* chown -R guest:guest /usr/pbi/couchpotato-amd64/* But I couldn’t get it to work. Or would I have to chmod 777 the folders?

I currently have transmission running on a PC running Ubuntu desktop which I leave running continuously. It currently has over a hundred torrents in various levels of activity uploading and downloading. I want to move these onto an Ubuntu Server system running transmission-remote on a more energy efficient former thin wire client machine. I am hoping that transmission stores all the torrent data somewhere and that it is compatible between the GUI version on my Ubuntu desktop and the remote system I intend to set up on my Ubuntu Server system. Can it be done and if so any advice/information very welcome.

I have a script that downloads an iso using transmission-cli, but while searching for information on another transmission command issue, I find this So I can do this:

transmission-cli magnet:?xt=urn:btih:375ae3280cd80a8e9d7212e11dfaf7c45069dd35&dn=archlinux-2023.02.01-x86_64.iso

But I can't do:

transmission-remote magnet:?xt=urn:btih:375ae3280cd80a8e9d7212e11dfaf7c45069dd35&dn=archlinux-2023.02.01-x86_64.iso

Trying to do this:

transmission-remote -a magnet:?xt=urn:btih:375ae3280cd80a8e9d7212e11dfaf7c45069dd35&dn=archlinux-2023.02.01-x86_64.iso

results in this:

transmission-remote:  (http://localhost:9091/transmission/rpc/) Couldn't connect to server

I've installed, configured and ran transmission-daemon on my CentOS 6 machine using service transmission-daemon start This works nicely, and I can see the web interface on http://server.ip:9091 as I need to. The problem is, that several minutes later, it spontaneously stops. Never says anything, without warning or error message. This happens even when I have no torrents active at all (as in, none on the list). I have no idea what's wrong, and the error logs I thought of (which probably isn't much) show nothing. How can I diagnose the causes for this? Has anyone else experienced a similar problem? ## EDIT After the suggestion Martin gave me, I got the log. It goes like this: [03:07:02.182] Transmission 2.13 (11501) started (session.c:624) [03:07:02.182] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:789) [03:07:02.182] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:962) [03:07:02.182] DHT Generating new id (tr-dht.c:384) [03:07:02.182] Using settings from "/var/lib/transmission/.config/transmission-daemon" (daemon.c:483) [03:07:02.182] Saved "/var/lib/transmission/.config/transmission-daemon/settings.json" (bencode.c:1683) [03:07:10.182] Port Forwarding State changed from "Not forwarded" to "???" (port-forwarding.c:95) [03:07:18.188] Searching for web interface file "/var/lib/transmission/.local/share/transmission/web/index.html" (platform.c:526) [03:07:18.188] Searching for web interface file "/usr/share/transmission/web/index.html" (platform.c:526) [03:07:24.189] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:241) It hangs on that last one until it dies. Now I've looked into [this question](https://askubuntu.com/questions/135178/transmission-remote-gui-setup-hangs-on-dht-attempting-to-bootstrap) , but my settings file is already owned by transmission, and even changing the permissions on the file to 775 didn't seem to have any effects. Any ideas?

I've installed Transmission on my Raspberry Pi with Raspbian on. Want to download torrents (legally of course) to an external hard drive. Permission is denied. root is owner and group for the drive I've tried to change permissions on the drive following a lot of different instructions here and other forums but can't make it. Found some information on that it's impossible to change permissions on a disk with exFAT. What workaround could I do? My main user is "pi" and I think that's the one Transmission uses. **EDIT: Add content to fstab**

proc            /proc           proc    defaults          0 0
PARTUUID=50913804-01  /boot/firmware  vfat    defaults    0 2
PARTUUID=50913804-02  /               ext4    defaults,noatime  0 1
# a swapfile is not a swap partition, no line here
# use  dphys-swapfile swap[on|off]  for that
UUID=67E3-17ED /mnt/67E3-17ED auto defaults,nofail 0 0
UUID=652F-FA93 /mnt/652F-FA93 auto defaults,nofail 0 0

**EDIT 2: lsblk --fs**

$ lsblk --fs
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS  
sda                                                                         
├─sda1       vfat   FAT32 EFI   67E3-17ED            196,9M     0% /mnt/67E3-17ED
└─sda2      exfat  1.0   8TB   652F-FA93              5,8T    20% /mnt/652F-FA93
mmcblk0              
├─mmcblk0p1  vfat   FAT32 bootfs D3E6-3F09                             436,8M    14% /boot/firmware
└─mmcblk0p2  ext4   1.0   rootfs cb6f0e18-5add-4177-ab98-e9f0235e06b3   42,7G    58% /

**EDIT 3: Changed fstab**

pi@raspberrypi:~ $ lsblk --fs 
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                         
|-sda1
|    vfat   FAT32 EFI   67E3-17ED                             196,9M     0% /mnt/67E3-17ED
`-sda2
     exfat  1.0   8TB   652F-FA93                               5,8T    20% /mnt/652F-FA93
mmcblk0
                                                                            
|-mmcblk0p1
|    vfat   FAT32 bootfs
|                       D3E6-3F09                             436,8M    14% /boot/firmware
`-mmcblk0p2
     ext4   1.0   rootfs
                        cb6f0e18-5add-4177-ab98-e9f0235e06b3   48,4G    54% /
pi@raspberrypi:~ $ ls -la /mnt
totalt 265
drwxr-xr-x  4 root root   4096 21 okt 16.28 .
drwxr-xr-x 18 root root   4096 10 okt 06.06 ..
drwxr-xr-x  4 root root 262144  7 nov 10.27 652F-FA93
drwxr-xr-x  2 root root    512  1 jan  1970 67E3-17ED

Thanks in advance for the help!

I have been working with Linux for a year now, but there are still some aspects of Linux that I'm struggling to understand. Currently, I am facing an issue related to setting the transmission power (tx power) of Bluetooth. I have attempted various methods and searched through multiple forums, but I have yet to find a solution. Here are the steps I have taken so far: - I used the hciconfig command to identify my Bluetooth device. - Next, I attempted to change the tx power using the following command: sudo hciconfig hci0 inqtpl 10 To verify if the tx power had indeed changed to 10, I ran the command: sudo hciconfig hci0 inqtpl The tx power remained the same as it was before the attempted change. How can I solve this?

For some reason, my DNS provider blocks torrent trackers as it appears. (Proven by connecting to my VPN provider with his DNS which solves the DNS problem.) But generally speaking, I otherwise like this DoT solution. I am running Linux Mint 21.1 Cinnamon with Transmission-GTK 4.0.3. I would like to change DNS for the torrent app only. Is this possible? (Heading to bed, and will reply to all comments or answers in the morning.)

I have my working on default port and I want to be able to use the web interface with an URL like http://my.domain/torrents . I tried adding a location and a proxy conf to Nginx but it fail to work fully. I guess it's because of web interface redirections. server { root /data/www; autoindex on; server_name localhost; location / { try_files $uri $uri/ /index.html; } location /torrents/ { proxy_pass_header X-Transmission-Session-Id; proxy_pass http://127.0.0.1:9091 ; } } This conf fail because it can't reach /transmission/rpc (404 /usr/share/transmission/web/rpc) I have tried many things and I always have something missing. transmission/rpc or transmission/upload or transmission/web or transmission/javascript/whatever...

I just compiled the transmission{-daemon,-cli} on my Debian 10 Buster, and installed it with some minor and major problems. One of those minor ones is apparent failure to set UDP receive buffer / send buffer as per log: [2019-05-23 12:45:40.950] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84) [2019-05-23 12:45:40.950] UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:89) [2019-05-23 12:45:40.950] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95) [2019-05-23 12:45:40.950] UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:100) I would like the client to show me its maximum performance, so I am curious as to how to tune these two things on my system, which it proposes? 4 on 1 MiB does not seem much to me, but since I am no networking guy, please elaborate, if I can tune it to even higher numbers. ------- Hardware ------- ISP link speed: Connection configuration: public static IPv4 with forwarded ports. ------- For the sake of completeness, let me mention other components as well, I don't know if this info is important here or not, so... - Server: Dell PowerEdge T20 - CPU: Intel Xeon E3-1225v3 3.2GHz 4C/4T - RAM: 32 GiB ECC DDR3 - System drive: SSD

I have a BTRFS external drive mounted at /mnt/media. I can create files/directories just fine with the shell (with both my personal user and transmission user). When I try to download something to the mount, Transmission throws Error: Read-only file system (/mnt/media/sometorrent).

$ su transmission
$ ls -l /mnt
drwxrwxrwx 1 root media    0 Jan 11 08:47 media

$ echo 'test' > /mnt/media/file
$ cat /mnt/media/file
test

badblocks and btrfs check didn't show any errors with the drive. I could use it with Transmission until recently.

## Target ## I am trying to run a service (transmission-daemon) in a network namespace for VPN usage. The service should automatically start using systemd. ## Implementation details ## I am using [namespaced-openvpn](https://github.com/slingamn/namespaced-openvpn) to create a network namespace. For this I have created the systemd unit file /lib/systemd/system/namespaced-openvpn.service:

[Unit]
Description=Namespaced OpenVPN
After=network.target

[Service]
User=root
Type=notify
ExecStart=/usr/local/sbin/namespaced-openvpn --config /etc/openvpn/myconfig.conf
ExecStop=/bin/kill -s STOP $MAINPID
ExecReload=/bin/kill -s HUP $MAINPID

[Install]
WantedBy=multi-user.target

This works as expected, after starting the service I can open a shell in the network namespace with the following command:

sudo ip netns exec protected sudo -u myuser -i

Running transmission-daemon from this shell also works. Trying to automate this process I created the unit file /lib/systemd/system/transmission-daemon-vpn.service:

[Unit]
Description=Transmission BitTorrent Daemon in VPN Tunnel
After=namespaced-openvpn.service

[Service]
User=root
Type=notify
ExecStart=ip netns exec protected /usr/bin/sudo -u myuser /usr/bin/transmission-daemon -f --log-error
#ExecStart=/usr/bin/transmission-daemon -f --log-error
ExecStop=/bin/kill -s STOP $MAINPID
ExecReload=/bin/kill -s HUP $MAINPID
NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

Using the commented line as ExecStart works, but is not using the VPN of course. Leaving out /usr/bin/sudo -u myuser also works but I need the daemon to run as a specific user. ## Problem ## Starting transmission-daemon-vpn fails with following error:

Job for transmission-daemon-vpn.service failed because a timeout was exceeded.
See "systemctl status transmission-daemon-vpn.service" and "journalctl -xe" for details.

---

# systemctl status transmission-daemon-vpn.service

● transmission-daemon-vpn.service - Transmission BitTorrent Daemon in VPN Tunnel
     Loaded: loaded (/lib/systemd/system/transmission-daemon-vpn.service; disabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Wed 2023-01-04 16:13:16 CET; 7min ago
    Process: 8116 ExecStart=ip netns exec protected /usr/bin/sudo -u myuser /usr/bin/transmission-daemon -f --log-error (code=exited, status=0/SUCCESS)
   Main PID: 8116 (code=exited, status=0/SUCCESS)
        CPU: 6.936s

Jan 04 16:11:42 nas systemd: Starting Transmission BitTorrent Daemon in VPN Tunnel...
Jan 04 16:11:42 nas sudo:     root : PWD=/ ; USER=myuser ; COMMAND=/usr/bin/transmission-daemon -f --log-error
Jan 04 16:11:42 nas sudo: pam_unix(sudo:session): session opened for user myuser(uid=1000) by (uid=0)
Jan 04 16:13:12 nas systemd: transmission-daemon-vpn.service: start operation timed out. Terminating.
Jan 04 16:13:16 nas ip: Closing transmission session... done.
Jan 04 16:13:16 nas sudo: pam_unix(sudo:session): session closed for user myuser
Jan 04 16:13:16 nas systemd: transmission-daemon-vpn.service: Failed with result 'timeout'.
Jan 04 16:13:16 nas systemd: Failed to start Transmission BitTorrent Daemon in VPN Tunnel.
Jan 04 16:13:16 nas systemd: transmission-daemon-vpn.service: Consumed 6.936s CPU time.

EDIT: Solution Found. In my case, I needed to go into the network settings, in the identity tab change the Firewall Zone to "trusted". My setup: Host: Windows 10 Virtualbox: Version 6.1.36 Guest: Linux Mint 19 Tara Network: Bridged mode, IP 192.168.0.x Various services (Transmission, etc) are accessible within the guest. I.E., I can navigate to their web pages locally. Transmission, for example, can be accessed within the guest via 192.168.0.x:9091. However, it and all other services are NOT accessible outside the guest, on the Lan. * Guest Firewall (ufw) is disabled for testing purposes, issue remains. * Guest VPN (private internet access) is disabled for testing purposes, issue remains. * I can ping the guest, and the guest can ping out to devices on the Lan. * Guest can browse the internet. * Guest SSH is operational. * (edited to add) - bypassed windows firewall by trying to access on android phone, same issues It's a real head-scratcher. Everything was working fine and then it just stopped working. As it happens, I have a backup of this VM, and when I spin up the backup instance, THAT works perfectly. For about three days, and then everything stops working again. So this issue is absolutely reproducible, but I have zero knowledge of how to track something like this down. It seems all the TCP/IP stuff is in order, and it seems the apps should all work fine. But something is preventing them from being accessible outside the guest/on the Lan. Any help would be highly appreciative. Please tell me what log files you might need/how to retrieve them. Thank you.

I am running transmission-daemon as a systemd service. ExecStart=/usr/bin/transmission-daemon -f --log-error -e where I have tried different values for path all with universal write permissions. The log file is successfully created but it is empty. systemctl status reports Nov 18 07:39:48 flip systemd: Starting Transmission BitTorrent Daemon... Nov 18 07:39:48 flip systemd: Started Transmission BitTorrent Daemon. Nov 18 07:39:48 flip transmission-daemon: sendto: Operation not permitted Nov 18 07:39:48 flip transmission-daemon: sendto: Operation not permitted Nov 18 07:39:48 flip transmission-daemon: sendto: Operation not permitted Nov 18 07:39:48 flip transmission-daemon: sendto: Operation not permitted requested by @binarysta [Unit] Description=Transmission BitTorrent Daemon After=network.target [Service] User=transmission Type=notify ExecStart=/usr/bin/transmission-daemon -f --log-error -e /mnt/ram/log/transmission-daemon.log ExecReload=/bin/kill -s HUP $MAINPID NoNewPrivileges=true [Install] WantedBy=multi-user.target

Transmission supports at least stopping, resuming, removing, removing with the torrent data, moving, queuing and verifying torrents. In the GUI clients (Qt and QTK) it's trivial to filter by a tracker (e.g. archive.org), select all and apply a desired action, but it seems unclear if transmission-remote supports similar accessible batch-functionality. For reference: transmission-remote --torrent all --info outputs information about all of the running torrents, including their trackers.