Jul 242013
 

This blog is starting to get old :-) Next February this weblog will be 10! I think it started with pMachine, then b2Evolution, and after that several versions of WordPress. I know I used some ASP.NET software at first, when the server was still a Windows machine, but “.Text” was not stable enough (reboots made the weblog unavailable), so that’s when I started with PHP-based weblog software and finally ended up with the best one!

Recently I installed a broken-link checker plugin, and that resulted in quite a number of dead links. Some that were links to my own weblog. I “unlinked” most of the external links (so the link is removed), and I am trying to sort out my own links. I restored some pictures already, but disk crashes in the past resulted in some media referred to by the links to be gone. Should have made better backups. Mind the word “should”.

Feb 022013
 

Just changed the server’s Apache model from Prefork to Worker. Should be easier on the memory and the CPU, but after downloading/installing it (via aptitude) nothing worked anymore. PHP works different under the Worker model, so directories need an extra handler and options. No biggie, read this thread.

Jan 162013
 

I saw that images in old posts weren’t showing, so for what it’s worth I restored the images as far as I could find them. That’s the problem with harddisk crashes, not everything can be restored. If you’re missing anything, tell me.

Jul 192012
 

To have some directories on my server protected by more than a simple username and password, I wanted to use SSL and client certificates. I could easily restrict the directories to my local network IP-addresses, but when I’m “outside” that would present a problem. Hence the solution with client certificates.

 

As I blogged earlier, I requested a real server certificate from the people at Xolphin. Nice people, low prices, fast service. But…..you cannot create/sign client certificates with such a certificate. You need the real certificate installed on the server, and you need to create a certificate that has been created/signed by you as a fake Certificate Authority. The Fake CA has to be known to Apache and to your browser. Next the client certificate (created/signed by the Fake CA) must be imported into your browser, and of course the directories you want to protect need to be in the SSL-configuration of Apache.

 

Now that I know how it works, it is simple, but most guides on the internet either follow the Fake CA principle (so you don’t need to buy a real certificate) or they only use a real certificate. Spending money to have your SSL-certificate-supplier do the job for you is another thing. But this works. And for € 10 (excluding VAT) per year I now have a real server certificate, and I can further protect my server with my own certificates.

Jul 152012
 

The domain switchbl8.nl now runs on a PC/server again. I replaced the motherboard, processor and memory, and ditched the old 9GB SCSI disk in favor of a 60GB SSD from Adata. Also, the system now runs Ubuntu 12.04 LTS x64, no longer the unmaintained 7.04 (in 32-bits).

 

The gallery is not back yet, gotta find out how to reimport/recreate the original structure, but as you can see, the weblog is up and running.

Jul 062012
 

The Synology has a WordPress module, which works great and it is a recent version (not the latest). But you are bound to having your weblog in the folder “/wordpress”, and my weblog resides in “/blog” for ages now. I couldn’t find how to change it by modifying PHP files, wp_options entries and just renaming the folder. So….

 

# mkdir blog

# cd blog

# unzip /tmp/wordpress-3.4.1.zip

# mv wordpress/* ./

# rmdir wordpress

 

And point your browser to the URL “synology-ip-adres/blog” and do the install.

 

I used the database credentials created by the Synology WordPress module, and vanilla-WordPress then says: Hey, already installed. Via the Admin panel you upgrade your database, and you’re good to go. Now disable the Synology WordPress module.  I haven’t uninstalled it, since I don’t know whether it will actually delete the database too.