Server Torrent on Rasoberry - Client on MAC - connection issie. Only on MAC.

Ask for help and report issues with the Mac OS X version of Transmission
Post Reply
bartasp
Posts: 6
Joined: Wed Feb 24, 2016 1:19 pm

Server Torrent on Rasoberry - Client on MAC - connection issie. Only on MAC.

Post by bartasp »

Hi. I have problem to connect Client (on MAC ) with Transmission server ( started on Raspberry). Transmission client on MAC not connected to server.
When i tried to connect from Windows Client to Server it's working correctly.
Maybe someone will help my with this?
Config in attached file!
Attachments
Zrzut ekranu 2016-02-24 o 14.15.14.png
Zrzut ekranu 2016-02-24 o 14.15.14.png (120.31 KiB) Viewed 5919 times
bartasp
Posts: 6
Joined: Wed Feb 24, 2016 1:19 pm

Re: Server Torrent on Rasoberry - Client on MAC - connection issie. Only on MAC.

Post by bartasp »

Yes, port is open. ( attached picture ) . Client on Windows 10 and Android connect to server and working correcty.
The issue is only on MAC. Firewall has been disabled.

I can login to Transmission via Safari : http://192.168.1.15:9091/transmission/web/ .

Message Log (Command-3 --- debug) would help . How to do it?
Attachments
Zrzut ekranu 2016-02-24 o 14.54.32.png
Zrzut ekranu 2016-02-24 o 14.54.32.png (79.12 KiB) Viewed 5913 times
bartasp
Posts: 6
Joined: Wed Feb 24, 2016 1:19 pm

Re: Server Torrent on Rasoberry - Client on MAC - connection issie. Only on MAC.

Post by bartasp »

Transmission Server - on Raspbbery PI - 192.168.1.15 - OpenPLI
I need to connect Transmission application as CLIENT on Mac to my Transmission server 192.168.1.15.
It's working via Windows (Transmission Client for Windows) and Android (Torrado client). But its not working via MAC.

Log:

Code: Select all

2016-02-24 16:38:31 +0000 session.c:736 [Info] Transmission: Transmission 2.84 (14306) started
2016-02-24 16:38:31 +0000 cache.c:261 [Debug] Cache: Maximum cache size set to 4.00 MB (244 blocks)
2016-02-24 16:38:31 +0000 rpc-server.c:824 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2016-02-24 16:38:31 +0000 rpc-server.c:1033 [Info] RPC Server: Serving RPC and Web requests on port 127.0.0.1:9091/transmission/
2016-02-24 16:38:31 +0000 rpc-server.c:1037 [Info] RPC Server: Whitelist enabled
2016-02-24 16:38:31 +0000 rpc-server.c:1040 [Info] RPC Server: Password required
2016-02-24 16:38:31 +0000 net.c:379 [Debug] Transmission: Bound socket 13 to port 59225 on 0.0.0.0
2016-02-24 16:38:31 +0000 net.c:379 [Debug] Transmission: Bound socket 14 to port 59225 on ::
2016-02-24 16:38:31 +0000 tr-dht.c:277 [Debug] DHT: Initializing DHT
2016-02-24 16:38:31 +0000 tr-dht.c:306 [Info] DHT: Reusing old id
2016-02-24 16:38:31 +0000 tr-dht.c:154 [Info] DHT: Bootstrapping from 41 IPv4 nodes
2016-02-24 16:38:31 +0000 tr-dht.c:331 [Debug] DHT: DHT initialized
2016-02-24 16:38:32 +0000 rpc-server.c:824 [Info] RPC Server: Adding address to whitelist: 192.168.1.15
2016-02-24 16:38:32 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2016-02-24 16:38:32 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2016-02-24 16:38:32 +0000 upnp.c:223 [Info] Port Forwarding (UPnP): Found Internet Gateway Device "http://192.168.1.254:2828/upnp/control/wanipconn-3"
2016-02-24 16:38:32 +0000 upnp.c:225 [Info] Port Forwarding (UPnP): Local Address is "192.168.1.107"
2016-02-24 16:38:32 +0000 upnp.c:300 [Info] Port Forwarding (UPnP): Port forwarding through "http://192.168.1.254:2828/upnp/control/wanipconn-3", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.1.107:59225)
2016-02-24 16:38:32 +0000 upnp.c:303 [Info] Port Forwarding (UPnP): Port forwarding successful!
2016-02-24 16:38:32 +0000 port-forwarding.c:92 [Info] Port Forwarding: State changed from "Not forwarded" to "Forwarded"
Attachments
Zrzut ekranu 2016-02-24 o 17.42.22.png
Zrzut ekranu 2016-02-24 o 17.42.22.png (62.89 KiB) Viewed 5895 times
Zrzut ekranu 2016-02-24 o 17.42.11.png
Zrzut ekranu 2016-02-24 o 17.42.11.png (151.17 KiB) Viewed 5895 times
bartasp
Posts: 6
Joined: Wed Feb 24, 2016 1:19 pm

Re: Server Torrent on Rasoberry - Client on MAC - connection issie. Only on MAC.

Post by bartasp »

It' simple. Connect Transmission client on Mac to my transmission server on Raspberry (192.168.1.15:9091) via Lan/WiFi Network. (as you see on screen i can manage transmission server via Web) - but i want to manage via Application.

Client can't connect to server.
I want to manage torrent on raspbbery via my MAC (Transmission client ).
bartasp
Posts: 6
Joined: Wed Feb 24, 2016 1:19 pm

Re: Server Torrent on Rasoberry - Client on MAC - connection issie. Only on MAC.

Post by bartasp »

OK. But i don't want add new torrent or manage them via Web Interface.
I need to add new torrent for transmission server via Application. I think Remote Connection was done to connect with other server transmission?

When I click Lounch Web Interface, he should forward me to 192.168.1.15:9091 (after configuration ). But this button forwarded me to localhost:9091.
Attachments
Zrzut ekranu 2016-02-26 o 16.03.21.png
Zrzut ekranu 2016-02-26 o 16.03.21.png (61.53 KiB) Viewed 5843 times
bartasp
Posts: 6
Joined: Wed Feb 24, 2016 1:19 pm

Re: Server Torrent on Rasoberry - Client on MAC - connection issie. Only on MAC.

Post by bartasp »

:D transmission-remote-gui - this is the app which I wanted to find :)
Thanks x190 . You are the best ;)
Post Reply