Transmission - segmentation fault

[iGz]

Hi folks,

After I`ve upgraded from 1.34 and pointed browser to my router with transimission installed, I get only "401: Unauthorized - Unauthorized IP Address" .

I changed nothing in configuration, and only thing that I found about this, is some problem with "auth.backend.htdigest.userfile" file instead "auth.backend.plain.userfile" . I did not find these files on my hdd

I`m newbie in linux world, so if you have any hint how to resolve this, or is there somebody who has same problem...

BTW : Have somebody older version of transmission (1.3x) ? Because this one worked, and after update I cannot find old version.

Thank you...

[Wxm]

Hi folks,

After I`ve upgraded from 1.34 and pointed browser to my router with transimission installed, I get only "401: Unauthorized - Unauthorized IP Address" .

I changed nothing in configuration, and only thing that I found about this, is some problem with "auth.backend.htdigest.userfile" file instead "auth.backend.plain.userfile" . I did not find these files on my hdd

I`m newbie in linux world, so if you have any hint how to resolve this, or is there somebody who has same problem...

BTW : Have somebody older version of transmission (1.3x) ? Because this one worked, and after update I cannot find old version.

Thank you...

Try this (Maybe) In my asus works
http://forum.transmissionbt.com/view...php?f=1&t=6659

[iGz]

Try this (Maybe) In my asus works
http://forum.transmissionbt.com/view...php?f=1&t=6659

Thanks, but your url is malformed, so i used search engine on that forum, but nothing there worked and found some others people that have same problem

Have anyone older Transmission release than 1.4x ?

[Wxm]

Thanks, but your url is malformed, so i used search engine on that forum, but nothing there worked and found some others people that have same problem

Have anyone older Transmission release than 1.4x ?

This solve your problem
http://www.wl500g.info/showthread.php?t=10307

[iGz]

Funny

Total reinstall is to much time consuming for me, so i`m trying to avoid it

[vleutmans]

Hi all,

after upgrading transmission to 1.41b4-1 I had to change the URL to be able to access the GUI again.
I remotely connect to router via SSH.

Before I connected to GUI by http://192.168.1.1:9091
(192.168.1.1 is the local IP of the router itself)

now I connect to http://localhost:9091 and the GUI is there.

As you see I'm not a guru, but it's easy to just try it :-)

Maybe it helps for you.

Regards

Michel

[iGz]

Thank you, this works with default configuration, but still doesn`t work with additional settings like customed port, user authentication, ip restrictions....

But thanks for hint
Seem to new Transmission doesn`t recognise older configuration.

[kaizen]

Seem to new Transmission doesn`t recognise older configuration.

Looks like it creates new config folder in /opt/torrent/.config
How to move it back to harddisk?

It looks likne -g switch stopped working this is not working anymore with new version

[BalMagnuM]

Hi Everyone,

first of all, thanks to oleg, wengi and oleo for the great job!

I just wanted to share, how I got rid of the issue - still partially.
I tryed to follow through wengi's instructions, part 10. transmission, but still got the error, until I figured, you need to explicitly enable the client's IP address from which you want to connect to your box.

From settings.json:
"rpc-whitelist": "your.clients.IP.address",

I've tried to add in a new line, other IP's or hostnames, but the result was the same 401 error message.

Now, this is wonderful, if you only connect to your box from 1 client, but presume some of us would like to see the box from ANYWHERE...

What makes me is why's there no info on how to put together a config file?

Cheers,
B

[BalMagnuM]

Hi,

finally back to normal after upgrading to 1.41b4-1 from 1.41b3-something.

Error:
- 401 error message in browser when connecting to the server

Root cause:
- config file may have been ignored or insufficient data in the config file. client's IP address is not added in the rpc-whitelist tag

Solution:
As a basis, I'm using wengi's well written instructions with minor changes to personalise settings of transmission.
Follow the post on transmission through, as we are just going to alter it to use the config file.
You need to set up server starting to take into account only the config file.

vi /opt/etc/init.d/S90transmission-daemon

Change the following line from

/opt/bin/transmission-daemon -g /tmp/harddisk/transmission/config -b -w /tmp/harddisk/transmission/download

to

/opt/bin/transmission-daemon -g /tmp/harddisk/transmission/config

Once that is done, you need only to alter the settings file. If you need to test your settings, you can use the server start|stop options or preferably the command line start and the server stop.

/opt/etc/init.d/S90transmission-daemon start
/opt/etc/init.d/S90transmission-daemon stop

or 

/opt/bin/transmission-daemon -g /tmp/harddisk/transmission/config
/opt/etc/init.d/S90transmission-daemon stop

To create your settings file, please read the official site about editing the config file.

Editing the options file, do

vi /tmp/harddisk/transmission/config/settings.json

Example:
don't use a blocklist, setup upload and download limiters, protect the transmission site with a us3r : pazWd5 access, where the server can be accessed from anywhere ("rpc-whitelist": "*.*.*.*")

{
    "blocklist-enabled": 0,
    "download-dir": "\/tmp\/harddisk\/transmission\/download\/",
    "download-limit": 200,
    "download-limit-enabled": 1,
    "encryption": 1,
    "max-peers-global": 200,
    "peer-port": 51413,
    "pex-enabled": 1,
    "port-forwarding-enabled": 0,
    "rpc-access-control-list": "+127.0.0.1",
    "rpc-authentication-required": 1,
    "rpc-password": "us3r",
    "rpc-port": 9091,
    "rpc-username": "pazWd5",
    "rpc-whitelist": "*.*.*.*",
    "upload-limit": 50,
    "upload-limit-enabled": 1
}

Cheers,
B

[wengi]

Hi BalMagnuM,

i wondered why my transmission does not accept my settings.json.
Maybe this is because of the other startup options.

Let me test your solution and update the HowTo.

Thank you
wengi

[Kenny]

    "rpc-whitelist": "*.*.*.*",

That did the trick for me, thanks

[Wxm]

Hi
I`need help.
I have a problem with transmission.
My deamon work good but only about 1h. and crash.
I can`t use putty and log to my asus.
Please help me.

[Kenny]

Hi, i've this script in /opt/etc/init.d/S57trans

#!/bin/sh


case $1 in
start)
/opt/bin/nice transmission-daemon -g /tmp/mnt/disc0_5/torrent/.config/transmission-daemon
                ;;
        stop)
                if [ -n "`pidof transmission-daemon`" ] ; then
                        echo "stopping transmission-daemon"
                        killall transmission-daemon
                fi
                ;;
        restart)
                $0 stop
                sleep 5
                $0 start
                ;;
        *)
                echo "usage: $0 (start|stop)"
                exit 1
esac

It does work if i start it manually, but it does not start automatically at boot. Permissions are set correctly (r,w,x). Any suggestions?

[alxndrv]

Hi! Reinstalled all my software from scratch after formatting hdd. Problems with trasmission: it doesn't create the file "settings.json" and thus doesn't save any settings via web-interface. It only creates 4 dirs: config dir with empty dirs blocklits, resume, torrents. Also it doesn't accept hand-made settings.json. Transmission v 1.42-1