Base ng Kaalaman
Create a CDN77 API token in the Client Panel and connect it, so a site can run on your own CDN77 account with purge and settings managed from your dashboard.
Connecting your own CDN77 account lets you put a site on your CDN instead of ours. The zone, the traffic and the bill are on your account, and you can still purge the cache and change the CDN's settings from inside your Zinn® dashboard — no switching between panels.
A CDN77 account.
In the CDN77 Client Panel open Account Settings and the API Token section, and create a token there. Store it somewhere safe before leaving the page.
Open Integrations in your dashboard and choose Connect an account. Pick Your own CDN as the group and CDN77 as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
appears as a destination. Choose it and confirm; we build the site's configuration on your account, check it, and only then move the site across, so the site stays up during the move.
account.
detail, purge the cache, change settings and — where the vendor has them — geographic rules. The checklist beside the connection shows which of those we could confirm, so a missing permission is visible before you move a site onto the account.
It was rejected. Check you copied the API token, not your Client Panel password, and that the token has not been deleted in Account Settings → API Token.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
Hindi pa naisalin ang artikulong ito sa iyong wika, kaya binabasa mo ang bersyong Ingles.
Ang aming isinulat tungkol sa hosting, SEO at pagpapatakbo ng mga site sa malaking saklaw.
Kung paano hinuhubog ng hosting ang indexing at link equity sa 2026: pagpapanatiling naka-index sa mga pahina, pagsusuri sa mga lumang domain bago ka magtayo sa mga ito, pagbuo ng link nang walang bakas, at tapat na pagsusuri sa kung ano ang kaya at hindi kaya ng imprastraktura para sa SEO.
Basahin ang post →Isang praktikal na checklist para sa mabilis at ligtas na WordPress: server-level caching, per-site object cache, ilang piling plugins na sulit patakbuhin, pagpapanatiling napapanahon sa stack, at ang mga pahina ng WooCommerce na hindi mo dapat i-cache kailanman.
Basahin ang post →Ano ba talaga ang nagpisa sa mahusay na managed hosting mula sa murang box na may control panel — mga migration, backup, isolation, tunay na caching at tapat na scaling — at kung paano ito husgahan bago ka pumirma.
Basahin ang post →Kasama ang suporta sa bawat plan, bukas ang desk 24 oras bawat araw, at maaari kang sumulat sa amin sa alinman sa aming 58 na mga wika — sasagutin ka namin sa iyong wika.
Makipag-ugnayan sa suporta → Lahat ng artikulo →