brikn

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

brikn's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I can't access deluge daemon from a thin client outside LAN. It works fine on LAN but outside of it I can't access using my external IP address. Any thoughts? I tried loading iptable_mangle module on docker host, made sure the thin client version is compatible (same version on both systems on and off LAN), but I can still only access on LAN. I have VPN enabled as well.
  2. I've tried recreating, changing permissions to root for the container and data directory but still nothing. I always get some form of error, whether it is tracker timeout or invalid IP, or just not connecting to any peers. I've read every source I could find about this issue but the only thing I can find is permissions error but nothing I do seems to fix the problem. I can get delugevpn and qbittorrentvpn working with ease but rutorrentvpn is still not working.
  3. yeah, i did "chown -R brian:brian /mnt/data" before and that user is what also is assigned 1000 UID and GID.
  4. yeah it exists. It's the same one I use for delugevpn. Oh this isn't on Unraid, is that why it's not working?
  5. My new log with VPN enabled. No error but stuck on queued when testing with official Ubuntu ISO. https://pastebin.com/5JcmCTTk
  6. I've been using your delugevpn for a while now but I want to try to make the switch to rtorrent but every time I've tried using it I get this error or something similar. Tracker: [Failure reason \"IP: My.External.IP.Here\"]. I've followed the Help FAQ from the github page but I don't see anything useful in the supervisord log. I want to use a VPN like I do with deluge but have it disabled while troubleshooting but same issues except reading my VPN IP in the error when VPN is on. https://pastebin.com/cXMdJT2F