make_sock: could not bind to address 0.0.0.0:443 no listening sockets available, shutting down

meaning, that the TCP port 443 was allready in use by another aplication. But since I did not install any other server software, I was confused which program would dare to occupy the standard https port… A quick google search helped me to figure out some “command prompt magic” to find the delinquent. The command

netstat -ano | findstr :443

returned

TCP 0.0.0.0:443 0.0.0.0:0 LISTEN 5104

which helped me to find the process ID of the program using port 443, in this case 5104. But since this PID number did not show up in the windows task manager (which scared me a little bit), I again did some googling and found the tasklist command:

tasklist | findstr 5104

revealed that Skype.exe was responsible for the “port occupation”. So I opened up Skype and started looking for reasons. Under “Tools > Options > Advanced > Connection” I found a checkbox labled “Use port 80 and 443 as alternatives for incoming connections”… I unchecked it, restarted skype, et voilà: XAMPP worked like a charm!

Skype setting to use TCP ports 80 and 443

Hope this helps you (and me again) sometimes… Cheers, Tobi

With the upcoming release of Lightroom 4 (it is being beta-tested at the moment), now is a very good time to get started with it (Lightroom I mean)!
You can get Lightroom 3 for about 120 Euros at the moment (for example at Amazon)! That is about 60% cheaper than the regular 300 bucks you have to pay for the full version.

I thought we were talking about buying Lightroom 4 not Version 3!

I was just getting there: Even if you buy the update to Lightroom 4 later on, you still can expect to get away way cheaper than buying the full version for 300€. The upgrade from Lightroom 2 to Lightroom 3 costed about 90 Euros, so if we expect the upgrade prices to stay close to that, we’ll be able to get a full version of Lightroom 4 for about 210€ (120€ for Lightroom 3 and 90€ fot the upgrade to Version 4). That is about 90€ cheaper than the full version, if we presume the release price is the same as for Lightroom 3.

Summary

Ok, all those numbers can be confusing, so here’s the short version: if you are planning to buy Lightroom, buy version 3 now and an upgrade to version 4 later and you’ll save a lot of money!

Weltuntergang

Weltuntergangsstimmung am Spargelfest

Da will man nur gemütlich ein paar Spargel essen, und plötzlich geht die Welt unter… naja, wenigstens sah es so aus als würde sie, tat sie dann aber doch nicht.
Das ist mal wieder der perfekte Beweis dafür, dass man seine Kamera immer dann nicht dabei hat, wenn man über ein schönes Motiv stolpert… Naja, wenigstens hatte ich mein Handy dabei. Besser Handyfoto als gar keines

This picture was originally uploaded to my flickr account. Check it out for more pictures!

Schmackhaftigkeiten

A menue in a bar in munich. It was just lit by the candle and the dimmed ambient light. I liked the mood of the scene

This picture was originally uploaded to my flickr account. Check it out for more pictures!

Suddenly my website stopped working at all. I got just a blank white page, with no code whatsoever in it. Even the administrative backend stopped working.

After a long time tinkering around with WP source files and after reestoring the database and the WP- configuration for about 100 times (OK, it was two times, but it felt like 100 times I figured out that it had something to do with the WP-Supercache-Plugin. after I deleted the line “define(‘WP_CACHE’, true); //Added by WP-Cache Manager” in the wp-config.php I finally could log into my admin backend again.

Unfortunately, whenever I opened the plugin configuratio page it automatically added this line to the config file, rendering my blog useless again.

So, now knowing what was wrong, I did some research. Reading the official installation manual (which quite changed since I installed the plugin a lon time ago) I found out, that there ought to be a second .htaccess-file in the folder “/wp-content/cache/” containing the following:


# BEGIN supercache
<IfModule mod_mime.c>
<FilesMatch "\.html\.gz$">
ForceType text/html
FileETag None
</FilesMatch>
AddEncoding gzip .gz
AddType text/html .gz
</IfModule>
<IfModule mod_deflate.c>
SetEnvIfNoCase Request_URI \.gz$ no-gzip
</IfModule>
<IfModule mod_headers.c>
Header set Cache-Control 'max-age=300, must-revalidate'
</IfModule>
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType text/html A300
</IfModule>
# END supercache

I also figured out, that my WP-folder did not contain a “wp-cache-config.php” file. After copying the example file from the plugin folder (wp-content/plugins/wp-super-cache/wp-cache-config-example.php) and renaming it to “wp-cache-config.php” my blog started working again. Yipee!

I don’t know if I messed things up during the update-process, or if something else went wrong, but now my blog is working again, and I still can use wp-super-cache, which is a great plugin by the way!

As mentioned above, the official WP Super Cache installation instruction helped me a great deal to figure out my problem. You can find it here http://wordpress.org/extend/plugins/wp-super-cache/installation/

I hope this helps. If you have any suggestions please leave a comment!

Whiteout, originally uploaded by tobbikern.

A new pic on Flickr

Here’s a new photo, fianlly A shell on a reflective surface, lit ba two flashlights (one with a softbox from the top, one with a grid from the left side…

A study in bananas – part 3

A study in bananas – part 2 of 3

A study in bananas – The first of a series of thre pictures I already shot two years ago… these shall decorate our wall in the “near” future! We’ll see