twistedsanity

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

6 Neutral

About twistedsanity

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Just adding another person to the list who is looking for a solution. Until 'official' support is available I'm sure we will need to look to compile ourselves. My search will go on
  2. I tried latest and its still linked to an old version. I then tried version-6.2.25 and so far all is looking good.
  3. If you click on the name of the container it will take you to the 'configuration screen' in there will be a field called "Repository" it will likely have the box filled with "linuxserver/unifi-controller" or "linuxserver/unifi-controller:latest" change this to "linuxserver/unifi-controller:version-6.2.23" (without the quotes) and click apply. This basically tells the system to go and get a specific version of the software rather than just looking for the newest. But again please remember this is a temp fix and will need to be reverted at some point. Also please note by changing thi
  4. Sorry, I may have missed something completely earlier in discussions but mine also had this issue as it looks like dockerhub linuxserver.io shows version 6.1.71 attached to the tag 'latest' which it isn't (its a release from a month or so ago) and mine is trying to downgrade to it as its thinking it is a new release. *** I fixed this (temporarily until linuxserver.io fix the tags) by changing out the repository field to "linuxserver/unifi-controller:version-6.2.23" this then reinstalled the 6.2.23 version and the container came up. *** Note: once fixed by linuxserver y
  5. @gaikokujinkyofusho I think I may have solved the issue. I found that 'Automatic Torrent Management' was not on/ticked for every new torrent. If I start a torrent then manually tick this it looks to get moved correctly. Unfortunately it looks like the options to configure this are not available in the WebGUI only the full desktop client, but... I opened the qBittorrent.conf in notepad and adjusted the following section to look like this (I only had to modify the last line on mine, false to true) [BitTorrent] Session\DisableAutoTMMTriggers\Categor
  6. Same here, tried a number of different things, but still can't get it to work. May see if I can get some debugging set and trace a small download end to end.
  7. I'm glad I came and looked, I am having exactly the same issue. I thought it was my config and have completely rebuilt the categories and folders. Hmmm I wonder what has changed.
  8. Just wanted to say thanks, this has really tidied up my list of containers
  9. 1) Using Unraid meant I was able to hugely condense multiple physical servers and service into one box (ha/dr to a second) whilst keeping power usage to a minimum and heaat output low. Something that I would welcome in 2020 would be some small improvements to the docker implementation, for example, visual updates for container grouping which could be collapseable. Its really great already, but with a little more tweaking would tip it over the edge into awesome.
  10. So very short term user, but already I've managed to reduce my home infrastructure to a single server (offsite data backup still and some other dedicated devices) running multiple containers and vms. This has reduced my electrical demand, heat generated and space required massively. I am over the moon with my setup that even though I don't need it I bought the pro license as a sort of thank you! I am still trying to think up new ways or things to do with my server to increase the value add.
  11. Technically it doesn't get a new external IP as its using the other container for its connectivity, but yes confirmed the route and that there is no leak to other interfaces. TBH its a great solution to what I was looking to do. Also running packet trace at the firewall to make sure all is as it should be.
  12. I have a rather custom setup where I use --network=container:[containername] via the 'extra parameters' option field (network type in the GUI is set to none). This means if I need to access the WebUI of this container I need to route via the other containers IP and port. Therefore I would like to be able to unhide/override the default behaviour for the WebUI menu item (which is hide on 'network type' = none) so I can manually point it to the correct address. Thank you for the consideration.
  13. Shame, never mind, thought I'd at least ask. I was hoping I could temporarily modify the xml or a flag to show it even though none was selected. Thanks for the help!
  14. I really do want it to appear as I am using --network=container:[containername] and want the webui option (manually configured) to use the ip and port assigned to the other container.
  15. Hello, I am using a custom network configuration, but I still want the WebUI option to appear with my customer ip/port configured. For some reason when network is set to none I lose the WebUI menu item. Any way to get this back?