How to ask a good wpfy support question

arnab — Thu, 25 Jun 2026 02:45:59 GMT

A good support question gets answered faster. Use this template when asking for help in Operations & Troubleshooting or any other category. Template What I tried: wpfy site create example.com --wp -le What I expected: A working WordPress site at https://example.com with SSL. What happened instead: SSL preflight failed with "DNS A record does not match public IP". Environment: OS: Ubuntu 24.04 LTS Docker: 27.3.1 (run docker --version) wpfy: run wpfy --version Domain registrar and DNS provider (if relevant) Debug output (redacted): $ wpfy debug [ paste output here, with secrets replaced by ] Redacted .env (if a specific site is involved): DB_NAME=wordpress DB_USER=wp DB_PASSWORD= DB_ROOT_PASSWORD= ... What to redact Before pasting anything, remove or replace: All passwords (database, Redis, SFTP, WordPress admin) All tokens and API keys Private SSH keys ACME account keys or certificate private keys Any line in .env that looks like *_PASSWORD=*, *_TOKEN=*, *_KEY=* Keep hostnames, container names, image tags, and error messages — those are not secrets and they help us diagnose. How to get wpfy debug output $ wpfy debug It audits Docker, Traefik, and every managed site. If the output is long, paste it in a code block (triple backticks). Redact first. One problem per topic If you have two unrelated problems, start two topics. It keeps threads searchable and makes it easier to mark the right answer.

Community Rules & Code of Conduct

arnab — Thu, 25 Jun 2026 02:45:57 GMT

These rules keep the wpfy forum useful, safe, and welcoming for everyone. By posting you agree to follow them. 1. Be respectful Treat everyone with respect. No harassment, personal attacks, hate speech, or discrimination. Disagree about technology; don't attack people. 2. Stay on topic Post in the right category. Keep threads focused. If a discussion drifts, start a new topic and link back. 3. No secrets, ever Never paste secrets into a post. This includes: Database passwords (MariaDB, Redis) API tokens (NodeBB, Let's Encrypt, GitHub, Docker registry) Anything from a site's .env file SSH private keys or host credentials ACME account keys If you need to share config for debugging, redact first. Replace secret values with . The project's security policy applies here too. 4. Search before you post Someone may have already asked. Use the search bar. If you find a related thread, reply there instead of starting a duplicate. 5. Give enough context to help When asking for help, include: What you were trying to do (the exact wpfy command) What you expected What happened instead The output of wpfy debug (redacted) Your OS and Docker version (ubuntu 24.04, docker 27.x, etc.) A redacted .env if the issue involves a specific site See How to ask a good wpfy support question for a template. 6. No spam or self-promotion This is a community for wpfy users. Don't post ads, affiliate links, or unrelated promotions. Sharing a relevant tool or blog post in the context of a real question is fine. 7. Respect the license wpfy is AGPL-3.0. If you share modified source, follow the license terms. Enforcement Moderators may edit, move, lock, or delete posts that break these rules. Repeated or severe violations lead to account suspension. Appeals go in Forum Rules & Meta. Reporting Use the flag button on a post to report rule violations. Don't reply to argue — flag and let moderators handle it.