Jump to content

guruleenyc

Members
  • Content Count

    164
  • Joined

  • Last visited

Community Reputation

1 Neutral

About guruleenyc

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    US

Recent Profile Visitors

775 profile views
  1. SOLUTION: Don't use Chrome! Apparently Firefox is able to load the WebUI of CrushFTP and Chrome is not. I'll investigate why Chrome is unable to display/load page versus Firefox and report back.
  2. All, Any tips/advice would be super appreciated.
  3. I tried removing image and reinstall it. Also using the default ports as well. No luck 😞
  4. My docker setup and logs attached:
  5. Thanks for pointing that out; I first checked this docker menu and in the community apps section for this app and there was no link to the unraid thread and support link points to http://www.crushftp.com/support.html , which noted a discontinued support forum: Also I searched the unraid site and found other CrushFTP app posts about issues, so I posted in the same area as those.
  6. I just installed CrushFTP and the only thing I changed was the webUI port from 9090 to 9191 and the webUI will not load. I do not see any errors i this dockers log either....Any ideas?
  7. I noticed as today that my pre-existing speed limits for uploads are no longer enforced. Is this a known issue from a recent update?
  8. I'm trying to get the Wazuh virtual appliance working as a Centos vm. I've extracted the VMDK and mounted it in a new vm. But it boots up and then hangs at a log mount error after a disk io error. Centos, Q35, sata Anyone have any ideas? Sent from my SM-N960U using Tapatalk
  9. THANK YOU! Following these steps exactly got me passed the import of Wazuh VMDK "kernal panic fatal error'. It is now booting! :-) Now onto configuring it hopefully.
  10. Good morning all! When I attempted to start this docker today, it would not start with this error in the logs: Removing docker/image and reinstalling it fixed it for now. But is this going to come back? I generally leave the docker stopped and only run it when I'm doing scans.
  11. Thank you for making this available.
  12. Greetings! I did a quick search and did not come across anything; I currently monitor unRAID using the Grafana/InfluxDB using this dashboard https://github.com/gilbN/theme.park#graforg. It does a very nice job for Docker CPU and RAM usage monitoring. Is there a similar solution for monitoring VM performance running on unRAID?
  13. Upgraded from 6.7.0 with no noticeable issues. Thank you!
  14. So for me the issue is only with Organizr docker. If I restart Organzr the issue goes away temporarily. Any idea what the long-term fix might be? The Organizr docker log in unraid UI shows no issues. But the log in the Organizr webUI shows: "OMBI Connect Function - Error: cURL error 7: Failed to connect to 172.16.1.5 port 3579: Connection refused [Execution Time: 01.30s | 1308ms]" UPDATE: after restarting Organizr docker all seems fine for a few days now.
  15. This just happening on my unraid 6.70 a few days ago, before that it was fine. Any fix for this?