Boxcryptor is eventually signed-in to a wrong account.

On desktop some Applications or the file browser shows a message with Invalid parameter when trying to open a file. This can have multiple reasons: Boxcryptor Access Issues There may be situations where files appear to be inaccessible. Learn more about exporting your keys and local accounts. when sharing files with other Boxcryptor users), it is recommended to regularly export a new key file.Īfter installing Boxcryptor, you can use the exported key file to access your encrypted files using a local account. Important: As new keys might be added over time by Boxcryptor's integrated key management (e.g. The exported key file contains all encryption keys associated with your Boxcryptor account. When these files are available, you will always be able to access your encrypted files on your own on any supported operating system - without any connection to any server. If you want to take additional precautions for the event that the Boxcryptor servers would go permanently offline, you must have the following backups: If you already have created a support case, you can simply enter the case number into the email body and we will automatically link your case.īoxcryptor has been designed in such a way that Boxcryptor continues to work even if the Boxcryptor servers are not available and you're still signed into Boxcryptor. Boxcryptor_Portable/Boxcryptor/app/.boxcryptor-internals/log/clogĪfter you enabled debug logging and reproduced your steps, you can send us an email with the debug log and a description what went wrong. macOS: ~./Boxcryptor Portable.app/Contents/Java/.boxcryptor-internals/log/.If you are already authenticated, you can enable Enable logging in the settings.Ī debug log ( clog ) is generated and saved to the following location: Run Boxcryptor_Portable.sh with your terminal.

Open Boxcryptor_Portable.sh with an editor.

Drag the Boxcryptor Portable.exe into this window.

Open the command shell (Windows Key+R → type cmd → Enter).

Add -args -d at the end of the command-line and execute it.

Drag the Boxcryptor Portable.app into this window.

If you experience problems before you can even sign in, you can enable a debug log via console:

System information such as OS version or required frameworks.

Communication with our servers and your cloud provider(s).

File operations ( including unencrypted filenames ).

User interaction such as button clicks and in-app navigation.

The debug log captures the following information. Which Information Does a Debug Log Contain? When you create a debug log, sensitive user information - like password, encryption keys, or actual file content will not be logged. It can help us to track down issues with Boxcryptor, for example bugs and incompatibilities with other software. A debug log captures all internal events while Boxcryptor is running.

Boxcryptor problems