so if, like me, you get errors when renewing a letsencrypt certificate, along the lines of

Attempting to renew cert from /etc/letsencrypt/renewal/domain.com.conf produced an unexpected error: The apache plugin is not working; there may be problems with your existing configuration.
The error was: PluginError(‘There has been an error in parsing the file /etc/apache2/sites-enabled/000-default.conf on line 59: Syntax error’,). Skipping.

This was due to VirtualHost *:433=”” which apache likes but certbot doesnt, removing the =”” and running certbot renew worked. I put the =”” back in and restarted Apache and everything is back to working.
I’ve actually had this problem more then once and each time I forget how I dealt with it….because I am useless.

Even though you should always care about certification, I only bother to do it so that I can get rid of pesky warnings in Chrome when connecting from where I work. Anyway, as this little server is a new setup where I trial new things, I opted to go with letsencrypt/certbot, this can now be verified at SSLLabs.
On a similar matter of gaining trust, keybase chat is now up and running, I can be contacted whenever you secret squirrels want to, here.
I also removed the fancybox posts with pictures of the cats. I couldn’t get on board with having such large images as part of the load, I promise to only link images in the future.
Also, turns out update/upgrade ruins permissions for random hexo files…you then find out that most of the troubleshooting pages for hexo users are written in Japanese and for Windows installations.

I have done a few different things

• added keybase link to footer (because we all want a circle of trust right?).
• add RSS feed generation and link to footer as atom.xml
• edited deploy script to prevent deletion of favion and ssh key for git deploy. I am sure there must be a way to fix this in the theme itself.
• added google analytics so that I can confirm I am the only person reading this.
• added an about page while not quite understanding why I dont have to publish the markdown file for it.

so it turns out my timezone data was all over the place. Even though everything was set to GMT+12 the date stated was 12 hours behind GMT. Anyways, to deal with being in GMT+13 thanks to daylight savings, the correct command is actually

1

ln -sf /usr/share/zoneinfo/Pacific/Auckland /etc/localtime

My dates should now all be accurate. Next step is to get the default markdown templates for draft and post to line up correctly and include some defaults.

so, hopefully the Disqus comments section will appear below?

so this would be a test of code blocks (obviously)

This is code

1
2
3

this could be code too
if I got it right
not haiku

1
2
3
4
5
6
7

public class Hello1
{
	public static void Main()
	{
		System.Console.WriteLine("Hello, World!");
	}
}

So now I have SSH keys setup to not bug me about credentials when deploying via git. This was actually a pain as I use lastpass for just about everything and had to call up the vault each time.
Next…getting the defult markdown file to generate with more usefull default content.

So this is where my ‘blog’ will be. I will use this as a place to note my findings when attempting to setup or install new tech/software.
I would imagine that I will actually use it as a hexo and/or node.js playground more than anything.