Error 501 when connecting to Transmission Remote

Printable View

Show 40 post(s) from this thread on one page

16-06-2009, 10:28
buddy

Error 501 when connecting to Transmission Remote

I am able to connect to the web interface using http://192.168.1.1:8008/cgi-bin/transmission.cgi but trying to connect through Transmission Remote I get an error saying "The remote server returned an error: (501) Not Implemented.

My settings in Transmission Remote are:
Host: 192.168.1.1
Port: 8008

I just upgraded to transmission 1.72 and using transmission-remote-dotnet 3.9

Can anyone help? I have looked everywhere to resolve this problem and dying to use Transmission Remote ratehr than the web interface.

Buddy
16-06-2009, 11:15
gouryella

Quote:

Originally Posted by buddy

I am able to connect to the web interface using http://192.168.1.1:8008/cgi-bin/transmission.cgi but trying to connect through Transmission Remote I get an error saying "The remote server returned an error: (501) Not Implemented.

My settings in Transmission Remote are:
Host: 192.168.1.1
Port: 8008

I just upgraded to transmission 1.72 and using transmission-remote-dotnet 3.9

Can anyone help? I have looked everywhere to resolve this problem and dying to use Transmission Remote ratehr than the web interface.

Buddy

maby the settings is overwrited by new version
check...

Code:

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

and sometimes web interface ads some garbage to config
16-06-2009, 12:10
buddy

Quote:

Originally Posted by gouryella

maby the settings is overwrited by new version
check...

Code:

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

and sometimes web interface ads some garbage to config

I tried that and I actually don't have any settings.json file

Why is that and what should be in settings.json file?
16-06-2009, 12:51
gouryella

Quote:

Originally Posted by buddy

I tried that and I actually don't have any settings.json file

Why is that and what should be in settings.json file?

it's standart cofig file, from wengi's tutorial http://wl500g.info/showpost.php?p=60933&postcount=4
16-06-2009, 13:36
buddy

Quote:

Originally Posted by gouryella

it's standart cofig file, from wengi's tutorial http://wl500g.info/showpost.php?p=60933&postcount=4

I created the settings.json file and added the contents that's on wengi's page. Changed the port to port 8008. I saved and rebooted.

Still no luck and with the same error.
But when I went to open the settings.json file again the contents was gone??
16-06-2009, 19:17
avberk

Looks like you did not install the correct version of transmission.

Did you install 'transmission' or 'transmissiond'?

You install the first one with

ipkg install transmission

Then you start the 'transmission-daemon' with the -f switch.
If you break it off you will see that the settings.json file gets created.
After that you should manually make changes to the file according to your needs.
Now you can start transmission again, but this time without the -f switch.

e.g.
/opt/bin/transmission-daemon -g /tmp/harddisk/torrent -T -w /tmp/harddisk/torrent -l 20

(run transmission-daemon -h for help on the switches)

Now you should be able to connect with transmission remote-dotnet (don't change the port number if you don't have too)
17-06-2009, 01:50
buddy

Quote:

Originally Posted by avberk

Looks like you did not install the correct version of transmission.

Did you install 'transmission' or 'transmissiond'?

You install the first one with

ipkg install transmission

Then you start the 'transmission-daemon' with the -f switch.
If you break it off you will see that the settings.json file gets created.
After that you should manually make changes to the file according to your needs.
Now you can start transmission again, but this time without the -f switch.

e.g.
/opt/bin/transmission-daemon -g /tmp/harddisk/torrent -T -w /tmp/harddisk/torrent -l 20

(run transmission-daemon -h for help on the switches)

Now you should be able to connect with transmission remote-dotnet (don't change the port number if you don't have too)

Thanks for the instructions but still no luck. Still gettings the 501 error. This is how I went about with ur instructions. I changed the port to port 8008 as thats what im using to connect to my browser as even though the settings.json file has set the port to 9091

Code:

[admin@WL-500GP root]$ ipkg install transmission Package transmission (1.72-1) installed in /opt/ is up to date. Nothing to be done Successfully terminated. [admin@WL-500GP root]$ [admin@WL-500GP root]$ transmission-daemon -f [10:22:42.762] Couldn't bind port 51413 on 0.0.0.0: Address already in use [10:22:42.938] Couldn't bind port 51413 on ::: Address already in use [10:22:42.977] RPC Server: Adding address to whitelist: 127.0.0.1 [10:22:43.132] RPC Server: Serving RPC and Web requests on port 9091 [10:22:43.133] RPC Server: Whitelist enabled [10:22:43.134] Transmission 1.72 (8702) started [10:22:44.371] %s succeeded (%d): initnatpmp succeeded (0) [10:22:44.372] %s succeeded (%d): sendpublicaddressrequest succeeded (2) [10:22:53.042] Starting: Starting [10:22:53.127] Starting: Starting ^[[10:24:30.517] Saved "/usr/local/root/.config/transmission-daemon/settings.jso n" [10:24:30.629] Stopped: Stopped Closing transmission session... done. [admin@WL-500GP root]$ nano /tmp/harddisk/transmission/config/settings.json [admin@WL-500GP root]$ transmission-daemon -f [10:25:40.969] Couldn't bind port 51413 on 0.0.0.0: Address already in use [10:25:41.001] Couldn't bind port 51413 on ::: Address already in use [10:25:41.043] RPC Server: Adding address to whitelist: 127.0.0.1 [10:25:41.067] RPC Server: Serving RPC and Web requests on port 9091 [10:25:41.068] RPC Server: Whitelist enabled [10:25:41.069] Transmission 1.72 (8702) started [10:25:42.282] %s succeeded (%d): initnatpmp succeeded (0) [10:25:42.283] %s succeeded (%d): sendpublicaddressrequest succeeded (2) [10:25:51.486] Starting: Starting [10:25:51.832] Starting: Starting [10:27:51.703] Saved "/usr/local/root/.config/transmission-daemon/settings.json" [10:27:51.730] Stopped: Stopped Closing transmission session... done. [admin@WL-500GP root]$ nano /usr/local/root/.config/transmission-daemon/settings.json [admin@WL-500GP root]$ /opt/bin/transmission-daemon -g /tmp/harddisk/torrent -T -w /tmp/hard disk/torrent -l 20 [admin@WL-500GP root]$ [admin@WL-500GP root]$ transmission-daemon -f [10:38:49.980] Couldn't bind port 51413 on 0.0.0.0: Address already in use [10:38:50.003] Couldn't bind port 51413 on ::: Address already in use [10:38:50.063] RPC Server: Adding address to whitelist: 127.0.0.1 [10:38:50.087] RPC Server: Serving RPC and Web requests on port 8008 [10:38:50.088] RPC Server: Whitelist enabled [10:38:50.089] Transmission 1.72 (8702) started [10:38:51.834] %s succeeded (%d): initnatpmp succeeded (0) [10:38:51.835] %s succeeded (%d): sendpublicaddressrequest succeeded (2) [10:39:00.001] Starting: Starting [10:39:00.342] Starting: Starting [10:39:05.609] Saved "/usr/local/root/.config/transmission-daemon/settings.json" [10:39:05.633] Stopped: Stopped Closing transmission session... done. [admin@WL-500GP root]$ /opt/bin/transmission-daemon -g /tmp/harddisk/torrent -T -w /tmp/harddisk/torrent -l 20 [admin@WL-500GP root]$

i ran transmission-daemon -f at the end again just to show u that I changed the port to 8008
17-06-2009, 04:54
buddy

I found now that I rebooted that I cannot even load tranmission through the browser http://192.168.1.1:8008/cgi-bin/transmission.cgi and it says unable to connect to the remote server when trying to use Tranmission Remote?
17-06-2009, 09:08
avberk

first of all, don't reboot because your setting.json file is not on an external disk and is not saved in flash as far as i can see. (check forum on how to save to flash)

Second. You should be able to connect with this:

http://192.168.1.1:8008

Since transmission has is own build in webinterface i would leave the port on default (9091) and connect like this:

http:192.168.1.1:9091

If that works, you should also be able to connect with transmission remote dotnet
17-06-2009, 15:58
buddy

Quote:

Originally Posted by avberk

first of all, don't reboot because your setting.json file is not on an external disk and is not saved in flash as far as i can see. (check forum on how to save to flash)

Second. You should be able to connect with this:

http://192.168.1.1:8008

Since transmission has is own build in webinterface i would leave the port on default (9091) and connect like this:

http:192.168.1.1:9091

If that works, you should also be able to connect with transmission remote dotnet

I followed them steps u gave me earlier and didn't reboot time and left the port number to 9091 in the settings.json file. But when I go to connect through the webbrowser http:192.168.1.1:9091 I get this msg

Code:

403: Forbidden Unauthorized IP Address. Either disable the IP address whitelist or add your address to it. If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries. If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

and I get the same 403 error when trying through transmission remote.

I can still though connect to transmission on the web browser using http://192.168.1.1:8008 but get the 501 error when connecting through transmission remote.
17-06-2009, 16:49
gouryella

just edit .json and change line with rpc-whitelist to:
"rpc-whitelist": "*.*.*.*,"
and restart transmisiion
18-06-2009, 01:07
buddy

Quote:

Originally Posted by gouryella

just edit .json and change line with rpc-whitelist to:
"rpc-whitelist": "*.*.*.*,"
and restart transmisiion

I edited the .json file and changed the whitelist and restarted transmission by
/opt/bin/transmission-daemon -g /tmp/harddisk/torrent -T -w /tmp/harddisk/torrent -l 20

But Im still getting the 403 error. Could I have another transmission running and thats y they r conflicting?

How would I go about removing everything like all the librarys and packages and start fresh but still keep the torrents that I have not finished yet? Im thinking that might be a solution.
18-06-2009, 15:56
avberk

if you run this command you will see what's installed.

ipkg list_installed

If you see transmissiond then uninstall it with:

ipkg remove transmissiond

btw:

Do you have a folder /tmp/harddisk/torrent?

be sure you have it, otherwise create it. Be sure you have a folder on your harddisk or usb drive connected to the asus.

This is the correct syntax for the rpc whitelist in settings.json:
"rpc-whitelist": "*.*.*.*",

Notice the place of the comma
18-06-2009, 16:56
buddy

Quote:

Originally Posted by avberk

if you run this command you will see what's installed.

ipkg list_installed

If you see transmissiond then uninstall it with:

ipkg remove transmissiond

btw:

Do you have a folder /tmp/harddisk/torrent?

be sure you have it, otherwise create it. Be sure you have a folder on your harddisk or usb drive connected to the asus.

This is the correct syntax for the rpc whitelist in settings.json:
"rpc-whitelist": "*.*.*.*",

Notice the place of the comma

Ok I had transmissiond so I uninstalled it and thats wat was running at port 8080 because now I can't connect to it. I have a folder /tmp/harddisk/torrent. I had already fixed the mistake with the comma for the rpc-whitelist when I changed it.

Gave it a shot and ran 192.168.1.1:9091 and I still get the same 403 error msg even though I changed the rpc-whitelist, y is that when I have changed it to accept any ip address?

Code:

403: Forbidden Unauthorized IP Address. Either disable the IP address whitelist or add your address to it. If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries. If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.
18-06-2009, 19:55
avberk

I am sure the problem is in the settings.json file, or you did not restart transmission-daemon after a change.

Can you post your settings.json file in an attachment, so i can have a look?

Can you tell me which subfolders you see in the /tmp/harddisk/torrent folder?
also change the permissions on the torrent folder to 777 with 'chmod'

and also do this: (you could have too old versions of these packages)
ipkg update
ipkg install openssl
ipkg install libcurl

Show 40 post(s) from this thread on one page