bombz

Hello, Checking in if there has been any updates/progress with the plugin? Thanks.

Hello, Stumbled across this docker randomly. Very happy to see it in CA! Installed the container , configured revproxy, everything is up and running in 5 minutes! Looking forward to more to come from this CA app. The fact that there is no storage path required for Ephemarel is awesome! Super handy docker! On another note, this CA app in the logs say this CA is EOL installed the new repo here: pglombardo/pwpush:latest

Would you mind posting your guide for Nginx proxy manager when you have a moment? Reviewing this specific guide, the paths posted are for letsencrypt ... which differ for Nginx proxy manager. Thank you.

Hello, Appreciate your time to review the logs. Interesting enough I pushed another scan on that instance and can confirm it is no longer appearing. I will keep an eye on things moving forward to see if it reoccurs. Thank you,

Hello, Sounds great! Has been a such a useful plugin over the years, be wonderful to resolve the concern. Appreciate the follow-up !

Hello, Please see attached. Thank you :-) diagnostics-20240822-1704.zip

Reporting same result. Fix Common Problems / Update Assistant not seeing new versions (reporting 6.12.10) is the latest. Is there a known fix or plugin update in the works perhaps?

Error: Rootfs file is getting full (currently 91 % used) Ran: df -h / Result: Filesystem Size Used Avail Use% Mounted on rootfs 12G 441M 12G 4% / To me the result doesn't look like it matches up with the error...Any ideas?

Any word on update assistant seeking the latest version? I understand manual intervention will work successfully... was curious if the dev-team was aware? Thank you.

+1 Same concern here <posted above>

FYI: Noticed on two running instances: Instance 01 - does not populate 6.12.11 update available in banner + update assistant does not detect 6.12.11 new version. <6.12.10 detected as latest> Instance 02 - does populate 6.12.11 update available in banner + update assistant does not detect 6.12.11 new version. <6.12.10 detected as latest> Thanks for all the hard work over the years!

as posted in 2 surpises: The workaround for this is to copy from source to destination, so that new files get created following the user share settings, then deleting from the source. The method I am using is moving data from /user/share -> /user/share Essentially this is not a source to destination move as I am not using the direct disk path. This was the confusing part, as /user/share -> /user/share/ was deemed safe, this is contraindicating that.

unBALANCE is wonderful I have it installed. It is strictly for moving data from disk to disk, which is awesome during a migration or backup! So thank you. I will see if I can get it to move share -> share EDIT: Looks like a i will move the data around with unBALANCED and monitor as the disk fills. Once filled move other data to another disk, and keep the same DIR structure throughout. I was thinking of disabling parity doing this but that raises some flags. I suppose I could enable turbo write

That Included setting just makes it so Unraid will choose from only those disks when deciding where to write a new file. Right, therefore disk 1 is outside any /user/share to which is why I would keep disk 1 as a /disk/share to write to when I needed That is safe (no data loss), but possibly still subject to the surprise #2 I mentioned. OK Another thing people often use for moving files on their server is the unBALANCE plugin. I will look into this. I would love some type of GUI i can run from Windows to move files within the server without having to hop out of the server.

Interesting and confusing. From my attached screen, you are saying DISK1 is included in this user share, even though it is not specifically specified in the user share itself? That's the confusing part. Right now I am moving data from user/share -> user/share I guess I will have to see how it goes, I am hesitant to make any changes now, but that will not allow me to consolidate. Thank you for the feedback.