Msingi wa maarifa
Copy your Bunny account API key and connect it, so a site can run on your own Bunny CDN with purge and settings managed from your dashboard.
Connecting your own Bunny 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 bunny.net account. Bunny's account API key has full access to the account, so treat it like a password.
In the bunny.net dashboard open Account → API Key. The key is hidden by default: press the eye icon to reveal it, or the copy icon to copy it.
Use the account API key. A storage zone's password or a video library's key is a different credential and is refused here.
Open Integrations in your dashboard and choose Connect an account. Pick Your own CDN as the group and Bunny CDN as the account, fill in Access key (your account API key), 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 stopped working. The key was regenerated in Bunny, which disables the old one at once. Copy the new key and connect it.
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.
Makala hii bado haijatafsiriwa katika lugha yako, kwa hivyo unasoma toleo la Kiingereza.
Mambo ambayo tumekuwa tukiandika kuyahusu upangishaji, SEO na kuendesha tovuti kwa kiwango kikubwa.
Jinsi hosting inavyoathiri uwekaji faharasa na usawa wa viungo mwaka 2026: kuweka kurasa kwenye faharasa, kukagua vikoa vya zamani kabla ya kuvijenga, ujenzi wa viungo bila alama, na mtazamo wa ukweli kuhusu kile ambacho miundombinu inaweza na haiwezi kufanya kwa ajili ya SEO.
Soma chapisho →Orodha ya vitendo vya kuaminika kwa ajili ya WordPress ya haraka na salama: kache ya kiwango cha seva, kache ya vitu kwa kila tovuti, idadi ndogo ya programu-jalizi zinazofaa kutumika, kuweka mfumo wa sasa, na kurasa za WooCommerce ambazo hupaswi kuzifanyia kache kamwe.
Soma chapisho →Kile kinachotofautisha mwenyeji unaosimamiwa vizuri na seva ya bei rahisi yenye paneli ya udhibiti — wahamiaji, nakala rudufu, utengaji, akiba halisi na upanuzi wa kweli — na jinsi ya kukitathmini kabla ya kujitolea.
Soma chapisho →Usaidizi umejumuishwa kwenye kila mpango, huduma ya msaada iko wazi saa 24 kwa siku, na unaweza kutuandikia kwa lugha yoyote kati ya lugha zetu 58 — tunakujibu kwa lugha yako.
Wasiliana na usaidizi → Makala zote →