Transmission - no longer able to access web interface

[uzelac]

I'm no longer able to load the transmission web interface. I think this problem began when my server was restarted about two weeks ago, but I'm not 100% sure.

I set up openvpn and then performed minimal config of ipfw in my transmission jail. I never had a chance to finish my ipfw config so I stopped the service and went about my day. (It was still enabled in my rc.conf at this point.)

I was on vacation a couple weeks ago and my server stopped responding, so I had a close friend come and reboot it. When I came back from vacation, I noticed that the transmission interface was no longer accessible.

The first thing I did was make sure that both ipfw and openvpn were stopped and disabled in my rc.conf, in case something had gone haywire. I still wasn't able to connect to the interface.

I know that transmission is functioning. transmission-remote -l shows that I have torrents actively downloading. It's also communicating with CouchPotato and Sonarr.

Netstat shows that the jail is listening on port 9091:

Code:

# netstat -an | grep 9091
tcp4       0      0 192.168.1.5.9091       192.168.1.4.41072      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.4.10566      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.4.45148      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.4.55525      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.4.36705      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.4.52296      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.4.31135      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.4.10188      TIME_WAIT
tcp4       0      0 192.168.1.5.9091       192.168.1.6.57911      ESTABLISHED
tcp4       0      0 *.9091                 *.*                    LISTEN

ps ax shows that the daemon is running:

Code:

# ps ax
  PID TT  STAT    TIME COMMAND
 9481 ??  SsJ  0:00.02 /usr/sbin/syslogd -s
 9520 ??  SsJ  0:17.31 /usr/pbi/transmission-amd64/bin/transmission-daemon -g /var/db/transmission -x /var/run/transmission/daemon.pid
 9529 ??  SsJ  0:24.36 /usr/local/sbin/openvpn --cd /usr/local/etc/openvpn --daemon openvpn --config /usr/local/etc/openvpn/openvpn.conf --writepid /var/run/openvpn.pid
 9555 ??  SsJ  0:00.00 /usr/sbin/cron -s
10487 ??  IJ   0:00.85 /usr/pbi/transmission-amd64/bin/python2.7 /usr/pbi/transmission-amd64/control.py start 192.168.1.5 12348
34256  0  SJ   0:00.01 bash
34677  0  R+J  0:00.00 ps ax

The only transmission-related entries in /var/log/messages are what I believe to be a utp-related error from when I rebooted my server about an hour ago.

Code:

Jan  5 18:38:36 transmission_1 transmission-daemon[9520]: UDP Failed to set receive buffer: No buffer space available (tr-udp.c:59)
Jan  5 18:38:36 transmission_1 transmission-daemon[9520]: UDP Failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c:78)

In my transmission config, RPC is enabled and bound to 0.o.o.o, and the whitelist is disabled.

As much as I hate to admit it... I'm at a debugging loss.

I should clarify that this is a local server on the same LAN and also add that I'm an idiot who doesn't have a snapshot to restore from.

Any guidance is much appreciated!

 

[Joshua Parker Ruehlig]

if you want you can backup and restore /var/db/transmission to a new instance of the transmission plugin.

 

[uzelac]

That is a good point. The stubborn side of me wants to find out what went wrong so I can prevent it from happening again, but I guess as long as the end result is that it functions, I can't complain.

 

[uzelac]

I set up a new instance of the transmission plugin and it was also giving me problems. I reset my router to its default settings and it fixed my issue. I'm guessing something went haywire with UPnP. Problem solved!