Notes from building KNJ Panel, in the order it actually happened.
blog /blɒɡ/ noun — 1. A web log. 2. Here: a build log. What we built, what broke, and what we learned.
Feedback raised two problems in webmail: a sidebar that drifted out of reach as messages piled up, and an address book that was empty in one place and…
Read more →A domain reached on the panel port returned an error that the request was too large, even though the request had not grown. Cause The feature that lets…
Read more →A recent incident showed that when a domain’s certificate has not been issued yet, an HTTPS visit fell through to the server’s default site and could show unrelated…
Read more →A restored account’s contacts had already been confirmed safe once, checked against the real contact entries with nothing missing. Then the actual owner tried to use them, and…
Read more →A new restore-time safeguard shipped the same day it was designed, and within hours we found it produced a false positive on a core WordPress file. The unit…
Read more →Our earlier review of a problematic backup was manual, which is not a repeatable safeguard. This phase makes the restore check for it automatically. A gap in signature…
Read more →The dashboard hang from earlier was supposed to be closed, but a satellite server still hung at login. The first fix was real and necessary, but not the…
Read more →Finding the missing contacts raised a broader question: what else might a backup carry that the restore never looks for? We reviewed a real-world archive against what the…
Read more →On a test restore, an account’s dashboard showed 1MB used although its files totalled about 1.8GB. On this server the home area was on a separate disk, and…
Read more →The admin dashboard on a satellite server showed a spinner indefinitely. The page shell loaded instantly, but a request for live service status never returned while every other…
Read more →While testing a restore from a real-world backup, everything checked out except the saved webmail contacts. The restore feature had never looked for them, although a full-account backup…
Read more →Two bugs this week turned out to be patterns, so we checked for the same shape elsewhere. The log that doubled itself The malware scan log showed each…
Read more →Two reports arrived together: a customer’s own domain on the account port showed a certificate warning, and the dashboard’s disk usage read “Unlimited” instead of a real number.…
Read more →During restore testing, an account with four subdomains had working DNS for only the first one. The records existed in the database but were missing from the generated…
Read more →A restore test produced a WordPress site with a PHP parse error. The database and the password were fine; the configuration rewrite was not. Cause The rewrite used…
Read more →During resource monitoring on a development server, we noticed an unexpected process running from a site’s files. That raised a broader question: what scans website files for malware?…
Read more →Security Scan reports on its checks but never offered a way to fix them. We added “Fix Now”, but different checks need different treatment, so there are three…
Read more →Earlier restore testing used synthetic archives and one real-world backup used to verify the format. A more realistic restore turned up three problems the earlier testing had not.…
Read more →The Firewall page under Controller → Security was largely a status display with unban buttons. We replaced it with a structured, editable rule table. Because mistakes here can…
Read more →The Reset Password page could generate or set a password, shown once on screen, and never emailed it. We added an option to email the new password, and…
Read more →