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?

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.

@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?

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.

@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

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.

@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

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...

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.

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

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

I quoted the wrong post... I have included updated Diagnostics. Thanks

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

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.

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...