This site is the public edition: reference pages that anyone can read. The on-premises edition is the same product running on a server inside your organization, with the parts that need your data and your people: a place to record what your team tried on your computers, and to prove that a fix worked here before anyone relies on it. Nothing you enter leaves your network.

What it adds

How the team uses it

Case log. After a fix attempt, a technician records the code, the computer, what was tried and the result (fixed, partly, did not fix, or a note). They can attach screenshots and paste a log excerpt. Pasted text is refused if it looks like it holds a password or key. The log shows every case, every computer, and the codes that keep coming back on the same computer.

Verify fixes. Imported fixes start as untested. A fix becomes "verified here" when someone records that it worked on a real computer, and "failed here" when it did not. The queue shows which fixes are waiting, so the team tests the ones that matter first.

Your own content. Your team can add a code, a fix or a script that is specific to your environment. Each script carries its risk, whether it needs administrator rights or a restart, and how to undo it. Technicians read and copy scripts; nothing runs from the site.

ConfigMgr scripts. Ten scripts for the PSScripts menu of Client Center for Configuration Manager, downloadable one at a time or as one package. Each returns one result block, starts long repairs in the background and writes a log on the computer. The page lists each script's test status, so you can see which ones were tested on a real computer and which were not.

Security and your data

• People sign in through a reverse proxy you already run (any proxy that can pass a verified user name). The app has no password screen of its own, listens only on the server itself, and (with the shared-secret setting the deployment guide requires) refuses any request that does not carry a secret from your proxy.
• Four database accounts with separate rights. The account the web application uses to write can add rows and cannot delete or rewrite content or the case log. The account that edits content is never used by the web application.
• Roles are built: reader, contributor, verifier and administrator, mapped from your group names. They are off by default, and with the setting off every signed-in person is an administrator, which suits a proxy that already limits access to one group. Turn them on before you open the site to more than one team.
• Per-person limits on changes per hour and on screenshot storage. Uploads accept PNG and JPEG only, checked by content, with location and camera data removed.
• Everything typed is escaped, raw HTML is never drawn, and writes from another site are refused. The server makes no outbound calls.

What you need to run it

One Linux server with PostgreSQL 16, nginx and Python. The reference installation runs on Ubuntu 24.04 with 2 virtual CPUs, 4 GB of memory and a 61 GB disk, of which 5 GB is used, and its database is under 100 MB. The package includes the database scripts, the service unit, an example nginx configuration, a nightly database dump that keeps 14 days, and a step-by-step deployment guide. Updating means copying the new files, applying any new database script and restarting the service.

Limits today

• One server. There is no cluster or failover; the nightly dump and a restore are the recovery path.
• English only, and Windows error codes only.
• No fleet view yet. The Error Code Export script collects the codes a computer has hit into a file you can open in a spreadsheet or in the Log Parser, but importing that file into the case log or a per-computer view is not built.
• Editing or deleting an entry from the page is not built; changes to content go through the database.
• Scripts are not code-signed yet, so an AllSigned execution policy will refuse them.

Not decided yet

Price, license terms, whether there is a trial, and which reference content ships in an on-premises copy are not settled, so this page makes no promise about them. To ask about availability, use the contact page at owenperrycyber.com/contact.