ceyo14

Members
 View Profile  See their activity

  • Posts

    140

  • Joined

  • Last visited

 Content Type 

Everything posted by ceyo14

  1. ceyo14
    Hello, I have the following message, Is this something I need or can do? if so how? Or do I just wait for an update to the docker?
  2. ceyo14
    ok, I figured it out... instead of extra parameters or post arguments, you need to add a Variable... there I put the following. In case someone needs this, or me in the future.
  3. ceyo14
    @Marzel So I couldn't connect to the docker and saw that it updated... this changed the port again to 5000. how can I prevent this from happening?
  4. ceyo14
    Thanks for posting this, I had been using ipvlan without issue with Untangle and OPNsense, but recently switched to Sophos XG and it immediately had issues with it, I changed it to macvlan and have had no further issues but remember I switched to ipvlan for a reason, I mean I can't remember why now but I was curious why Sophos didn't like ipvlan... but this seems like a much better option regardless.
  5. ceyo14
    @Marzel Can you please change the ENV to the Unraid template instead of the image? I assign an IP address to the Docker and I would like it to listen to port 80 and not 5000. I can change it using Portainer but I have to recreate the docker and I am worried about updates... ASPNETCORE_URLS http://*:80
  6. ceyo14
    I believe it was stated that on reboot it gets overwritten, hence why it says not to use scripts. so if you changed it manually you can just install this plugin so it will do it for you and stop once you upgrade as it is made to work up to version 6.11.5 and not anything newer.
  7. ceyo14
    @Djoss Just an FYI in case you didn't receive their email about it, there is a branding update for Crashplan 11 that will affect the names of some packages or processes... Change is scheduled for March. https://support.crashplan.com/hc/en-us/articles/11427606025997
  8. ceyo14
    I understand, can I ask that you undeprecate the agent? I was able to use another docker and it seems to be working so far. but obviuosly I get the mmessage about it being deprecated and I am guessing if I remove it I won't be able to re install the agent...
  9. ceyo14
    I haven't had any further lockups yet... it's been up 7 days and I plan to change some hardware so if anything I will open another thread if needed. thanks for your help.
  10. ceyo14
    ok, I just fixed that, hopefully it improves stability. This is something else that is happening lately, this is the output when trying to boot, the reason sometimes after the second boot it comes up. (what I mentioned above about it refusing to boot) Including fresh logs and diagnostics... not sure if it helps. Thanks a lot for the help. nas-diagnostics-20220807-1931.zip syslog
  11. ceyo14
    that is for the plugin, it was already installed but it appears to have been deprecated... I left it to use with the new docker. it is working. syslog
  12. ceyo14
    I quoted the wrong post... I have included updated Diagnostics. Thanks
  13. ceyo14
    ok, today it locked up but was able to sort of login through the IPMI, sent reboot through the Terminal but it didn't respond, sent cold boot and it started normally... I do see the Parity drive is reporting issues, I am looking to replace it, Parity Check started but was going at 13MB/s... so I canceled it. Please let me know if there is anything else. nas-diagnostics-20220802-1814.zip
  14. ceyo14
    ok, I enabled the Mirror to Flash Option, will reply when it crashes again. FYI I replaced a deprecated CheckMK docker from CA and installed one from the DockerHUB. only change, this was performed today, hopefully this is irrelevant.
  15. ceyo14
    Will you still work on this?, Or do you think that at this point you will not continue supporting CheckMK? I always wanted to get this running but haven't had much time to get it to work. I mean actually using it... it ran if I stayed away from 2.0 I understand whatever your decision is, not expecting anything, just wondering...
  16. ceyo14
    I need some help identifying this, I have seen the server refuse to boot giving something about a USB device, it says sda which is the unraid flash drive, I checked it on a windows PC and it didn't find any errors and another reboot usually worked. today it locked up again but it booted up in the first try after a cold boot, but this time the parity drive threw a Helium error which I have never seen but just appeared. FYI I run my router in a Nested VM so it boots without internet. nas-diagnostics-20220728-2246.zip
  17. ceyo14
    Make sure PiHole is not blocking http://msftncsi.com/, or better yet, whitelist it.
  18. ceyo14
    ok, I just reinstalled, hopefully it goes better, not an issue with this docker stopped so it is definitely something with it. I will update if I have more issues.
  19. ceyo14
    it doesn't actually lock up the server, what doesn't work that I can tell is the WebGUI, obviously the Checkmk Docker and for some reason if I try and pull diagnostics using SSH, it freezes and never completes.... VMs and other docker still work though
  20. ceyo14
    its the WebGUI and that docker that lockup... webgui I get a 500 error, docker just stays loading.... I just got it again after upgrading to 2.0... I will have to check this out.
  21. ceyo14
    I think that helped, before it would be pretty quick to lockup... its been a few hours and I've been able to use it so I think we are good. so how do I update to the new 2.0 version?
  22. ceyo14
    ok, just made the changes and started the docker... For reference I have 4 day 4 hours of uptime currently... let see how it goes...
  23. ceyo14
    have you been able to check on the checkmk docker?
  24. ceyo14
    of course, its not like I am paying you... lol obviously I understand that with so many things on my server it may work for you and I have something else that "bothers" it... Let me know how it works for you to then see what we can try on mine. if anything write a PM to check this out more in depth.
  25. ceyo14
    yes on 1.5.0, have not changed to 2.0.0 I am running 6.9.2 and a bunch of other things... not sure if these help, but I am including diagnostics as of now, working normally... without the checkmk docker running nas-diagnostics-20210618-1338.zip