binhex

Community Developer
  • Content count

    2421
  • Joined

  • Last visited

Community Reputation

48 Good

2 Followers

About binhex

  • Rank
    DevOps wizard

Converted

  • Gender
    Male
  • Personal Text
    Doing stuff and all

Recent Profile Visitors

889 profile views
  1. ive never done this, but yeah it should be possible, one thing you will need to ensure is that the source teamspeak server is running the same version as the docker TS server (as close as possible) otherwise things like database etc wont import ok, im assuming the source teamspeak server is also linux right? if its windows then again you might run into issues with that. what you could try is slowly transition it over bit by bit, so stop the source TS server, stop the docker TS and then copy just the channels across, then start docker TS and see if that comes across ok, if it does then try icons etc.
  2. /usr/bin/env is a command you can execute to see what env vars have been defined, in this case a env var called "python" doesn't exist, you need to specify the version instead, so change the line:- #!/usr/bin/env python to #!/usr/bin/env python2 this is assuming its a python2 script, if its written for python3 then change the above line to python3.
  3. so im unclear as to what you're trying to achieve, not sure what you mean by "I'm trying to connect your version of sabnzbdvpn with sabnzbd", are you trying to transition over FROM sabnzbd TO sabnzbdvpn right, as in all your settings etc?.
  4. Yeah I spotted your issue (and possibly the other guys) in the log and worked around the problem, but it was getting late so I pushed the build button and went to bed. So I'm not 100% happy with the fix, so I will tweak it again today, so if you see another update then please pull it down and let me know if it's still ok. Sent from my SM-G935F using Tapatalk
  5. ok please follow this procedure:-
  6. i suspect you didnt do this:- but lets see in the logs, please follow this procedure:-
  7. well @Dagarth @doremi @lastOne i have done some testing and i cant replicate the issue, so im assuming this is either some corruption of your plugins and/or corruption of rtorrent settings. i can successfully create a container from scratch with no pre-existing configuration and it starts successfully with normal access to the rutorrent web ui and full port forwarding working (for pia) and the correct external ip assigned. so with that in mind i think we need to try and reset some stuff and see what the cause is:- 1. delete /config/rutorrent/plugins/ folder and reboot the container - if this doesn't fix it move onto 2. 2. rename /config/rtorrent/rtorrent.rc to /config/rtorrent/rtorrent.rc.old and reboot the container - if this doesn't fix it move onto 3. 3. rename host path for /config to suffix with '_old' e.g. /mnt/cache/appdata/rutorrent_old and reboot the container - this will fix it (tested). if you had to go with step 3 then you will need to copy across from the old path the /config/openvpn/ folder to the newly created /config, you are probably safe to also copy your rtorrent.rc file too, the only last things to do would then be to tweak any settings for the rutorrent web ui that have been reset.
  8. ok guys i will take a look at lunch and see if i can reproduce this.
  9. your vpn provider is using a weak cipher for their certs, its not permitted with openssl 1.1.x:- VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: please contact your vpn provider and get them to update their certs.
  10. it should be up by the end of today.
  11. Overview: Support for Docker image arch-airsonic in the binhex repo. Application: Airsonic - https://github.com/airsonic/airsonic/ Docker Hub: https://hub.docker.com/r/binhex/arch-airsonic/ GitHub: https://github.com/binhex/arch-airsonic If you appreciate my work, then please consider buying me a beer For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here
  12. ahh yes thats fine, your ports looks good to me, just make sure you have a separate /config path for each as well right. im not sure of the limits for rutorrent, but i thought it was higher than that, more like 20,000 but i might be wrong.
  13. Remove value for vpn_options Sent from my SM-G935F using Tapatalk
  14. yes, simply change the port mapping on the host side so that you dont get a port clash, oh and use a different host path for /config as well.
  15. Git isn't present in this docker images, simply select advanced view on the docker tab, then click on the force update option for this container to get you back in sync Sent from my SM-G935F using Tapatalk
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.