Skip to content

Troubleshooting

Sayrox edited this page Jul 20, 2026 · 1 revision

Troubleshooting

"Failed to check" on update check

This means the GitHub API request to check for updates failed. Possible causes:

  • The repository is not yet public or has no releases
  • Network issues or firewall blocking GitHub API requests
  • GitHub API rate limiting (rare)

The plugin still works fine — this only affects the update checker.

Clone stops mid-progress or freezes

This is usually caused by Discord's rate limits. Clonecord handles rate limits automatically and will resume, but if you see repeated 429 errors:

  1. Wait a few minutes before trying again
  2. Try cloning fewer items at a time
  3. Use Resume mode to continue where it left off

You can always cancel using the button in the progress notification.

"Clone Server" option doesn't appear

Make sure:

  1. Clonecord is enabled in Settings > Vencord > Plugins
  2. You are right-clicking a server name or icon (not a channel or user)
  3. You have the latest version of Vencord

Onboarding not cloned

Onboarding requires both Channels and Roles to be enabled in the clone modal. If either is unchecked, onboarding will be disabled automatically.

Stickers or sounds missing after clone

Check the target server's boost level. Sticker and soundboard slots are limited by Discord:

  • Level 0: 5 stickers, 8 sounds
  • Level 1: 15 stickers, 24 sounds
  • Level 2: 30 stickers, 36 sounds
  • Level 3: 60 stickers, 48 sounds

Items exceeding the limit are skipped.

Error: "You do not have permission"

You can only clone into servers you own. If you selected an existing server you don't own as the target, the clone will fail. Choose "Create New Server" instead, or select a server you own.

Clone created duplicate channels in Resume mode

This shouldn't happen — Resume mode checks for existing items. If it does happen, it may be a bug. Please report it.

Clone this wiki locally