Jump to content

JasonJoel

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

5 Neutral

About JasonJoel

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Too late for that. No updates in 2 months <> soon. But it will be done when it's done, I guess. By definition. My data, and uptime on the system, is too important to me to run pre-RC betas. So I'm just getting impatient. Lol
  2. Probably. But I don't think we should be making general recommendations for users to use beta software releases. And further the beta hasn't updated in over five weeks, and it has plenty of known issues... Not sure I would recommend someone jumping over there just yet.
  3. I did remember that but thank you for the reminder as that isn't very intuitive/obvious!
  4. Putty it is then. Thanks for your help, as always!
  5. I actually forgot that was adjustable. 😫 I put the container last to buy more time, but I haven't tried increasing the delay. Duh... I'll try that next.
  6. Very true, and I can certainly do that. It is just to tantalizingly easy to click the terminal button when in the interface, though. To your point - putty is a fine workaround if it can't be changed.
  7. I thought it might be that.... If I remember correctly I created it on the console of the unraid server, than I added this to my container as a post argument: "; docker network connect --ip 192.168.2.252 br3 avahi" I need the docker to talk to 2 networks (the whole point of the mDNS reflector), and couldn't figure out any other way to bind the container to 2 networks.
  8. I guess I'm getting old... I simply can not easily read some of the text on the unraid console when I get in there. The green background highlighting with blue text messes with my eyes. Is there any way to change that? Example, see the text on the directory listing:
  9. I have one docker container that will not start after a reboot. Every time, I have to go into the container, edit it, change something (anything) and hit Apply, then it starts and runs just fine. It is the only container I have that does that, and I'm struggling to understand why. It isn't the end of the world, since a simple edit/apply fixes it until next reboot, but it is just weird. The container in question is named "avahi". As you may guess, it runs the avahi mDNS reflector service. unraid-diagnostics-20191231-1720.zip
  10. Well, the plugin says to post questions here, so I did.... 🤷‍♂️ Attached. Thanks! unraid-diagnostics-20191231-1720.zip
  11. Every reboot I get the following warning in FCP. I then do Apply Fix, it says 'fix applied successfully', and I go on my merry way. Next reboot same warning message. Is there any way to stop this permanently?
  12. Understood, and that's what I did - no issues. Thanks for maintaining these great plugins!