Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by binhex

  1. And it got updated, told ya it wouldn't be long [emoji16] check for updated image Sent from my CLT-L09 using Tapatalk
  2. no it doesnt, its flagged out of date, as soon as that updates the build will commence, just hold tight guys, im sure it will be 'soon'.
  3. sorry my bad, i was looking at tags for delugevpn, for this image you need tag '2.0.3-1-02'
  4. check q3-q5 from the following link to see if you have the db corruption issue:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md p.s. the answer is 42
  5. Hi all, i monitor hd prices on amazon, noticed a nice drop in the price of the WD My Book 8TB from around £153 down to £112 today, thought it worth a quick post :-). https://www.amazon.co.uk/dp/B01LWVT81X/ref=cm_sw_em_r_mt_dp_U_Mu71DbSJ80S2N
  6. actually it looks like there is way of doing this by using 'phantom' this piece of software in essence makes a minecraft server appear like its running on the remote users lan, when in reality its actually running over the internet, pretty cool hu!. so for this to work each remote user running xbox one minecraft would have to install, configure and run phantom, configuration should be as simple as specifying the public ip for the user running the minecraft server (port forwarding would also have to be in place for this to work). link to phantom:- https://github.com/jhead/phantom
  7. So i use the core/thread pinning feature quite a bit for both a single VM and Docker containers and whilst this works great i do have to remember to configure the cores/threads to be pinned when adding a new Docker container/VM, this is especially a pain for me as i develop docker images and thus there is a lot of creation/deletion of docker containers going on. So what i would love to see is an ability to set the default cores/threads to be pinned when creating any subsequent VM's/Docker Containers, maybe defined at the top of the screen settings/cpu pinning for each tab?.
  8. due to arch being a rolling release (arch used for base docker image), this is actually more tricky than you would think, and as Python 3.8 is now the latest stable version its more a case that plugin developers need to update their plugins to work with 3.8. having said that, if you want to stick with a version running python 3.7 whilst the devs play catchup then you can simply use a tagged version, 2.0.3-1-08 should do it, if you are unsure how to reference a tagged version then please see q5 from the link below:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
  9. you have changed your webui_port to 2020, taken from the log:- WEBUI_PORT=2020 if you want to use port 2020 to access the webui then you need to alter the host AND container port from 8080 to 2020, alternatively change WEBUI_PORT from 2020 back to the default of 8080.
  10. see Q5 in the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
  11. sorry for the delay, the fix was a bit more gnarly than i thought, please pull down the new image and you should be good.
  12. i can see from your screen and your log you havent configured lan_network correctly, this is from your log:- 2019-11-19 02:20:21.317692 [info] LAN_NETWORK defined as '' and from your screenshot i can see your unraid ip is if you dont know how to configure this correctly then see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  13. yes, as long as your vpn provider allows multiple concurrent connections, most do, but some dont, who are you with?. also can you post your log file, see procedure below:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  14. if you setup a port forward on your router for the minecraft server then external minecraft clients will be also able to connect to it, the exception to this is xbox one, which will only connect to the minecraft server on the same lan, there is to my knowledge no way around this, short of paying for a 'realm', as you cannnot add external ip addresses to the minecraft server list on the xbox one version of minecraft.
  15. Reverse proxy, I don't know, forward proxy yes, as I'm doing just that. Sent from my CLT-L09 using Tapatalk
  16. See my Plex pass support thread for possible reasons for this, tvdb cattle trucked Sent from my CLT-L09 using Tapatalk
  17. Not sure who authors the non binhex one, but no doubt it will be base image used and release mechanism, both of which are fairly unique to my images. Sent from my CLT-L09 using Tapatalk
  18. well deluge has changed a lot over the past few months especially with the switch to deluge v2.x and bugs can (and have) crept into deluge, not much i can do about it im afraid (i dont develop or maintain deluge).
  19. looks like a bug in deluge or a badly set configuration option, same applies to you:- https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=789449
  20. do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  21. see Q3-Q5 in the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
  22. yes, create a /config/permissions.json file, edit it and add your xuid and grant yourself whatever permissions you need, e.g.:- [ { "permission": "operator","xuid": "1234567812345567" } ] players xuid value should be shown in the /config/supervisord.log file when you connect to the world.
  23. nothing to worry about, that is most probably a lock file from the previous run of libreoffice, if the app leaves the lock file and doesnt delete it on close of the app then it will warn you that the lock file already exists.....unless you have any risk of somebody else also currently using this container? (unlikely).
  24. form this i would assume you have set a value incorrectly in the core.conf file which is causing deluge to crash on startup, 3 options to fix this:- 1. open /config/core.conf and try and find the offending value and correct it. 2. restore the application configuration from backup 3. rename /config/core.conf to /config/core.conf.old and restart to re-create the config file (core.conf), then reconfigure deluge.
  25. if you want to use a custom bridge then the network for that custom bridge has to be different to your lan, in your case for example, if you use the same network range as your lan then you will not be able to access the container.