local.bin

Interesting, so they don't highlight those two versions on their user website for general downloads, just one x64 download, which I used. Perhaps they have changed their approach, or mis-labeled the versions.

ok thanks.

Thanks for confirming. I've downloaded the binary directly from resilio sync and it has the same problem, so it appears that its not the binary but the docker itself.

With the latest update i am getting the following errors from the sync binary; Wondered if anyone is seeing the same? Have removed and added a couple of times now with no errors on installing, but the binary will not execute. The same errors are in the docker log. TIA

Something very weird is going on during/after a backup has occurred and I am struggling to track it down. I lose my config, the docker tab disappears from the main menu and I have to shut the machine down and reboot to get it back. I have taken a diagnostic log but there are no errors, as it seems after the event there is no issue. I struggle to get a diagnostic when the issue occurs as the menu's are all misbehaving. The issue only occurs during/after a backup has taken place? Any thoughts as to how to track this down further please? Thanks in advance. I have log to stick enabled but there is no log for today, only a successful log for the 24th April.

Thanks, I had a feeling it was a little more involved Haven't had a chance to take a look yet, but will do hopefully over the weekend.

Could you clarify if you have anything else done to get this working, as it doesn't recreate the abc crontab file for me. The command works fine in isolation and works great when I manually enter the same details in the abc crontab file myself. It wont though create the file itself on container update. I am trying to track down which logs I might find some information as to why at the moment.

Didn't know that, as I thought it was building from github latest release tags.

I've tried fully removing and installing from scratch and I'm am still on v0.14.25, Linux (64 bit) "Dysprosium Dragonfly", while github is showing v0.14.26 as being available? https://github.com/syncthing/syncthing/releases/ Not urgent, just wondered if others had gotten the update already?

Mmh thats odd, as you could create two separate syncs, one for photo and one for video and select the sync time or on demand per sync pair. You can also select whether you want over wifi, specific wifi or 4g.... Add a file type filter to each, to only select pics or video if they are in the same source directory.

Having the same issue as you on Nougat with their app. Have tried the beta and it doesn't work for me either. I have great success with foldersync on android though, which syncs everything with fine grained control, when and how I want, so I use that to be honest. I have the paid version, but there is a lite version you could try, to see if it supports nextcloud. The paid version works fine as I say.

Ok thanks Probably right, just me trying to get the A+ from an A Seems there is some dev from LE to perhaps make the process more automatic, so maybe there will be more options in the future.

I wondered if you had any plans of supporting manual updates, or forcing the use of the same CA cert, in order to be able to manage hpkp pinning? I have the certs setup and working, but the auto update would mean I likely lock myself out of my site each time the renewal occurs. I wondered if anyone had a working hpkp pinning process at all? Thanks in advance certbot-http-public-key-pinning-hpkp/

mmh, yes, thats what I was using too, but hadn't noticed a spurious hash in front of the command! Sorry about that

OK, so my script ran according to the logs but only the nextcloud one worked. My other one failed for some reason. I think it was because in the grep command I only had piwik, rather than nginx-piwik. Just to clarify, your abc cron file, is that in addition to the root cron that exists in /etc/crontabs already? I presume so, so how do you get cron to see it as an additional cron? I have manually added abc cron file and restarted the cron service, but abc's commands do not get listed as current crons in crontab -l

Appreciated, thanks for taking a look.

Thanks for the insight and option for me to try. I have added similar for my case and await an update to test it. I was hoping for the letsencrypt crontab functionality to be added, but hopefully this will do the job.

Is there a way to have crontabs remain past an update at all please, like the letsencrypt container. I've used this as a generic container for my web based apps, but am struggling with the cron getting wiped out. Thanks in advance.

Thanks for the further guidance, which helped me get it working. This works for me; Edit jail.local and add the following to the nextcloud or other jail; Copy ..action.d/sendmail-whois.conf to sendmail-whois.local and then edit the last line of the action, changing the sendmail command line part;

Thanks for that. It does indeed work as you suggest it does. I am trying to incorporate sendmail using the standard fail2ban actions in actions.d in order that the email content is created by fail2ban, to give me the detail of who has been banned etc. The fail2ban docs talk about adding the following to jail.local, which works, but because sendmail does not have the base config setup via its config (-H 'exec openssl s_client -quiet -tls1 -connect smtp.gmail.com:465' -auMYEMAILADDRESS -apMYPASSWORD) it fails, as sendmail tries to send from localhost. mta = mail action = %(action_mw)s

I have gone through exactly the same process today and as you found no config files to setup proxying to gmail to be able to send emails out. I had to park it for now, but we must be missing something simple, as installing sendmail should have created the config files somewhere. At least thats my thought process

Thanks for the comprehensive writeup, very helpful thanks. I had understood, obviously wrongly that fail2ban would still block attempts at the proxy first, but after testing this I do get the correct IP address to ban. If I have understood correctly, the base setup for the letsencrypt docker will only log and block .htaccess failures via nginx, but as I don't use that for nextcloud and piwik, neither would be protected by fail2ban. I moved the nextcloud.log to my nextcloud data directly, rather than mounting my data directly from letsencypt and note that the config.php edits are also needed to get nextcloud to output the log to the appropriate place Works nicely, thanks. Now to see if I can do the same with Piwik and get them both logged by netdata

Whats the benefit of adding the specific nextcloud filter when the original setup would do the same.

Thanks for that, I'd twigged when I reread the second para of dmacias As I edited, apart from nextcloud individual filters, wouldn't the same IP still get banned in the setup now, but just wouldn't be listed in a specific nextcloud filter?

@dmacias Thanks for the explanation. I was at a more principle level in that I'd understood, the letsencrypt docker was looking at its nginx access logs in order to ban attempts to access any and all of the servers that it was proxying. I presume you are additionally setting up fail2ban on the nextcloud docker too, in order to detect nextcloud specific access attempts and the need to get the real IP of the remote user, rather than the IP address of the LE proxy. I've got these setup and working nicely, but am not sure fail2ban on he LE docker is doing what I think it is, hence my continued clarification. Apologies for being a bit slow Edit: Ok, reading 2nd para again, it seems you are sharing the nextcloud specific logs via mount points to the LE container, so that the LE container can be setup specifically to monitor and ban nextcloud specific attempts, which makes sense. If those logs only contained the IP's of the proxy then the remote client would never be banned. Is giving the NC logs better than the LE container blocking the IP anyway? as wouldn;t the same IP be in the generic nginx logs as well? Guess that is what I am missing.