Kyrin

Members
  • Content Count

    46
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Kyrin

  • Rank
    Newbie
  • Birthday 06/08/1981

Converted

  • Gender
    Male
  • Location
    Calgary, Alberta, Canada

Recent Profile Visitors

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

  1. While it doesn't seem like it was just yesterday, I do remember when I first built my first pair of Unraid servers about 10 years ago... So much has changed, back then I couldn't even have imagined being where we are now, but looking back, I'm so thrilled with the progress and where things are headed. Here's to another 14 years!
  2. Wow, thanks, I missed that error. Guess it could be possible that it's on its way out... it's one of my two original USBs from when I first started using UnRAID almost nine years ago...
  3. So this is a weird one I've not encountered before, and I can't seem to draw a correlation between dockers that I can and can't edit... For background, I had an unclean shutdown last night, things started up just fine afterwards, including all my usual dockers were running and responding normally... Now, I don't normally make changes to my dockers as the system is pretty stable and as such I don't tend to change things, simply update the containers when there's an update. So, it's possible the issue may have been around a bit longer than just since last night, I can't be sure if the uncle
  4. Which network do you need to assign the static on? For your primary network you can do that in the docker config page if you want it on its own IP (separate from the host) when you choose to bind it to 'bond0' or whichever your network is called, and on the secondary, 'iotnet' network, it's specified in the 'docker network connect' command... Shouldn't need to rely on DHCP for either if you don't want.
  5. If you've already clicked on the 'Update Ready' bit, ensure that the toggle on the right is 'On' and then hit 'Apply' at the bottom of the page and it should "reinstall" all the packages and that would ensure the update gets applied.
  6. After having just updated to 6.4.1 I hadn't updated my NerdPack, which was what led to missing the fact that there was this update, which has since fixed the issue... The 10 minutes of my life I could have had back from just updating everything first and then ssh in, rather than first ssh in, go crazy that it doesn't work, and fix that first... Edit: Also, it works fine with PuTTY, thanks dmacias, no need for more work!
  7. You'd have to start the docker, and then manually connect it to the second network, and then give it say 5 minutes and check the XML response from /servers (https://192.168.1.100:32400/servers ) and see if it lists it there (dunno if it will or not), or just watch the Plex log files for it refreshing its network info... It may be of value to not have it see the gateway on that network, or at least not be able to get to the Internet via that network, so it won't try and register with the Plex mothership via that network... Damn... 12:44a here, I was supposed to be catching up my time tracking t
  8. At startup Plex will bind to all available IPs, the limitation is more with the single docker having the two NICs assigned and less the Plex Server application itself... Depending on the docker, you could potentially do this... It's well beyond the current scope of Docker on unRAID, but it looks like it can be done now... Here's some reading if you fancy yourself a Wizard: https://hicu.be/docker-networking-macvlan-vlan-configuration The key bits are about a quarter, and half way down... I can transpose them for what commands *MAY* work for your scenario... First you'll need to
  9. So, I totally have the same thing, but turns out it's when using screen, not when just SSH into the server... Screen version 4.04.00 (GNU) 19-Jun-16, installed via NerdPack plugin... after some digging I figured out it was the termcap, for some reason screen is starting and using the vt100 term, even with no changes made to PuTTY or anything else (other than upgrade to 6.4, still present in 6.4.1 btw), it's doing this now, despite TERM=xterm being present as a system variable prior to starting screen... The fix is simple, just add '-T xterm' to your screen start command (capital T is important
  10. That's not a bad idea, might chat to the fellas about that, only problem is mitigating the risk for those running from command line on other operating systems, I can see issues with the ro being left off.... Any chance of getting this back, or is there another place I can pull the image from? I've been using it quite regularly prior to having to reload my main docker image, and would like to get it back on my system...
  11. Heya, sorry to revive an old topic here, but I'm in a situation where I need to read my XFS disk and I've got Linux Reader installed, but the log is stating 'File system is not supported' when I try to mount it...
  12. Now I don't know the process, but I'm just curious how to request the addition of a container, or if that's even a thing... but as upStatsBoard is somewhat dead, and I'm sure people are looking for an alternative, I was wondering if we could get a container for Plex-Board (https://github.com/scytherswings/Plex-Board) somehow... Though it's still in somewhat early active development, it looks like a good start and I think the exposure would help the project keep moving along EDIT: Okay, so I went and made one (my first docker ever btw gostlund/plex-board), and in actually using it, I
  13. Tried that, no dice. Did you set the username to admin and use the password? At this point, we need to see the log from deluge. I've tried putting admin and my password. I've tried putting just my password. Nothing worked which was why I just wound up configuring Blackhole instead. Do I lose any functionality with Blackhole over Deluge? Like am I not able to DL torrents from sites that only have magnet links? Hey, so I was frustrated as hell with this as well and think I found the key to what might have been blocking you... In the Deluge web-ui, go to Prefe
  14. You have to edit the settings.json file while Transmission isn't running. The container will copy a settings.json file to /config only if it's absent. Weird... I swear I tried that... Thanks, totally worked that time I tried it... /sheepishgrin
  15. @gfjardim: I am hoping that there may be a way for the Transmission docker to stop overwriting parts of the settings.json file... or for there to be an environment variable to set the bind address... I need to have transmission operate from an alternative IP address, and though I edited the line in the json file, it resets and I'm losing my mind here... Thanks?