VK Token Stopped Working — How to Reconnect
VK occasionally revokes access granted to apps — usually after a password change or signing out of all devices. It's not a malfunction: sign in again and publishing resumes. Communities and project settings are preserved.
How to set up
Open the 'VK' section in the app
Launch the Crosslybot app (button in the @crosslybot bot, or the web version) and go to the 'VK' section. If access was revoked, you'll see a red 'VK revoked access' notice with a reconnect button.
Tap 'Connect VK account'
A page with instructions and an 'Authorize via VK' button opens. Important: sign in to the same VK account that was connected before and administers your communities. Do not disconnect or delete the current connection.
Authorize on VKontakte
Tap the authorization button — the VK sign-in page opens. After signing in, VK redirects you to a blank white page. That's expected.
Copy the page address and paste it into the field
Copy the full address of the blank page from the browser address bar (a long link containing access_token) and paste it into the field on the instruction page. Don't take long pauses — the connection session lives 10 minutes; if it expires, just start over.
Done — publishing resumes automatically
Access refreshes on the existing connection: communities stay connected, project settings don't change, nothing needs to be set up again. The next post from your source publishes to VK as usual.
Features
Why did VK revoke access?
Most often — after a VK password change, signing out of all devices ('end all sessions'), or an automatic VK security check. Sometimes VK revokes app access as part of routine sweeps. Nothing is broken on your side — or ours. That's how VK security works.
No need to disconnect communities
A common mistake is deleting the connection or recreating the project. It doesn't help: the problem is not in the settings but in the revoked access. Just authorize again — the token refreshes on the existing connection, everything else is preserved.
Posts missed during the outage are not lost forever
Posts that didn't reach VK while access was revoked are not re-sent automatically. If you want them published — after reconnecting, contact support (in the app: Support → Contact us), and we will queue them for re-publishing.
Publishing to other platforms doesn't stop
A revoked VK access affects only VK publishing. Posts to Telegram and Max keep going out on schedule — the project works, only the VK target is paused until you reconnect.
FAQ
Will project settings disappear after reconnecting?
No. Re-authorization only refreshes the access (token) on the existing connection. Communities, projects, signatures, filters and all settings stay as they were.
Should I disconnect the VK account first and reconnect?
No, and better not to: disconnecting deactivates connected communities and project targets, and you'd have to set them up again. Just tap 'Connect VK account' and authorize — access refreshes by itself.
I didn't change anything — why was access revoked?
VK can revoke app access automatically: during security checks, suspected sign-ins from a new location, or routine sweeps. This happens on VK's side and doesn't depend on Crosslybot.
How do I re-send posts that didn't reach VK during the outage?
They are not re-sent automatically. After reconnecting, contact support (in the app: Support → Contact us) — we will queue the missed posts for re-publishing, it usually takes a few minutes.
How do I know everything works again?
The red notice in the 'VK' section disappears right after successful authorization, and the next post from your source publishes to VK. You can also check manually: publish a test post in the source channel.
What if my community is not in the list during authorization?
The list shows only communities where your VK account is an administrator. Check that you signed in to the right VK account and that it has admin rights in the community. You can also connect a personal page instead of a community.
The connection session expired — what should I do?
The authorization link lives 10 minutes. If you didn't make it — no problem: return to the 'VK' section and tap 'Connect VK account' again, the process starts over.
Why VK access disappeared
VK grants apps access (a token) tied to your VK account session. When you change your VK password, tap “end all sessions”, or VK runs a security check, all granted accesses are invalidated — including Crosslybot’s. This is VK security working as designed, not a malfunction.
What it looks like: VK publishing stops, you get a “VK token invalid” notification, and a red notice appears in the app’s “VK” section. Posts to Telegram and Max keep going out.
Quick fix
- Crosslybot app → “VK” section
- “Connect VK account” button (no need to disconnect anything!)
- Sign in to the same VK account that was connected
- Copy the full address of the blank page and paste it into the field, following the on-screen instructions
Done: access refreshes on the existing connection, communities and project settings are preserved, publishing resumes automatically.
Re-sending posts missed during the outage
While access was revoked, posts from the source were not published to VK. They are not re-sent automatically — to get them published:
- First reconnect VK (steps above)
- Contact support — in the app: Support → Contact us
- We will queue the missed posts for re-publishing — it usually takes a few minutes
Ready to try?
Connect the bot in 2 minutes. Free plan — no cards, no signup.
