Ryonez

This plugin critically fails to backup poste, WITHOUT USER NOTIFICATION Unfortunately, this has gutted my email system as I deleted the appdata folder for it after a change didn't work and was going to restore from backups. As far as I can tell, files and folders with mail group and mem user are what's missed:

I like to be there when updating just in case something breaks. Not sure if the auto update plugin would fix it though, because it wouldn't be updating the plugin would it? Or does it suppress the notifications anyway?

Dynamix System Statistics has a minimum Unraid version of 6.7.0 as of it's last update. Latest stable unRaid version is 6.6.6. I've been getting a notification about this update everyday for a week.

Would someone happen to have a guide on how to set up gitlab pages with the letsencrypt reverse proxy docker? I'v tried to go through it a few times, but with it wanting another ip, and another domain (I have one I can use), I'm really not sure how to proceed.

Ahh. I'd imagine they'd only be read when the connection is started. Shifting them off the flash wouldn't give any real benefit I think..

it's a hidden share called flash. So goto: `\\<unraidip>\flash`

Thank you, that worked. Would you be able to tell me what the "Extended Routing:" is for? Will I be able to have dockers/vms use the vpn, but still be able to access their web interfaces?

How do you set up the vpn client? The head post here links to: However that's a dead link. Also, the Client configuration file section is just a drop down box with nothing to select. My goal with this is to set up a reverse vpn for dockers to use.

So version restricted plugins will disable themselves if the versions don't match? And hey, no sweet, I'll just keep an eye on it anyway. I hope you enjoy your time away.

Alright, that's done the trick beautifully. Thank you very much, that was an amazingly fast hotfix >.< Do I just keep an eye out and remove it once I see the fix appear in an unRaid update, or will it remove itself when it's not needed? I haven't played with plugins in depth, so I'm not really aware of the intricacies for them.

The extra parameters are `--env GITLAB_OMNIBUS_CONFIG="external_url 'https://abc.def.com/'; nginx['listen_port'] = 9080; nginx['listen_https'] = false"`

This docker is failing to load for me after updating it this morning. The following error is returned: root@localhost:# logger 'docker command execution halted due to security violation (Bash command execution or redirection)' The command finished successfully!

Yup, something to do with starting up. 125 errors, all torrents with tracking errors, including those that had started to work again before restarting the docker container.

No. Though it seems some are responding now. They were working before I restarted the docker hours ago, I'll see if restarting it again drops them off again.

I've got this happening on all of my torrents, it's not just one tracker affected. This could be a problem...

Has something happened in the last update? All of the torrents trackers are no longer responding. Tried switching the vpn to a different endpoint, put no dice.

Just finished on my end, preclear successful. Thank you for fixing it up.

Great to hear. I'll stop the preclear I'm doing with the other script and use this. I'll verify if it works my end.

Not sure how it's unsafe. The drive has completed two full reads successfully. So no bad sectors. The writing worked, thought the other script seems to missed someplace as part of the the script, not the hdd, which caused the post-read to fail. The reason the ppre-read takes so long is to add stress to the drive to see if it fails isn't it? The hdd has already had two full-reads, and two full writes, so I'm not sure where the risk is in skipping the pre-read and speeding up the post-read. At this point I don't see how increasing the time would increase the safety.

Great, so I don't need to specify the starting sector. I'll be using the -W flag to skip the pre-read, the drive has completed that twice successfully with the other script. I am looking at using the -f flag for fast post-read, as the normal post-read is designed to test the hdd as well. This drive has already gone through two full reads and two, mostly full? writes with gfjardim's script. I should be alright with the fast post-read, yes?

Okay, I've had a quick look at the script, I'm just worried what values I should use for the starting sector.

No, I've been using gfjardim's. Not sure where to install and how use BJP's.

But binhex suggests using gfjardim's atm. Isn't that not working though, or is there a patch for that? I've started looking through the forums after the second Post-Read fail, and am having trouble piecing together what's happening and what's working.

There isn't an issue with them: I tested it with the tools on poste.io's site, and can see them passing in the email headers.

It says it's found a DNS record. Why do you ask?