News History

For the news that are slightly too old for the front page, here are all the public announcements made since the first LeapingTiger server went online.

2017-11-22: Debian upgrade complete

Hisoka was upgraded to Debian 9 (stretch) today. Apart from some touchy configuration (looking at you dovecot and mariadb) it went pretty well. The server was also rebooted to use the latest available Linux kernel, thus resetting our uptime after nearly 500 uneventful days.

As usual, if you notice some of your stuff is broken after this update, please holler at me and I'll fix it as soon as I can!


2017-05-30: Tigris is now HTTPS-only

All virtual hosts on hisoka are now served exclusively over HTTPS, thanks to letsencrypt.org (please consider donating). Non-HTTPS request are automatically redirected to their secure URI, so this should have a minimal impact.

It's possible, however, that your site still might need special configuration to be compatible with HTTPS. Poke your favorite admin if it's the case, so we can fix it ASAP.

As usual, sorry for the inconvenience. It's for the greater good, this time!


2017-03-15: Self-hosted DNS

Our own DNS server hosted on hisoka now manages tigris.fr as well as leapingtiger.org. I didn't see anything breaking, and for all intents and purposes it should be entirely transparent to the end user.

But as usual, if something does break, yell very loud in my direction or something.


2016-08-22: leapingtiger.org DNS is back

I had completely forgotten that leapingtiger.org was managed by our own DNS server and didn't migrate the configuration to the new Debian installation. As such, all of leapingtiger.org was unreachable due to DNS lookup failure.

It's back, now. However, it's still deprecated and I strongly urge you to use tigris.fr instead.


2016-08-03: Welcome to hisoka v5

We have now migrated to Debian 8, to make maintenance easier and play along better with some legacy code.

This is still the same physical server, so all domains redirecting to hisoka's main IP should still work. However your SSH client will probably complain about a new server key (whose fingerprint should be e0:dd:b9:0a:e5:86:7f:da:21:54:31:24:8d:42:94:3a).

Some websites are still being migrated from lighttpd to nginx, but for all intents and purposes, hisoka should work just like before, except all our hosted sites should eventually be served exclusively over HTTPS, thanks to letsencrypt.

Sorry for any inconvenience, this should be the last big maintenance for a while.

Previous | Next

Sunday 16th of December 2018, 12:52 - 1.4.22 Tiger picture by Tambako