Can't get to Transmission Web UI

[defonza]

I just installed and setup FreeNAS, the first plugin i added was Transmission.
It installed fine, and set up a jail with IP 192.168.1.6,

When i go to 192.168.1.6:9091, i'm not able to connect. I can ping the IP, and it responds, but unable to connect to web interface.


any suggestions?

 

[codenamezero]

You need to check the NAT box in the Transmission plugin setting.
But for some reason mine stopped working after I played with it for a while, now even after I uninstalled the plugin, I can't reinstall it again.

 

[Joshua Parker Ruehlig]

the NAT box is irrelevant. did you enable the webui + start the plugin?

 

[codenamezero]

Man, this 9.2.1 is buggy... Anyhow, I had to delete the whole jail dataset, then it was acting funny and won't let me reinstall the plugin at all, because there isn't a jail dataset... then after a while I log back in, the dataset is there again... and then I could reinstall Transmission from scratch.

 

[Joshua Parker Ruehlig]

Man, this 9.2.1 is buggy... Anyhow, I had to delete the whole jail dataset, then it was acting funny and won't let me reinstall the plugin at all, because there isn't a jail dataset... then after a while I log back in, the dataset is there again... and then I could reinstall Transmission from scratch.

It doesn't seem buggy to me, but I started with a fresh jail + plugins for testing. It must suck to be running a production environment with these plugins and have to be constantly re-installing stuff anytime the OS updates. Hoping for stability soon.

 

[defonza]

It's all enabled, just can't get to the site on the IP it designates...

Should the JAILS be on the same subnet as my FreeNAS, or should I create a subnet just for this stuff?

 

[Joshua Parker Ruehlig]

It's all enabled, just can't get to the site on the IP it designates...

Should the JAILS be on the same subnet as my FreeNAS, or should I create a subnet just for this stuff?

I have them all on the same subnet, i don't know how else the jail's IP would be route-able.
Can you ping the jail's IP from your computer?
In the jail, can you show the output of 'sockstat | grep transmission'

 

[defonza]

Yeah, I can ping it... just can't browse to it...

 

[defonza]

I have them all on the same subnet, i don't know how else the jail's IP would be route-able.
Can you ping the jail's IP from your computer?
In the jail, can you show the output of 'sockstat | grep transmission'

nothing for that command, here is the whole sockstat...

Code:

root@transmission_1:/ # sockstat | grep transmission                           
root@transmission_1:/ # sockstat                                               
USER    COMMAND    PID  FD PROTO  LOCAL ADDRESS        FOREIGN ADDRESS     
root    python2.7  4924  3  tcp4  192.168.1.6:12346    *:*                 
root    cron      4729  4  dgram  -> /var/run/logpriv                       
root    syslogd    4675  4  dgram  /var/run/log                               
root    syslogd    4675  5  dgram  /var/run/logpriv                           
root    syslogd    4675  6  udp6  *:514                *:*                 
root    syslogd    4675  7  udp4  *:514                *:*                 
root@transmission_1:/ #                                                       
                                                            

 

[defonza]

i just ran from the jail, the command transmission-daemon

When i try to go to the website, it says:

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.

i never set any of these settings, so i'm not sure what it is referring to?

 

[Joshua Parker Ruehlig]

i just ran from the jail, the command transmission-daemon

When i try to go to the website, it says:

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.

i never set any of these settings, so i'm not sure what it is referring to?

don't run transmission directly. use the init script, you may have just created files owned by root that transmission won't be able to edit now...

some plugin settings are in the freenas transmission menu item, but whitelist should be disabled. you probably just created the whitelist issue by running transmission without a config.

I recommend the following

Code:

killall transmission
chown -R transmission:transmission /usr/pbi/transmission-amd64/etc/transmission 

open+save transmission settings in freenas webinterface
start transmission from freenas webinterface

 

[defonza]

don't run transmission directly. use the init script, you may have just created files owned by root that transmission won't be able to edit now...

some plugin settings are in the freenas transmission menu item, but whitelist should be disabled. you probably just created the whitelist issue by running transmission without a config.

I recommend the following

Code:

killall transmission
chown -R transmission:transmission /usr/pbi/transmission-amd64/etc/transmission 

open+save transmission settings in freenas webinterface
start transmission from freenas webinterface

Well, we are there, 99% there... now i just can't reach my tracker... if anyone has experience with what.cd, i'd love to get some assistance with making sure i can connect to their tracker.

 

[defonza]

it's resolved, the tracker is currently down, so that makes sense why i can't connect. Thanks for all the help!
[SOLVED]