Skip to content
Dashboard
Browse & search guides
All guides

Troubleshooting

Find the cause of missing deliveries, payment issues or unavailable actions.

The server has not contacted the store0% read

The server has not contacted the store

  • Confirm the Craftly jar is installed on Paper 1.16.5 or newer with Java 11 or newer and the server is running.
  • Check that your Minecraft host can reach https://craftly.one over HTTPS. The plugin connects to Craftly automatically; no site URL is needed.
  • Check secret matches your store’s current plugin key. After changing it, run /craftly reload and /craftly check.
  • Read the game server console for connection or authentication errors. The connection indicator tracks plugin requests, not player-count pings.

A paid order is still queued

  • Check Game server for recent contact and use the current Paper plugin.
  • Make sure the username and Java/Bedrock choice are correct. Join with that account if an action needs the player online.
  • Check the command syntax and that its Minecraft plugin is installed. Try a test payment with your own name.
  • Player commands need that player’s permissions. Review whether the action should run as console instead.
  • Keep the plugin’s checkpoint files. Do not mark delivered or retry blindly; confirm what already ran first.

A payment is pending or a provider is missing

  • A provider appears only when enabled. Confirm its credentials and save the settings.
  • Check that all PayPal credentials belong to the selected sandbox or live environment, or that your Stripe key matches the intended mode.
  • Verify the webhook URL is publicly reachable over HTTPS, the required events are subscribed, and the signing secret or webhook ID matches.
  • Check the provider dashboard for payment status and webhook delivery errors. A browser success redirect alone does not confirm payment.
  • If Craftly reports that payment setup is unavailable, contact the Craftly operator; this is a platform configuration issue.

An extension action is unavailable

Enable its extension in Extensions. For uploaded files, review and import the definition before enabling it. Replacing an extension disables it until you enable it again.

If validation fails, use the matching field type and declared options. Keep permission and group fields to one argument. Use a duration such as 30d. The file preview reports invalid definitions before import. Existing paid delivery snapshots are preserved even while an extension is disabled.

A package, sale or template is not showing

Make the package active and check its category. For sales, check the selected category, percentage and deadline. Zero disables the campaign discount. A larger package discount takes priority.

A template preview is visible only to the owner. Apply it to change the public shop, and check that your plan includes it. After a downgrade, unavailable templates fall back to Classic.