About Bobay Stack
Bobay Stack is my own run log. Everything written here meets one common standard: it actually ran on a machine, and it actually broke.
What I write about
- Virtualization and containers: configuring and troubleshooting PVE, LXC, QEMU
- Networking and proxies: soft routers, forwarding performance, protocol compatibility
- Operations: certificates, backups, restore drills, change ordering
- Security boundaries: credential management, login methods, minimal exposure
What I don't write is just as clear: no benchmark comparisons, no "top ten tools" lists, no tutorials that trail off with no follow-up.
Why I write
Two years ago I started keeping a note of every troubleshooting session, at first just so I wouldn't step in the same hole twice. Later I found these records had an extra value: they capture why I judged it that way at the time, and that part usually isn't in the official docs.
So the article structure here is basically fixed: symptom → troubleshooting order → root cause → fix → recheck list. If there's no conclusion, I don't publish it.
On accuracy
Every version number, command and figure is dated. Software changes, commands stop working, prices change. Check any conclusion you read against the version at the time; don't treat it as permanent fact.
If you find a post that's gone stale, please point it out — corrections matter more than new posts.
Attribution
All articles are signed with the site domain bobay.top; no personal name is published.
Contact
This site is run and maintained independently under the bobay.top domain: topic selection, writing, deployment and operations are all done by one person. Bobay Stack (波贝自建栈) is not a media organization and has no editorial team.
- Email: [email protected] (signed with the domain, no personal name published)
- Use it for: content corrections, factual additions, dead-link reports, privacy and removal requests
- Response: usually within 3 business days; it's one person handling it, so please bear with me when it's slow
If you find something in an article that doesn't match what you measured, please say so directly — corrections matter more than new posts.
All reader mail goes to [email protected], and I usually reply within one business week. If your message is about troubleshooting in production, include the system version, the exact error text and the steps you've already tried — with those three, the reply has a chance of being useful.
Scope
This site doesn't cover three kinds of things: configs that haven't run on real hardware, "one-click script" wrappers, and upgrade tutorials that skip backups and rollback. If I can't write it properly, I'd rather not write it.