caddy-proxy-manager
Self-hosted reverse proxy built on Caddy: proxy hosts, automatic HTTPS, TCP/UDP streams and traffic analytics, with an optional per-host WAF, sign-in and access rules.
Runssource: GitHubhomepageTypeScriptNOASSERTIONcommit 927144e6c5b1
TypeScript, NOASSERTION licensed. The project labels itself: caddy, geoblock, http, mtls, proxy, quic, reverse proxy and tcp.
caddy-proxy-manager runs. An Argusic agent installed it in 23 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Next.js 16.4.3 production server responds on port 3000: login page returns HTTP 200, unauthenticated routes redirect to /login, and API endpoints return HTTP 401 as expected without a session cookie.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- @tailwindcss/oxide native optional dependency not resolved by npm (common npm optional-deps issue)3 minutes
- Node.js v18 is too old for vitest 5.x / rolldown 1.x (needs node:util.styleText)2 minutes
- maplibre-worker-staging test failed: maplibre-gl v6.16.0 inlines all worker chunks into one file, test asserted deps contained 'maplibre-gl-shared.mjs'2 minutes
- Install time
- 23 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- vitest run --config tests/vitest.config.ts: 144 files passed, 2118 tests passed; next build: completed with BUILD_ID=Y3meTvGztObQJ3Unb6wEf; curl http://localhost:3000/login returned 200 with login page HTML; curl http://localhost:3000/ returned 307 redirect to /login; curl http://localhost:3000/api/v1/settings/general returned 401 Unauthorized
- Model tokens used
- 323,712
- Exact commit tested
- 927144e6c5b1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: === Versions === v22.14.0 === OS === PRETTY_NAME="Ubuntu 24.04.4 LTS" NAME="Ubuntu" VERSION_ID="24.04" Here's the final report. 2026-10-29T02:12:00.276650Z ERROR codex_core::session: failed to record rollout items: thread 01a18… tokens used 323,712 Here's the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
What did not, or is not known
- Took 23 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Its license file could not be classified automatically, so check it yourself before using it.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 caddy projects Argusic has installed and timed, caddy-proxy-manager was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/caddy-proxy-manager)Questions
- Does caddy-proxy-manager run?
- Yes. caddy-proxy-manager runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test caddy-proxy-manager?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 927144e6c5b1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test caddy-proxy-manager?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does caddy-proxy-manager take to install?
- 23 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does caddy-proxy-manager need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing caddy-proxy-manager?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does caddy-proxy-manager compare with the alternatives?
- Of the 4 caddy projects Argusic has installed and timed, caddy-proxy-manager was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for caddy-proxy-manager?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.