Being super pumped for the new Lets Encrypt project, I signed up for it shortly after beta and started using it some production web servers. As of this posting, I haven’t done on this web server… obviously. But I should do that soon. A couple customers use Owncloud and DAVdroid to sync their files with works great but they kept getting this error message on their phones.

Well that got really annoying quick and many times caused syncing to fail. People got mad… I got called… meh. IT Happens.

Seems there is an X1 chain of certificates that is not trusted or a link in the chain is just unknown to android. To fix this, we just need to add a link in the chain to let it know. Full disclosure though, I did not think of this on my own. I found the answer on this page.

https://community.letsencrypt.org/t/cert-not-work-in-firefox/5272/10

The error appears in Firefox it seems for the same reasons. The last post in the thread shows you need to do. Those of you with Nginx should be able to do something similar but this was the solution for me with all my Apache Servers. Where is solution from the last post in the thread.

This will give whatever client, be it Firefox or DAVdroid, the links in the certificate chain to trust the certificate. I’m not an expert in certificates but I am assuming this is a short lived bug in the project.

Props to the Lets Encrypt Project and it’s sponsors for this. This is huge and will change the internet for the better.

I find VBScript to be buggy and doesn’t flow very well for me. I’m still decent at it but Powershell has been my scripting language of choice for a while. Here is another little diddy I made out of Powershell.

I present to you…. File Delete! Yea it’s a common thing you do I know but darn it, I don’t like using the admin share all the time to delete files off hundreds of computers. I execute this script… kick back… watch the beauty of the text scroll up my screen and watch for any errors and investigate. All while the user is using the computer and they never know! Makes me feel like some sort of wizard… or ninja….

Ok, grown up time Keith.

So the script is similar to the rest. Change the last line to your computers.txt file path.

Line 4 is then the file path you want to delete on your remote computer. This script takes advantages of UNC paths for windows so when you enter this part in, just think of it as you would for a standard admin share. Remember you will need access to the file location. Powershell will use the credentials that was opened with your Powershell or Powershell ISE window.

Because I am also experimenting with using Log files, you’ll also need to make an area for the log file for this script. Or you can delete that area. I’m starting to like log file though in my scripts.