What is protection mode?

Protection mode is CryptPeer®'s active security posture. When an essential check cannot be confirmed at startup or during operation, the platform preserves your environment by limiting access rather than opening a workspace whose integrity is not assured.

CryptPeer® is designed as a sovereign, self-hosted, self-installable and self-operable platform capable of running on Windows, Linux, macOS, WSL, VM, VPS and offline infrastructures, without mandatory cloud dependency.

Key point

This is not an unexpected failure: it is secure continuity preserving your data, license and operational sovereignty.

CryptPeer is built on continuous protection: encryption from the end-user device, a blind-by-design server architecture, and clear assistance messaging — in 18 languages — to guide you calmly, without unnecessary jargon.

Why CryptPeer temporarily limits access

When access is limited, CryptPeer applies proactive protection: safeguarding the confidentiality of your communications, the validity of your license and the stability of your secure environment.

  • Prevention — avoiding service resumption in an uncontrolled context;
  • Persistent protection — maintaining confidentiality and encryption on the user device;
  • Data and license protection — priority to the integrity of your sovereign deployment;
  • Environment stability — ensuring reliable continuity before full reopening.

Your data stays protected on the user endpoint; the application relay does not process content in the clear. No mandatory cloud exposure is required to continue assistance.

Active protection, built for enterprise

CryptPeer continuously strengthens the security of your sovereign collaboration, including against:

  • malicious acts or behavior;
  • malware and environment corruption;
  • unusual behavior or unauthorized system modification attempts;
  • security violations, compromised environments or infrastructure incidents;
  • unauthorized changes affecting service continuity.

Temporary access limitation is part of this controlled prevention approach — for your teams' peace of mind and your organization's trust.

Self-operable sovereign deployment

Unlike many secure collaboration platforms, CryptPeer® can be deployed, diagnosed and operated locally by an operator without imposed cloud infrastructure or mandatory SaaS dependency.

Why an emergency page appears

You may see an emergency page (sober screen, dark background, protection symbol) when CryptPeer needs to confirm your environment is ready to host the full application again, for example if:

  • secure initialization sequence has not yet completed;
  • a license or environment check is in progress;
  • planned maintenance or a security operation is active;
  • local access to your data requires a brief stabilization.

The page is provided by an integrated fallback mini server: it remains available even when the usual interface is not yet accessible.

Important information

The term “emergency” refers to a secure continuity interface and does not indicate a confirmed system compromise.

Integrated fallback assistance server

The integrated fallback assistance server is a lightweight, autonomous assistance layer. It supports you even when the full application is not yet available:

  • clear instructions in 18 languages;
  • simple actions (restart, assistance documentation);
  • download of an incident diagnostic file for your support team;
  • offline use on workstation, VM or local VPS — no mandatory cloud.

Data protection and continuity of trust

In protection mode, CryptPeer maintains proactive security and preserved confidentiality. Your content remains encrypted on the user device; the blind server architecture does not receive your data in the clear.

Local sovereign infrastructure

CryptPeer® enables local deployment of a secure communication platform without mandatory cloud dependency, compatible with sovereign architectures, enterprise environments, defense infrastructures and isolated systems.

Messages on the assistance page are deliberately calm and reassuring: they guide you toward service resumption without revealing sensitive infrastructure details.

Your license and secure environment stability shape next steps: validated re-import, administrator guidance or publisher assistance, depending on your organization.

Data protection status

Protection mode does not imply data loss. Runtime continuity protections are designed to preserve encrypted local data integrity during incident handling and secure recovery procedures.

Offline, VM and VPS

CryptPeer® is designed for sovereign, self-hosted and self-installable deployments on local workstations, enterprise VM, VPS, local Docker, offline infrastructures and isolated environments.

CryptPeer® is suitable for enterprise, governmental, defense, industrial and sovereign infrastructures requiring local control, offline continuity and secure self-hosted deployment.

CryptPeer assistance references (CP-XXX-NNN)

Each incident displayed by CryptPeer includes a standardized assistance reference using the format: CP-XXX-NNN

Why this reference exists

This reference helps identify the incident category quickly, guide the user to the right procedure and speed up administrator or support assistance, without exposing sensitive information about your environment.

CryptPeer references are designed to remain:

  • short and easy to communicate;
  • understandable by every user profile;
  • compatible with offline, VM and VPS deployments;
  • stable over time;
  • suitable for enterprise and sovereign environments.
Reference Meaning Example
CP-DRT Protected environment and startup verification CP-DRT-007
CP-LIC License, activation or validation CP-LIC-001
CP-OFF Offline operation or limited connectivity CP-OFF-001
CP-AUTH Login, session or authentication CP-AUTH-001
CP-ENV VM, VPS or system configuration environment CP-ENV-001
CP-MAINT Maintenance or administrator operation CP-MAINT-001
CP-REC Recovery, restore or secure service resumption CP-REC-001
CP-STOR Local storage, disk or secure volume CP-STOR-001
CP-SYNC Synchronization or service continuity CP-SYNC-001

Protecting your environment

CP-XXX-NNN references never reveal sensitive technical information. They are used only to simplify assistance, improve incident understanding and accelerate secure recovery.

In a code such as CP-DRT-007:

  • CP → CryptPeer universe;
  • DRT → the protection category involved;
  • 007 → the unique assistance identifier used by support.

Always provide this reference to your administrator or CryptPeer support: it helps with diagnosis while preserving the confidentiality of your environment.

JSON diagnostic download

From the emergency page, the “Download diagnostic” button generates cryptpeer-incident-diagnostic.json in your browser (no automatic upload to the Internet).

The file includes only what your support team needs: incident reference, deployment context, recommended actions and an assistance summary — no keys, message content or confidential organizational data.

Quick support actions

✔ No confidential content included

This feature allows administrators and operators to quickly copy a sanitized runtime summary into support tickets, incident reports, email or enterprise collaboration tools.

Runtime status levels

CryptPeer uses standardized visual runtime levels to simplify operator assistance, runtime diagnostics and incident understanding, including in offline, VM, VPS and air-gapped environments.

Sovereign continuity

These runtime states are informational only. They never replace technical logs, security decisions or internal protection mechanisms.

Status Meaning
🔒 SOVEREIGN READY Sovereign runtime operational and continuity protections verified.
✔ VERIFIED Verification completed successfully.
▲ WARNING Attention required but runtime still operational.
⚠ DEGRADED Runtime operational with reduced capabilities or trust posture.
✖ SECURE BLOCK Runtime startup intentionally blocked to preserve integrity and security.
ℹ INFO Informational runtime message without direct security impact.
🔒 CONTINUITY Continuity protections and sovereign safeguards remain active.

Installation progress example

ℹ Installing sovereign runtime dependencies...
ℹ Verifying local HTTPS environment...
ℹ Detecting platform compatibility...
🔒 Initializing sovereign continuity protections...
ℹ Estimated remaining time: 3–8 minutes
✔ Runtime initialization completed

Installation duration

Initial installation duration may vary depending on:

  • operating system;
  • hardware performance;
  • Windows Defender or antivirus activity;
  • WSL filesystem performance;
  • offline dependency cache availability;
  • npm native package compilation.

Typical installation time:

  • Linux native: 2–6 minutes;
  • Windows PowerShell: 5–15 minutes;
  • WSL2 on NTFS: 10–25 minutes;
  • Offline / airgap: depends on local cache availability.

Integrated operator assistance

CryptPeer® provides structured and guided operator assistance designed to simplify installation, diagnostics and operation of a secure sovereign infrastructure.

This approach reduces the need for advanced technical support while improving deployment autonomy, operational continuity and resilience of secure environments.

Runtime diagnostic command

npm run doctor internally executes npm run sovereign-local:doctor

Recommended local diagnostic:

npm run doctor

Example output:

✔ Node.js version verified
✔ HTTPS certificates available
✔ EviSKMS-Core bridge reachable
▲ TPM unavailable
⚠ WSL runtime running on NTFS mount
✖ Native package platform mismatch

Healthy runtime example

🔒 SOVEREIGN READY

✔ Node.js runtime verified
✔ HTTPS certificates verified
✔ EviSKMS-Core bridge reachable
✔ Runtime continuity verified
✔ Local sovereign services operational
✔ Last runtime verification: 2026-05-20 14:22 UTC

Runtime diagnostic codes

CryptPeer may display runtime diagnostic references intended for administrators, runtime operators and support teams.

These references remain compatible with:

  • offline environments;
  • SSH and remote terminals;
  • VM and VPS infrastructures;
  • CI/CD environments;
  • enterprise and forensic support workflows.

Sensitive information protection

Runtime diagnostic codes never expose:

  • cryptographic keys;
  • runtime secrets;
  • user content;
  • EviSKMS segments;
  • sensitive infrastructure components.
Code Description Impact
WSL-NODE-001 Cross-platform dependency conflict detected inside WSL. SECURE BLOCK
TPM-002 TPM unavailable — degraded trust mode enabled. DEGRADED
HTTPS-004 Local HTTPS certificate generation failure. WARNING
DRT-008 Runtime startup refused by continuity protection mechanisms. SECURE BLOCK
CORE-003 EviSKMS-Core bridge unavailable. SECURE BLOCK
DOCKER-001 Docker runtime unavailable. WARNING

Offline assistance

CryptPeer runtime diagnostic references remain usable without Internet access in order to preserve operator continuity in sovereign, isolated and air-gapped infrastructures.

Operator example

✖ SECURE BLOCK WSL-NODE-001

Incompatible Linux dependencies detected inside a WSL environment using a Windows NTFS volume.

Recommended action:
rm -rf node_modules
npm install --prefer-offline

Fullsecure® compatibility

The JSON diagnostic is structured for automatic ingestion by support tools (compatibility with Fullsecure®). Your organization can open enriched tickets, speed up diagnosis and maintain enterprise traceability without technical copy-paste.

User procedure (simple)

  1. Read the displayed title and message — they explain the situation in plain language.
  2. Note the support reference (e.g. CP-DRT-007).
  3. Click Download diagnostic and keep the JSON file.
  4. Use Restart application once if your administrator advised it.
  5. Send the reference and JSON to your administrator or CryptPeer support.

Administrator procedure

  1. Identify the CP-XXX-NNN reference and category (license, maintenance, environment…).
  2. Analyze the JSON diagnostic (product version, deployment mode, startup state).
  3. Check license, planned maintenance, connectivity and local database access.
  4. Apply documented procedure (license re-import, service restart, VM/VPS validation).
  5. Open or enrich the support / Fullsecure® ticket with reference and JSON file.

Detailed guides: Administrator user guide, Super Admin.

Local access

Depending on your installation, CryptPeer is reachable via:

  • http://127.0.0.1:5173 — development or typical local instance;
  • http://localhost — depending on reverse proxy configuration;
  • Local Docker — URL published by your compose (often port 5173 or 3000);
  • Local VM / VPS — internal IP or hostname documented by your IT.

In protection mode, the same address may show the emergency page instead of the usual interface.

Situations that may show the emergency page

These situations are possible but uncommon: they explain why CryptPeer enters protection mode instead of the full application — which is why this assistance page exists.

Expired or pending license

Typical reference CP-LIC-001 to CP-LIC-004. Re-import a valid license or contact your administrator. See the incident assistance FAQ.

Planned maintenance

CP-MAINT-001 — wait or follow internal communication; no risky user action.

Restart required

Recommended action on the page; one clean restart is often enough after admin fix.

Changed environment

CP-ENV-001 or CP-DRT-001 — check VM, disk, undocumented migration.

Database unreachable

Check database service, disk space, permissions; administrator consults Super Admin guides.

Recovery / reset

Follow only the procedure validated by your organization — do not reset without governance.

VM / VPS reboot

After hypervisor or host reboot, wait for services to come up then restart CryptPeer.

CryptPeer appears stuck

If the screen does not change:

  • confirm the exact URL (127.0.0.1, localhost, VM IP);
  • download the JSON diagnostic from the emergency page;
  • run the browser compatibility diagnostic on a client workstation;
  • contact your administrator with CP-XXX-NNN reference + JSON file.

Premium assistance, built on trust

Protection
Controlled prevention
Diagnostic
Local file
Assistance
CP-XXX reference
Resumption
Secure continuity
  • Sovereign architecture — endpoint encryption, blind server, controlled deployment;
  • Continuous protection — preventive limitation for your data and license;
  • Proactive assistance — clear, multilingual guidance even during incidents;
  • Simplified operator experience — installation, diagnostics and autonomous deployment without advanced cybersecurity expertise;
  • Offline continuity — diagnostic and documentation without mandatory cloud;
  • Trusted relationship — enterprise transparency, readable for every profile;
  • Self-installable platform — guided sovereign deployment without imposed cloud dependency.

A rare capability in the global market

The ability to locally deploy a self-installable sovereign secure platform, compatible with offline environments, VM, VPS and isolated infrastructures, remains rare in the global enterprise collaboration market.

CryptPeer® combines secure continuity, integrated operator assistance and patented sovereign technologies to simplify the operation of secure environments without mandatory cloud dependency.

Few solutions today provide self-installable sovereign deployment with integrated secure continuity and local operator assistance without imposed cloud dependency.

Sovereign technologies integrated into CryptPeer

CryptPeer relies on several advanced protection, secure continuity and sovereign trust technologies developed by Freemindtronic®.

These technologies help:

  • preserve secure continuity across environments;
  • strengthen VM and VPS environment protection;
  • improve offline deployment resilience;
  • maintain a privacy-preserving and blind-by-design server architecture;
  • detect certain unusual behaviors or compromised environments;
  • reinforce license and encrypted data protection.

Sovereign trust infrastructure

The protection mechanisms integrated into CryptPeer notably rely on:

  • EviSKMS Runtime Sovereign Trust Doctrine;
  • EviSKMS Runtime Integrity;
  • EviSKMS Sovereign Runtime Anchors;
  • EviSKMS PKI Runtime Infrastructure.

These components help strengthen service continuity, secure environment stability and proactive protection for critical infrastructures.

Learn more:

Frequently asked questions

Dedicated FAQ

Detailed answers (security, diagnostic, languages, support portal) are grouped in the Incident assistance and protection mode section of the CryptPeer® FAQ.

See also the glossary for definitions of terms used on this page.