SOS Support & Security

Get help with SOS, report a problem or contact apluskdesign about a security concern

Last Updated: 01/10/2026

Version: 1.0

SOS Documentation

We’re here to helpIf you need help using SOS, have a question about the documentation or want to report a potential security concern, you can contact apluskdesign directly.

SOS – Critical Error Page is developed and maintained by apluskdesign.

This page explains where to find help, what information is useful when reporting a problem and how to contact us about a potential security concern.

Before contacting support

The SOS documentation covers the most common setup, testing and troubleshooting questions.

Before contacting support, you may find the answer in:

Checking Developer Tools before contacting support can also provide useful evidence about the current SOS installation.

Get support

For help with SOS, email:

support@apluskdesign.com

Please describe the problem as clearly as possible so that we can understand what you were trying to do and what happened.

What information should I include?

Useful information can include:

  • the SOS version;
  • your WordPress version;
  • your PHP version;
  • what you were trying to do;
  • what you expected to happen;
  • what actually happened;
  • whether the problem can be reproduced;
  • the relevant Developer Tools status; and
  • relevant error-log information with sensitive information removed.

If the problem involves the optional Geneva connection, information such as the connection status or HTTP status shown in Developer Tools may also be useful.

Understand SOS Developer Tools →

Protect your credentials

Please do not send passwordsWe do not need your passwords in order to receive and assess an initial support request.

Do not email:

  • WordPress administrator passwords;
  • hosting or control-panel passwords;
  • database credentials;
  • FTP or SFTP passwords;
  • API secrets;
  • private keys; or
  • other sensitive access credentials.

If further investigation genuinely requires additional access or information, that should be discussed separately rather than included unnecessarily in the initial request.

Report a potential security concern

If you believe you have found a potential security vulnerability in SOS, please report it responsibly to apluskdesign.

Email:

support@apluskdesign.com

Use a clear subject line such as:

SOS Security Report

Please provide enough information for us to understand and investigate the issue, including where appropriate:

  • the SOS version affected;
  • the WordPress and PHP versions used during testing;
  • a clear description of the potential vulnerability;
  • the steps required to reproduce it;
  • what you expected to happen;
  • what actually happened; and
  • any relevant technical evidence that can be shared safely.

Please report security issues responsibly

If you believe you have identified a genuine security vulnerability, please give apluskdesign a reasonable opportunity to investigate the report before publishing detailed information that could unnecessarily expose other SOS users.

Please do not use a suspected vulnerability to access, modify, damage or obtain information from websites or systems that you do not own or have explicit permission to test.

Good-faith reports are welcomeClear, reproducible information helps us understand a potential issue and determine whether SOS requires a security update.

What can SOS support help with?

apluskdesign can help with questions relating to SOS itself, including:

  • installing and configuring SOS;
  • the Critical Error Page;
  • the controlled fatal test;
  • Developer Tools statuses;
  • SOS-owned drop-in behaviour;
  • the resilience profile;
  • the optional Geneva connection; and
  • suspected SOS bugs or security concerns.

Problems outside SOS

A Critical Error Page can appear because another part of the WordPress website has encountered a fatal error.

SOS displaying correctly does not mean SOS caused that underlying problem.

We may be able to help explain the evidence provided by SOS, but problems involving another plugin, theme, hosting environment, custom code or WordPress itself may need to be investigated by the relevant developer, provider or support service.

Troubleshooting SOS →

WordPress.org support

SOS is distributed through the WordPress Plugin Directory.

Once the public WordPress.org listing and support forum are available, users may also use the official SOS support area on WordPress.org for appropriate plugin questions.

Do not publish passwords, credentials, private server information or other sensitive information in a public support forum.

Security reports should not be posted publiclyIf you believe you have found a security vulnerability, contact apluskdesign directly rather than publishing technical exploitation details in a public support thread.

Support SOS

SOS is available free of charge.

If you find SOS useful and would like to support its continued development, you can buy apluskdesign a coffee.

Buy apluskdesign a coffee →

Supporting SOS is entirely optional and does not unlock features or affect the support available to you.

Thank you for helping improve SOS

Useful bug reports, clear support questions and responsible security reports all help make SOS better for the WordPress community.

If something does not seem right, we would rather know about it.

Continue exploring

Where next?

Troubleshoot

Troubleshooting SOS

Investigate common SOS statuses, testing problems, drop-in conflicts and Geneva connection issues.


Troubleshoot →

Technical

Developer Tools

Review the operational evidence that can help explain the current state of your SOS installation.


Developer Tools →

Start

Getting Started

Return to the beginning and review the core SOS setup, configuration and testing process.


Getting Started →

Call apluskdesign