• Content Count

  • Joined

  • Last visited

Community Reputation

25 Good

1 Follower

About clowrym

  • Rank
  • Birthday 01/26/1975


  • Gender
  • Location
    Calgary, Alberta

Recent Profile Visitors

2436 profile views
  1. i believe you require --dns ....but i could be wrong i guess!!
  2. did you also add the "--" to --dns ? is was missing in your run least compared to mine.
  3. I believe this should be --dns ..... If that doesn't help, try moving off the :dev branch
  4. Can you post the docker run command, remove your username/passwords
  5. I haven't really paid much attention.... Generally though, I find its really dependent on the tracker im connected to. The private ones im on have always seemed very fast! I've got a 1g connection.... Just doing a test i'm running 200+ mbps Update..... watching it, its now jumped to 500~600
  6. i need to see your run command..... have you tried adding google dns
  7. I dont see an issue with the run command, what does your log say? Looking at IPvanish on git hub, I dont believe you need to download config files and place them anywhere, Just set 'OPENVPN_CONFIG'='XXXX' to which tunnel you want. You may have to set 'VPN_PROVIDER_HOME' location though.......looks like its an error that should be in the docker logs
  8. Looks like your log in details are incorrect?
  10. you could try and map your backup folder to another location on your array.... or there may be a config file in the server files to set the backup folder, i have only created the template, not the program. its been a long time since i ran a minecraft server, so I cant say i remember where it stores the files. in the origional post there should be a link to github where you could also ask the question.
  11. not sure what your question is here, but it sounds like you have the same port, or a range of ports that includes this port already specified on your router.........
  12. can you post your run command? its hard to say whats going on without knowing what is set to run. Typically if you have set all the variables / paths the same as the origional docker, you should still have all the old settings / torrents running
  13. There seems to be a few issues with the port updating script lately. if you are having issues with your Transmission_VPN losing connection resulting in a fatal error, I have a script that I have been using to look for fatal errors in the docker log, and restart if one is found. #!/bin/bash #Check for error in Transmission log and restarts docker if found #change /Search_String/ to suit the required error docker logs --tail 50 Transmission_VPN 2>&1 | awk '/fatal_error/ {print | "docker restart Transmission_VPN"}' I run this every 15 minutes with the User Scripts plugin. c