Error Messages

Find the sentence you were shown, character for character. The wording is what tells the failures apart.

The messages

Messages are quoted exactly as the product emits them, so you can search this page for the sentence itself. Where a message appears as a pop-up notification, the bold text is its heading and the quoted text is the line beneath it.

Share limit reached

Two wordings, one cause. Inside the app you get a notification headed Share Limit Reached with an action button labelled Buy More Shares. From the Slack app or the API you get the server's own sentence, "You have reached limit of your share creation."

The widget on the CredenShare homepage creates its links anonymously and is exempt from the allowance, so it never produces this refusal.

The allowance counts shares created, not shares currently alive:

A paid plan's month is anchored to your renewal day, not to the first of the calendar month: if you renew on the 17th, the count resets on the 17th. Your dashboard shows Shares used against the cap, and warns with a line such as "Only 3 shares remaining" as you approach it.

Two things catch people out:

• Credentials submitted into a secure request count against the request owner, not against the person filling in the form. A widely circulated request form can consume an allowance quickly.
• The API and the dashboard draw on the same pool. There is not one allowance for each.

To buy more, go to Account → Subscription and, under Available Plans, switch the selector to Buy More Shares, which lists the available share packs. Full detail is on Plans and share allowance.

Plan does not include this feature

"Your plan doesn't support this feature, please upgrade to higher plan" comes back when a share is created with a protection option the plan does not carry. In the create dialog those controls are disabled and carry a small Upgrade pill, whose tooltip reads "Not included in your plan — upgrade to unlock", so you normally meet the pill rather than the message.

Require login is not plan-gated and is available on every plan, Free included. Neither is encryption: shares created on the web, through the API or with an SDK are encrypted in your browser on every plan. The zero-knowledge entitlement gates custody — the account passphrase, device linking and key wraps — not encryption itself. See Encryption.

If a plan-gated control looks enabled but the share is still refused, reload the page. The app reads your plan from a copy held for the session, so an upgrade made in another tab is not picked up until the page is loaded again.

Slack is not in your plan

"The Slack integration requires a Plus, Business or Enterprise plan" is a distinct refusal rather than a generic one, precisely so it can be told apart from an outage. It means the account the Slack workspace is connected to is on Free, Solo or Basic.

Nothing was created and nothing was charged. Either upgrade to Plus or above, or create the share in the app and paste the link into Slack yourself. Connecting the app is covered in Slack integration.

We could not confirm your plan

We could not confirm your plan just now. Nothing has changed on your account — please try again in a moment.

The billing provider could not be reached and there was no recent cached answer, so the system does not know what your account is entitled to. It refuses rather than assuming the worst — the alternative would silently treat a paying customer as though they were on Free.

Take the message literally: nothing has changed, no share was created, and no charge was made. Wait a moment and retry. If it persists for more than a few minutes, email support@credenshare.io and say what you were doing.

"This share is no longer available"

This share is no longer available

It may have expired, been deleted, or the link may be incomplete. Check that you opened the full link exactly as you received it, or ask the sender to share it again.

Every link that will not open produces this one card, whatever the reason: the share expired, its view limit was used up, the sender deleted it, the code never existed, or the link arrived incomplete. The identical wording is deliberate — a page that distinguished the causes would tell anyone typing in random codes which codes are real.

The message therefore cannot tell you which applied, and reloading will not reveal it. Only the sender knows. The full walkthrough, in likelihood order, is on Link not working.

Links created with the widget on the CredenShare homepage are destroyed after exactly one view and expire after 24 hours, and neither can be changed. If the sender opened the link to check it worked, that was the view.

"Passcode does not match"

The passcode was wrong. The share is intact and you can try again. The message appears beneath the field in the Password Required dialog.

The passcode is set by the sender and never travels with the link. Ask them for it through a different channel from the one the link arrived in.

Senders can attach a failed attempts tolerance of between 1 and 10, described in the create dialog as "Delete after N wrong attempts". When one is set, the dialog may show a line such as "2 attempts remaining" beneath the error. Do not rely on seeing it — a share can carry an attempt limit without the count being displayed, so treat every wrong entry as expensive.

The sender can see the current figure themselves: it is listed as Attempts Remaining in the share's details panel.

Destroyed by failed attempts

Share Locked

Too many incorrect password attempts. For your security, this share has been permanently destroyed.

The tolerance ran out on that last attempt, and the credential was scrubbed on the same request. This card has no Try Again button, because there is nothing left to try.

If you were the sender, treat the credential as having been the subject of a guessing attempt. Rotate it before sharing it again.

"Captcha verification failed"

Captcha verification failed. Please refresh and try again.

An invisible bot check runs on sign-in, registration, password reset, creating a paste, and opening a share or a secure request. This message means it returned a failing score.

Refresh the page and repeat the action. If it keeps failing:

• Use a normal window rather than a private or incognito one.
• Turn off a VPN or corporate proxy for the attempt, if you can.
• Try a different browser or a different network.

The check is designed to fail open when the script is blocked outright, so an ad blocker usually does not cause this — the page proceeds without the gate instead. A repeated failure normally means the network you are on looks automated.

Login-required shares

Login Required

You need to be logged in to view this share. Please log in to continue.

The sender restricted this share to signed-in CredenShare accounts. Use Log In to Continue; you are returned to the link afterwards. A Free account satisfies the requirement — there is no charge to open a share someone sent you.

If you sign in and are still refused, the sender may have restricted the share further. Two-factor authentication produces its own card, Two-Factor Authentication Required. An IP allow-list produces "You don't have permission to access this share". Ask the sender which account and which network they expected you to use.

Secure requests carry the same gate, worded "You need to be logged in to submit this request."

If your message is not listed

Some text on a share page is written by the sender rather than by us. A Secure Content prompt carries whatever wording they chose; if they left it blank it reads "This content is view-protected. By proceeding, you acknowledge that your access will be logged."

For anything else, email support@credenshare.io and paste the message exactly as it appeared, along with the short code — the part of the link before the #, never the part after it. What else to include is on Help and support.

Developers looking for integer error_code values, the error envelope, HTTP statuses and rate limits should read Errors and rate limits instead; this page does not repeat them.