Oh, and happy Independance Day for those of us in the US. Xepher.net continues to chug along pretty reliably as of late, so no major problems to report. A small hiccup the other day with /tmp/ filling up, but it was only affecting things for a couple hours. Just a reminder to anyone submitting a problem/outage report... most of the time these end up being local/semi-local/ISP problems on the reporter's end, ocasionally a problem with the datacenter/backbone routing at this end, and rarely an actual problem with xepher.net itself. Still, I like to take all problem reports seriously, so if you do see a problem or can't connect, feel free to let me know. It's very helpful though if you give me an exact time when you noticed a problem, preferably in UTC, but at the very least, specify what timezone/offset you're in. Also, any network information you know how to get (like traceroutes) is always useful. Send me whatever you got, and I'll look into things. Likewise, if you get error messages or other such things, give me all the info you can.
I'm currently tracking (aka, I think I fixed it, but I'm not sure) a transient problem involving an SSL "Change Cipher Spec". This only really applies when you're visiting the secure sections (user-services, webmail, or phpMyAdmin) of the site (no user sites are affected.) But if you run into this (your browser will give an error about "change cipher spec" and not load a secure page), please let me know. Note: this is seperate from the issue with the self-signed certificate which is mentioned on the help page. (http://xepher.net/help.php)