If you want to speed up your server with NGINX and you run WordPress, you might want to grab this plugin to make WordPress permalinks more compatible.

WordPress Permalinks and NGINX

Hopefully I will find some time to document my experiences with nginx and post them here. Exciting stuff for sure!

Today it was time to take another look at my site speed. As sites grow you need to adjust server settings etc. I just wanted to post my experiences here. I could write a book about optimizing dedicated servers by now (I’m not joking btw), so it’s a very wide topic, but here are my tips.

If you have problems with images created by TimThumb that have spaces in their filenames then here is the fix. WORKS 100%!

I haven’t posted here in a long time, because I was quite busy being a webmaster. Anyway, today I am going to show you how you can make the TimTHumb script W3C-valid!

I haven’t added anything new to this blog for a while, but today I stumbled on a really useful trick that allows you to force a file download of specific file types via .htaccess. More after the break.

If you find this in your apache error.log: Premature end of script headers in index.php and get a 500 error on your wordpress blog, then you should check your suexec log. When it reaches 2GB you will receive a 500 error and the message: Premature end of script headers

You can find the log here: /var/log/apache/suexec.log or simply enter locate suexec.log

Also check your /var/log/suphp.log … if it is over 2GB large you will receive the 500 error!

If you find this error in your apache error.log you most likely have rebuild your system and broke a few apache modules.

I received the error after rebuilding my system with EasyApache and using APC + Memcache. I compiled memcache and APC myself, so after rebuilding the system via EasyApache it would receive the error: child pid exit signal segmentation fault 11

If that is not your problem, you should rebuild apache without eaccelerator, acp or memcache, because they can cause the problem.

… if you encounter this or a similar problem the easiest solution is to validate your feed.

To validate your RSS feed, simply go to http://feedvalidator.org/check.cgi?url=

Enter your Feed URL and hit enter. Now you know if the feed is valid or not. Most likely it is not. Write down the error line and find out what entry is causing the error. When you found the post you should remove any signs that might cause problems. In my case I had to remove the “&-sign”. Because HTML hex-codes normally start with the “&”-sign they are causing some problems sometimes.