math-captcha domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/news.numlock.ch/public_html/wp-includes/functions.php on line 6114
Make a diff!
Just a quick update to let you know that this blog/changelog will soon be migrated to a new (faster) server.
I’ll keep (unavoidable, due to DNS changes [see comments below, ed.]) downtimes at the minimum and will inform you in advance about expected outages.
Thanks for your understanding.
If you change your A record’s TTL to a very low number, let’s say 60 ahead of your current TTL value, you should have pretty smooth transition. Also, your SSL cert is invalid :)
Thanks, Andy, for pointing this out.
You’re right, and actually, the TTL setting is at very low 20 seconds already. Theoretically, DNS caching thus shouldn’t cause any noticeable service interruption for most visitors.
The strange thing is that I already migrated the SMTP server(s) a while ago, i.e. adjusted the MX record(s), and noticed quite a lag (of several hours) in regard to DNS refreshes, in spite of these super-low TTL setting(s). Overruling those TTL settings on the client side might be more common than I thought. Or perhaps, my current DNS provider simply failed to propagate the new IP address to its DNS servers in a timely manner. I didn’t investigate any further as I didn’t care too much, admittedly (as these aren’t customer domains and generally low-traffic servers).
Re the invalid SSL cert: The cert is actually fine, but self-signed only. On purpose, as this is a rather unimportant server (read: not used for commercial purposes). You can always check the cert’s validity manually here using PGP though:
https://news.numlock.ch/certs/
https://news.numlock.ch/pubkey/
For commercial/customer sites, certs signed by well-known Root-CAs are used.
Cheers
Dani