Happy New Year! It is the beginning of a new year.
This is a year of Tori, according to the Oriental Zodiac.
Though Tori is bird(s) in Japanese, I image cock(s), hen(s) or chick(s) as a symbol of the year of Tori, maybe other Japanese will agree.
By kanji and Hiragana we write 酉年 or とり年, but don’t write 鳥年. Originally 酉 doesn’t mean birds though we use chicken’s image as the Tori year icon.
Recently, when I drive along the river on the way to and from home, I see them almost every time. They are Ohban. I think this year is the first year when I see them.
I couldn’t find some time to take photos of them until today and I did it today. I didn’t descend to the riverbank because I had no much time. I use zoom feature of DSC-WX220. So, their images are not clear. But one of them looked having something orange. Is it food?
Yesterday, around 17:00 JST, on TODOS くりくりさん said he wasn’t able to reach my site because of ‘正引きできない’.
I guess he had ‘ERR_NAME_NOT_RESOLVED’ or ‘DNS_PROBE_FINISHED_NXDOMAIN’.
I found his comment and was very surprised around 19:30 JST. Very late (^_^;). I checked my site. I maybe made the same stupid thing again, but it’s not my fault at this time.
くりくりさん told me eNomのネームサーバー障害, and I found them out, enomsupport1, enomsupport2, enomsupport3 and enomsupport4.
eNom hit with heavy DDoS attack yesterday, which caused domain name resolution problems. See ‘eNom hit with DDoS attack – domain registrar is currently stable’.
On November 11, I updated AWStats from 7.4 to 7.5, as I forgot to do it though I found AWStats7.5 when they released it in April. If you need How To, see ‘Updating to AWStats7.3’.
On October 26, my NJ2100 was suddenly broken when I installed my first wireless router which is WHR-1166DHP3. Until now, I’ve struggled in vain, finally I give up.
I cannot even get in BIOS.
I first doubted the LCD because it hadn’t been good since the other day, but maybe this is not its faults. Because I cannot see anything from an external monitor, either. Its HDD is fine. I found its data still existed in itself though I don’t need the data because I always backed my data up. I replaced memory modules, which gave no effects. I guess this is probably a malfunction about one of the parts on the system board because I cannot even get in BIOS. I ran out of bullets. (T_T)
I had it on 2008 March 5 with ¥178,800 + consumption tax (it was 3% at the time).
Yesterday, I changed one of my router settings and rebooted it. After that, I checked I was able to access my sites from the Internet or not. I couldn’t. Because Dice didn’t work well. I changed DDNS IP address by manual though I wondered why it didn’t work. Then I became to access my sites.
But I continued to change settings and rebooted again and again. I forgot to check final accessibility from the Internet. Dice didn’t work at the time, either. So you couldn’t access my site until about 9 am.
Why didn’t Dice work? What trap did I blunder into?
It was A password.
When I last changed my eNom password, I forget to tell it to Dice. I’m embarrassed I wants to disappear.
[2017.OCt.20] We can use mod_md in ApacheLounge 2.4.x version now, so I changed from dehydrated (former Letsencrypt.sh) to mod_md about certs updating tool. About this, see → “From dehydrate to mod_md, Let’s Encrypt Tool”.
========================================================
On October 7, when I tested my site by SSL Server Test, I found ‘OCSP Must Staple Not Supported’ on it. So, I re-checked the old test report and also saw ‘OCSP Must Staple Not Supported’ there. I talked about this with くりくりさん at my Japanese blog comments. We also talked about Extended Validation(EV), CHACHA20, and Certificate Transparency(CT). But, these three are not available for my server now. EV is expensive. CHACHA20 Apache official version already supports but Apache Lounge version 2.4.23, which is my server current version, hasn’t yet. If I want to use, I need to build the supported version by myself. This is difficult for me. CT Apache hasn’t supported yet.
However, I changed several things about my server TLS environment.
Recently, I had an email from YAHOO!. Its subject is “Secure your Yahoo account”. I think this is maybe related to “Yahoo hit in worst hack ever, 500 million accounts swiped”. Because …
[2017.OCt.20] We can use mod_md in ApacheLounge 2.4.x version now, so I changed from dehydrated (former Letsencrypt.sh) to mod_md about certs updating tool. About this, see → “From dehydrate to mod_md, Let’s Encrypt Tool”.
========================================================
[Oct.26] As I use Elliptic curve Diffie–Hellman (ECDH) for kx now, I posted a new article. ☞“Letsencrypt.sh on Windows-#4”
========================================================
On September 17, I got the first success of the renewal of Let’s Encrypt Certificates. The script and my batch made it at the daily task. I found the file differences in my Certs folder on the server like this ☟.
