Baza wiedzy
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.
Ten artykuł nie został jeszcze przetłumaczony na Twój język, dlatego czytasz wersję angielską.
O czym piszemy w kwestii hostingu, pozycjonowania i prowadzenia stron na dużą skalę.
Jak hosting wpływa na indeksowanie i autorytet linków w 2026 roku: utrzymanie stron w indeksie, weryfikacja leciwych domen przed ich użyciem, pozyskiwanie linków bez pozostawiania śladu oraz szczere spojrzenie na to, co infrastruktura może, a czego nie może zrobić dla SEO.
Przeczytaj post →Praktyczna lista kontrolna dla szybkiego i bezpiecznego WordPress: buforowanie na poziomie serwera, pamięć podręczna obiektu dla każdej witryny, garść wtyczek, które warto uruchomić, utrzymywanie stosu w aktualnym stanie oraz strony WooCommerce, których nigdy nie wolno buforować.
Przeczytaj post →Co tak naprawdę odróżnia dobry hosting zarządzany od taniego konta z panelem sterowania – migracje, kopie zapasowe, izolacja, prawdziwe cachowanie i uczciwa skalowalność – oraz jak to ocenić, zanim podejmiesz decyzję.
Przeczytaj post →Pomoc jest wliczona w każdy plan, dział wsparcia jest czynny przez 24 godzin na dobę i możesz pisać do nas w dowolnym z naszych 58 języków – odpowiadamy w Twoim.
Kontakt z pomocą techniczną → Wszystkie artykuły →