Jump to content

Squid

Community Developer
  • Posts

    28,769
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. - Added ability to wait for a port to become active before carrying on. The timeout / delay is how long to wait for the port to come alive. After that is exceeded, then the system will continue on with starting other apps. - If port is not specified, then operation is as before: Delay followed by starting
  2. I just tried it and it works perfectly. Close all your browser windows and try again. (or tell me the exact steps your doing to see this
  3. I noticed that the auto-updater is already disabled in Radarr and Sonarr from linuxserver.io. I'll just update the container as they come along then. Thanks! Set up CA Auto Update, and it'll install the updates from lsio as they are released
  4. Added in checks for Machine Check Events (MCE) Added in ability to re-add previously found ignored items
  5. Add the /DownloadComplete mapped to /mnt/user/DownloadComplete/ to Sonarr. Theres a couple of entries in the Docker FAQ (linking containers)
  6. You have to refresh the page. They are set to not autostart
  7. Guess that I can't delete that feature of CA now... Hopefully other authors will see the options it brings up and take advantage to make things easier for new users. Is there documentation on how to implement this in a template squid? Sent from my SM-G900F using Tapatalk Programming forum docker xml thread. Sent from my LG-D852 using Tapatalk Ta, I will take a look Sent from my SM-G900F using Tapatalk Do it on a test container so you see how CA reacts Sent from my LG-D852 using Tapatalk
  8. Guess that I can't delete that feature of CA now... Hopefully other authors will see the options it brings up and take advantage to make things easier for new users. Is there documentation on how to implement this in a template squid? Sent from my SM-G900F using Tapatalk Programming forum docker xml thread. Sent from my LG-D852 using Tapatalk
  9. Guess that I can't delete that feature of CA now... Hopefully other authors will see the options it brings up and take advantage to make things easier for new users.
  10. I would guess that your UPS triggered a clean shutdown of the server. I doubt if the backup completed correctly as that process only runs during a backup, and was terminated as part of unRaid's shutdown procedure.
  11. Both of them would require modifications to system files to accomplish, and that brings with it its own can of worms which I don't like opening unless its absolutely necessary. But I agree with you, and the one for docker is easy since CA includes the support link in the templates that it passes over to be installed (even though dockerMan doesn't display it on the template screen) The plugin manager is a different story as it handles .plg files whereas CA utilizes an .xml which in turn points to the .plg Either way, post up a feature req and I'm sure you'll get lots of +1s on it.
  12. Not until the next reboot (or stop & start of the array) at which point you can request a trial extension or buy the software
  13. Works fine on my systems (6.3.1) I don't have NerdPack installed, and can still hit Checksum's GUI without any complaints about inotify not being installed
  14. Great Vid Gotta admit that you did such a good job with the arrows that I didn't notice the lack of dancing girls. Really glad that Rob added it to the Docker FAQ. Should be really helpful to those new users.
  15. Check again. There's an update dated today. You probably got caught with some GitHub caching
  16. Hopefully a stupid question, but did you update FCP? Show a screenshot of the error as if its still present it should have changed slightly. Its not showing on my systems after the update
  17. And it's fixed. Caused by a specific error in an application template that an author made... Hard to anticipate every template error...
  18. Ding Ding, we have a winner, that appears to exactly have been the case for that issue, now a new issue: Warning: basename() expects parameter 1 to be string, array given in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 837 when accessing FCP via Settings just above the "Errors Found" section. Cheers! Same here, right after 6.3.1 upgrade. Restarted (Chrome) browser and still having this warning. That's going to be related to the template errors that neccessitated an update to CA. I'll fix tonight
  19. Odds on you've got an open browser session from before the boot still running. Sent from my SM-T560NU using Tapatalk
  20. Its in CA. There are a couple of issues with the template (I issued a PR on GitHub) where errors will appear on CA (Also pumped out an update to CA to handle these errors should they ever pop up again in another community template)
  21. Set up CA Auto Update to handle it all for you on a schedule. Hi...I am sorry, not sure what that is. Is that another Docker? Community applications plugin Oh, yea, I have that. Thanks Guys....Really. The issue is I seem to have the cur (rent version of Community Apps, 2017.01.29, however I do not have that option in the settings area. (As per where the manual says it should be.) Running UnRAID 6.1.9 so not sure if that may be the issue. You may have uninstalled it. Go to apps, CA Modules (top right) and you can install it from there.
  22. Set up CA Auto Update to handle it all for you on a schedule.
  23. The nzb downloaders (sab / nzbget) have options to remove illegal characters from the filenames
×
×
  • Create New...