I noticed that sometimes the settings in LuCi interface do not reflect those in settings.json In my case, at one point I had rpc-whitelist disabled in LuCi and settings.json showed it enabled (and it did not have the correct settings); hence, I suggest enabling transmission after setting it up.
Check the rpc-whitelist and either add the router IP address (the default 192.168.. is already listed - if different, the same format should be used) or disable it altogether.
Hey Donhylo,
I didnât change anything in the firewall settings.
I got it working after removing all the relevant packages and reinstalling them again and inserting the right settings immediately, certainly in the RPC whitelist â(127.0.0.1,192.168.star.star)â if remember it rightly.
As markerfit says, it seems that sometimes things are not saved correctly in the config file.
Removing and reinstalling the packages lets it all start from scratch again.
Try to do that maybe? And using the right URL in your browser 
Itâs trial and error for me too to be honest as Iâm not a specialist at all.
I think that is because thereâre more than one settings.json for Transmission.
/etc/config/transmission is the file that LuCI reads/tmp/config/transmission/settings.json is the file that LuCI reads when nothing is installed/mnt/nas/transmission
Iâve tried whitelisting everything (...) with no success.
Iâve tried stoping the daemon before modifying all the config files I could find with no success.
Iâve tried removing the related packages and installing them back with no success.
@Nick87 How then did you open the 51413 port youâre supposed to open for income traffic? Through UPnP?
A good old factory reset did the trick but man⌠I wish that things that did work just keep workingâŚ
Hmm, a bit annoying that a factory reset makes the trick work after hours of searching. Should not be case.
Maybe iâll try the reset too and see if that makes it work.
Any tcp, udp
From any host in wan
To any router IP at port 51413 on this device
I have this rule in my âFirewall - traffic rulesâ.
This should open the port for transmission no?
How can I check if this really is open. In the settings of the web interface of transmission it says âport is closedâ.
Not really sure what the problem is to be honest.
I already rebooted.
I made an input and forward traffic rule on the 51413 port
Donât know what to do more, it this what should be done? I guess so no?
Transmission
Any tcp, udp
From any host in wan
To any router IP at port 51413 on this device
Accept input
Transmission2
Any traffic
From any host in wan with source port 51413
To IP 192.168.1.1, port 51413 in lan
Accept forward
The text from the config file:
config rule
option target 'ACCEPTâ
option src 'wanâ
option proto 'tcp udpâ
option dest_port '51413â
option name âTransmissionâ
config rule
option enabled '1â
option target 'ACCEPTâ
option src 'wanâ
option dest 'lanâ
option name 'Transmission2â
option src_port '51413â
option dest_ip '192.168.1.1â
option dest_port â51413â
You might be better off enabling UPNP. Transmission has the option to randomize start port, so either uncheck that and go with a fixed port, or just enable UPNP on the Omnia and let it automatically set up the port forward. Works fine for me.
UPNP is activated. So if I check ârandomize portâ then UPNP is used and otherwhise not?
Make sure the Transmission option âUse port forwarding from my routerâ is checked.
Was checked from the beginning
Whatever change you make in the config, make sure to STOP the daemon BEFORE applying the modifications you want to apply. Then START it again.
In order to open port 51413 I add a new rule under Firewall > Port Forwards
As I mentioned previously, those are the settings I used:
The result in LuCI would be:
I havenât been able to make UPnP work with the Transmission Daemon. I know it works because I have configured the Transmission app (not the GUI or web interface) on my Mac with UPnP with the option of randomise port checked.
One last observation I could make is that the only User that would work for me is Root (that would be under Transmission > Global settings > Run daemon as user). If I put anything else, the web interface would not load (server not found in web browser). Itâs not ideal because of file permissions in my NAS but for now it works.
Yes, trying to run the native Omnia Transmission demon as anything other than root is going to have lots of problems. Youâre better off putting it in a LXC container if you want to do that. Probably not a bad idea anyway from a security standpoint.
Just a tip, after changing the configuration. Try restarting the daemon. That mostly helps. Or rebooting the router.
Does anyone know how the download queue works? I want only 1 torrent to be downloaded at the same time but they all start immediately now. I though I changed the right setting but it doensât really work. Tried restarting the daemon already.
Because when I do multiple downloads the transmission web interface becomes really slow. Like the router canât handle it but the Luci interface is still fluently loading.
Update: SOLVED
Restarting the dameon one more time did the trick! So this confirms my first comment
