docs(cloudways): warn against using network wildcard in WU_CLOUDWAYS_EXTRA_DOMAINS

[superdav42]

Summary

Updates the public Cloudways integration doc to warn against putting your own
network's subdomain wildcard (e.g. *.your-network.com) into
WU_CLOUDWAYS_EXTRA_DOMAINS — a step the previous wording suggested by
listing "Wildcard domains (e.g. *.example.com)" as a use case for that
constant.

Combined with a manually-installed Cloudways wildcard SSL certificate, that
configuration prevents Cloudways from issuing Let's Encrypt certificates for
per-tenant custom domains, leaving them without SSL.

Reported by a real user in
Ultimate-Multisite/ultimate-multisite#1141 — the docs change here matches the
companion PR against the plugin's in-product wizard.

Changes

docs/user-guide/host-integrations/cloudways.md:

• Drop *.wildcard.com from the wp-config example. Add a :::warning
  admonition that forward-links to the new pitfall section.
• Reframe Extra Domains as for external (non-network) domains only —
  remove the "Wildcard domains" bullet that suggested putting
  *.example.com here, replace it with parked/marketing/staging examples,
  and end with an explicit "Do not use this constant for your own
  network's subdomain wildcard" note.
• New top-level Important — Wildcard SSL Pitfall section with the
  recommended Cloudways SSL setup (standard Let's Encrypt cert on the
  network domain, DNS-only wildcard for tenant subdomains).
• Under SSL Certificate Management, note that the integration always
  requests standard (non-wildcard) Let's Encrypt certs and strips the
  leading *. from any wildcard supplied in WU_CLOUDWAYS_EXTRA_DOMAINS
  before the SSL request.
• New troubleshooting bullet under SSL Certificate Issues for
  per-tenant custom domains stuck without SSL when a wildcard cert is
  active on the Cloudways application.

The 40+ i18n/<lang>/.../cloudways.md translation copies are not
hand-edited here — they regenerate from this English source via the repo's
translate.sh workflow.

Companion PR

Equivalent changes to the in-plugin setup wizard:
Ultimate-Multisite/ultimate-multisite#PENDING (linked once opened)

Refs

Ref Ultimate-Multisite/ultimate-multisite#1141

---

aidevops.sh v3.14.92 plugin for OpenCode v1.14.40 with gemma4:e4b spent 15h 37m and 263,673 tokens on this with the user in an interactive session.

[coderabbitai]

Warning

Rate limit exceeded

@superdav42 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 30 minutes and 7 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c211059d-5ce0-446b-8fe0-226833425fed

📥 Commits

Reviewing files that changed from the base of the PR and between 837f0c9 and 81e5642.

📒 Files selected for processing (1)

• docs/user-guide/host-integrations/cloudways.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/cloudways-wildcard-ssl-pitfall-um-1141

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}