Troubleshoot package decryption
Help a sender or recipient understand package-opening problems without sharing passphrases or package contents.
Outcome
You can narrow a package-opening issue to link, passphrase, browser, expiry, or permission context without exposing secrets.
Your progress
Mark each step as you complete it. This is saved only in this browser.
0 / 3 steps complete
Before you start
Visual frame
Review asset
Package decryption troubleshooting storyboard
Synthetic package frame only. It never asks users to paste passphrases, package contents, or private files into support.
Synthetic frame
Package link
Confirm the route before troubleshooting.
Troubleshoot package decryption workflow frame
Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.
Guided steps
Follow the task, then check the result.
Check the package link
Confirm the link is complete, current, and received through the expected channel.
Check the passphrase without sharing it
Retype or paste the passphrase locally. If it fails, ask the sender to confirm through a separate trusted channel.
Check browser and package state
Try a supported browser, check whether the package expired, and note the visible error category.
Branch questions
Can you see the package opening surface described in this guide?
Did the result match the completion check?
Completion check
Support boundary
Support can use by default
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Intent ID
- Article slug
- App route
Requires your consent
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user
Not collected by default
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
Safe support summary
Copy a scrubbed handoff.
Redactorr KB support summary Article: /knowledge-base/package-decryption-troubleshooting Selected issue: A valid package still will not open in a supported browser. Playbook progress: 0/3 steps marked complete Safe context to include: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-redacted sample only after review. - Intent ID - Article slug - App route Requires explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture User note: - Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.
Article details
Troubleshoot package decryption
Help a sender or recipient understand package-opening problems without sharing passphrases or package contents.
Use this guide when the package opening surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.
Outcome
You can narrow a package-opening issue to link, passphrase, browser, expiry, or permission context without exposing secrets.
Before You Start
- Do not paste passphrases into support.
- Confirm you are using the intended package link.
- Ask the sender for a fresh package only through a trusted channel.
1. Check the package link
Confirm the link is complete, current, and received through the expected channel.
Check before you continue: You are opening the intended package link.
2. Check the passphrase without sharing it
Retype or paste the passphrase locally. If it fails, ask the sender to confirm through a separate trusted channel.
Check before you continue: The passphrase has been checked without sending it to support.
3. Check browser and package state
Try a supported browser, check whether the package expired, and note the visible error category.
Check before you continue: You know whether the issue is link, passphrase, expiry, browser, or unknown.
Completion Check
- No package contents or passphrases were sent to support.
- Link, passphrase, expiry, and browser state were checked.
- The sender is contacted through a trusted channel if regeneration is needed.
Safe Examples
- A masked package link showing only the domain and route.
- An error category without the passphrase.
If You Need Support
Contact support when:
- A valid package still will not open in a supported browser.
- The visible error does not match link, expiry, or passphrase troubleshooting.
Include only support-safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
Still stuck?
Copy a safe article handoff.
Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.
- Article slug
- Selected issue
- Screen name
- Action name
Redactorr support case Source: Article playbook: package-decryption-troubleshooting Route: /knowledge-base/package-decryption-troubleshooting Selected issue: A valid package still will not open in a supported browser. Safe context: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-redacted sample only after review. - Article slug - Selected issue - Screen name or article section - Action name Only include with explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture - Hidden diagnostic uploads User note: - Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.
Support case builder
One case format, wherever you start.
This is the same support case shape used by diagnostics and article handoffs.
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Article slug
- Selected issue
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions