FAQ
Common questions grouped by topic, each with self-help steps. For full walkthroughs see the tutorials: Cloud Hosting · Self-hosted · SSL.
General
Section titled “General”Do I need my own server?
Section titled “Do I need my own server?”Not necessarily. GOCO Cloud Hosting needs no server of your own — buy a plan and build. The self-hosted route needs a VPS / cloud server with the BaoTa panel; the platform connects over SSH to build and deploy.
Will it change my server config?
Section titled “Will it change my server config?”A build deploy only writes the generated site files into the site directory (webroot); it doesn’t touch your nginx vhost — which is why you create the site in BaoTa first. Two other places do reach the panel / SSH, both as rollback-safe, self-contained snippets that leave your own config alone: SSL deployment / renewal writes the certificate into the matching site and reloads nginx; and onboarding a server writes an SSH keep-alive config (sshd_config.d/99-goco.conf) and reloads sshd.
Is the content AI-generated? Will it be duplicated?
Section titled “Is the content AI-generated? Will it be duplicated?”Yes, AI-generated — and each site’s content, brand and URL structure are differentiated to avoid site-farm fingerprints and duplicate content.
Do I need to bring my own AI API key?
Section titled “Do I need to bring my own AI API key?”Either way works.
- Use the platform’s goco-AI: the 500 USDT self-hosted license is authorization only and keeps the platform model locked. Unlocking it costs a one-time 300 USDT AI add-on, which itself includes 300 build credits (one-time, never expiring); extra credits are $1 each afterwards. Managed hosting’s Starter tier ships 50 credits at purchase, and Standard and above can add an AI pack.
- Bring your own key (BYOK): enter your own API key in Step 2 of the batch wizard — never locked, never consumes platform credits.
If quota is temporarily unavailable it falls back to publishing the original, so nothing stalls.
Which languages are supported?
Section titled “Which languages are supported?”Two layers: the console UI is available in 12 languages (Chinese, English, plus Indonesian, Malay, Filipino, Vietnamese, Thai, Burmese, Khmer, Lao, Japanese and Korean); site content generation supports 8 languages (Simplified Chinese, Traditional Chinese, English, Japanese, Korean, French, German, Spanish) — pick the primary / secondary language in Step 2 of the batch wizard.
Builds failing / stuck
Section titled “Builds failing / stuck”My batch is stuck in Draft — what now?
Section titled “My batch is stuck in Draft — what now?”After submitting, a batch normally moves to Pending → Running. Stuck in Draft at 0 progress usually means the jobs never reached the build queue: open the batch detail and, when you see the hint that rows were written but jobs never reached the queue, click Retry to enqueue them again. If submission reported a queueing failure, the system auto-retries within minutes — no need to resubmit. Still stuck? Confirm the chosen server’s status is normal (servers in maintenance / offline take no builds).
Sites sit in Queued or Building for a long time?
Section titled “Sites sit in Queued or Building for a long time?”Open the Build throughput panel on the batch detail: if “your server” is idle but sites still queue, the wait is in the system pool shared by all users — just wait. If your server accepts jobs slowly, run the one-click SSH optimization on the Servers page. Large batches build site by site; some waiting is normal.
Batch shows Partial — how do I retry the failed sites?
Section titled “Batch shows Partial — how do I retry the failed sites?”Click Rebuild failed sites on the batch detail and pick a mode: keep the original template and rerun, assign fresh random templates from the batch’s original pool, or use one fixed template for all. If the rebuild request fails to reach the worker, try again shortly.
It says all rows failed and the empty batch was removed?
Section titled “It says all rows failed and the empty batch was removed?”The whole batch failed creation validation (typically malformed domains or a failed server check). Fix the errors listed at submit time and submit again — the empty batch was auto-deleted and used no quota.
I hit “Free build quota used up” or “Build credits exhausted” — what now?
Section titled “I hit “Free build quota used up” or “Build credits exhausted” — what now?”The first means your account’s free build quota is gone — buy a license or build credits to continue. The second means the server’s remaining build credits don’t cover the batch — top up goco build credits ($1/credit), or switch to your own API key in Step 2 (uses no platform credits).
Do failed builds still cost me build credits?
Section titled “Do failed builds still cost me build credits?”No. A site that fails to build automatically returns the build credit it consumed — no support ticket needed. The refund only reduces the used count; it never touches your total.
It says “Out of goco Hosting capacity”?
Section titled “It says “Out of goco Hosting capacity”?”Your Cloud Hosting plan’s site quota is used up. Buy more goco Hosting capacity (or upgrade the plan) on the Servers page, then create sites.
It reports duplicate domains in the batch?
Section titled “It reports duplicate domains in the batch?”A batch cannot contain the same domain twice. You’re returned to Step 1 with the duplicates listed — remove the duplicate rows and resubmit.
DNS not resolving
Section titled “DNS not resolving”Which DNS records does a hosted domain need?
Section titled “Which DNS records does a hosted domain need?”Three per domain (view and copy them under Domains needing DNS setup on the site detail): 1) Routing CNAME: @ (and optionally www) → the record value shown in the console (e.g. tw1.goco.cc per shard, possibly in a goco-host.com form) — the site only opens once this exists; 2) Certificate CNAME: _acme-challenge → the target shown, for automatic HTTPS issuance; 3) Ownership TXT: _cf-custom-hostname → the verification value, proving the domain is yours.
Records are added but the status is still “Awaiting DNS”?
Section titled “Records are added but the status is still “Awaiting DNS”?”Work through this checklist: the records are at the DNS provider the domain actually uses (wherever its nameservers point); the Host field uses the relative form (@ / www / _acme-challenge) — don’t append the domain again; values match the hints exactly, with no trailing dots or spaces. Then click Check status next to the domain.
How long does DNS take to propagate?
Section titled “How long does DNS take to propagate?”Usually minutes to a few hours; after an NS change or with long TTLs it can take up to 24–48 hours. Once live, the status moves from “Awaiting DNS” → “Issuing certificate” → “Active” on its own — no repeated action needed.
My domain is on Cloudflare and still won’t open?
Section titled “My domain is on Cloudflare and still won’t open?”Set the “Routing” CNAME to “DNS only” (grey cloud). An orange-cloud proxy double-proxies the traffic, and both resolution and certificate issuance fail — the single most common cause of a stuck domain.
My root domain can’t take a CNAME — what now?
Section titled “My root domain can’t take a CNAME — what now?”If your DNS provider supports CNAME flattening, use the CNAME as shown; otherwise use the A record (fallback) from the records list instead (one or the other). Alternatively enable NS full-managed: point the domain’s nameservers at goco and every record is created automatically.
The ownership TXT shows as not fetched — does it matter?
Section titled “The ownership TXT shows as not fetched — does it matter?”If the site already shows “Active”, ownership was verified long ago and no record is needed — ignore it. Only when the site stays inactive with the routing / certificate records in place should you click “Retry” to re-read it.
It says the domain is already in use by another account?
Section titled “It says the domain is already in use by another account?”Go to Sites → Bind a domain and click Start transfer on the domain. Pass proof of control (your own active Cloudflare zone / goco NS-hosting / publishing the shown DNS TXT — any one) to take it over, then resolve DNS as usual.
I have many domains — how do I resolve them in bulk?
Section titled “I have many domains — how do I resolve them in bulk?”Use Mode 5 · Hosting on the console’s CF page: paste domains (one per line) or click “Fill my pending domains”, then click Read records to generate every domain’s full record set. Submit in one click (when the domains live in your linked Cloudflare account) or “Copy all records” to add at your DNS provider.
SSL not issuing / renewal failing
Section titled “SSL not issuing / renewal failing”Do hosted sites need a manual SSL request?
Section titled “Do hosted sites need a manual SSL request?”No. The certificate issues automatically once DNS resolves, and renews automatically before expiry. The _acme-challenge certificate CNAME is a one-time delegation — keep it after issuance; renewal depends on it and deleting it leads to a certificate error.
The status is stuck on “Issuing certificate”?
Section titled “The status is stuck on “Issuing certificate”?”Routing works but validation hasn’t passed: check the _acme-challenge CNAME exists and its value matches the hint exactly; on Cloudflare this record must also stay grey-cloud. Then click Check status — it normally flips to “Active” within minutes.
The SSL column shows “Cert error”?
Section titled “The SSL column shows “Cert error”?”Usually a DNS record was deleted, so the certificate failed to issue or renew. Open Domains needing DNS setup on the site detail, verify all three records are present, and restore any missing ones — recovery is automatic, no manual re-issue needed.
How do I issue certificates on my own server?
Section titled “How do I issue certificates on my own server?”On the console’s SSL page, click New certificate: pick the server and a CA (Let’s Encrypt / ZeroSSL / BuyPass — all free), cover “all domains on this server”, and enable auto-renewal. Full steps in the SSL tutorial.
Certificate renewal fails on my own server — what now?
Section titled “Certificate renewal fails on my own server — what now?”Open the config and read Last error: HTTP-01 (webroot) validation needs port 80 reachable; if it says the domain doesn’t resolve to this server’s IP, fix DNS first; or switch to DNS-01 (CloudFlare token) validation. Then click Retry renewal — still-valid certificates are skipped automatically, and avoid force re-issue (it burns CA quota).
Publishing not showing up / billing
Section titled “Publishing not showing up / billing”Publishing reports success but articles aren’t on the site?
Section titled “Publishing reports success but articles aren’t on the site?”Articles auto-deploy after publishing, going live in about 1 minute. If it’s past the normal go-live time, click Refresh to re-check; if still not live, use Retry on the affected site to re-publish. Browser cache can also show a stale page — hard-refresh and look again.
“Run now” published nothing?
Section titled ““Run now” published nothing?”If you see “Daily cap reached — nothing published”, the schedule already hit today’s per-day cap and the manual run produced no articles; to continue anyway choose Override cap in the confirmation dialog (not recommended — it may signal low-effort content to search engines). Also note a schedule that’s Off won’t auto-run, but “Run now” still fires it once.
Why are some sites skipped when publishing?
Section titled “Why are some sites skipped when publishing?”Sites whose template lacks news list + detail pages can’t publish articles and are silently skipped at runtime (they appear under “Skipped sites” in the run detail). Switch those sites to a template with news pages and publishing resumes.
How do I retry failed articles in bulk?
Section titled “How do I retry failed articles in bulk?”Click Retry on the run detail: failed articles are reset and re-deployed. Up to 500 are reset per click — if many failed, click again to continue. A site whose AI polish fails falls back to publishing the original text; that’s by design, not a fault.
How is it priced?
Section titled “How is it priced?”Self-hosted servers use per-server licensing: 500 USDT per server (authorization only — the platform model stays locked) plus an annual platform fee. To use the platform’s AI, add the one-time 300 USDT AI add-on (300 build credits included), or bring your own key (BYOK), which consumes no credits. Every account also gets 10 shared free build credits to try things out.
Cloud Hosting is sold as plans with site quotas, renewed periodically; the Starter tier is exempt from the annual platform fee, Standard and above are charged (higher on the XL tiers). Optional add-ons: the goco-AI pack (platform model credits) and pay-as-you-go build credits ($1/credit).
Everything is charged from the prepaid wallet, topped up with USDT. See the console’s Servers page for exact pricing.
It says my wallet balance is insufficient?
Section titled “It says my wallet balance is insufficient?”Open the Prepaid wallet and click “Top up” (whole USDT amounts; the credited amount equals what you pay, in full). During a purchase you can also pay just the shortfall online — the purchase completes automatically once funds arrive. If provisioning fails, the charge is refunded to the wallet.
Can Cloud Hosting be refunded? How do I stop auto-renewal?
Section titled “Can Cloud Hosting be refunded? How do I stop auto-renewal?”A hosting plan can be refunded to your wallet while it has never used goco-AI, never bound any site, and is within 7 days of purchase — use “Request refund” on the plan detail. Auto-renewal is toggled on the plan detail too: on, it renews from your wallet at expiry so sites never go dark; off, service stops at expiry.