GuideTroubleshootingPage Crash or Error

    Page Crash or Error

    Encountered an unexpected crash, a blank page, or an error screen in Simply Send? This guide walks through the most common causes and how to recover quickly — including a known issue with browser translation extensions.

    What a Page Crash Looks Like

    When Simply Send encounters an unrecoverable rendering error, it shows an error screen instead of the normal page content. You may see something like this:

    app.simplysend.email/smtp

    🫣

    Something went wrong

    We apologize for the inconvenience. An unexpected error has occurred while processing your request.

    Reload Page← Go Back
    🏠 Return Home✉ Contact Support ↗
    Simply Send error screen

    In most cases, clicking Reload Page on the error screen is sufficient to recover. If the crash happens repeatedly on the same action, read on for specific causes and fixes.

    Browser Translation (Most Common Cause)

    This is the #1 cause of sudden crashes

    When your browser auto-translates Simply Send into another language (e.g. using Chrome's built-in translation or an extension), it directly modifies the page's HTML structure. This conflicts with how Simply Send manages the page, causing a removeChild or insertBefore DOM error — which triggers the crash screen.

    How to Fix It

    If you see the crash screen after a page translation was applied, follow these steps:

    1

    Disable Translation on This Page

    Chrome
    • Click the Translate icon in the address bar
    • Click (three dots menu) → Never translate this site
    • Or right-click the page → Translate to English to toggle off
    Edge / Other Browsers
    • Click the Translate icon in the address bar
    • Select Never translate this page or toggle translation off
    • Disable any installed translation extensions in browser settings
    2

    Reload and Repeat Your Steps

    After disabling translation, reload the page and try repeating the action that triggered the crash. The page should now work correctly without interference from the browser translation engine.

    Use Ctrl+R (Windows) or ⌘+R (Mac) to reload
    3

    Still Crashing? Try a Private / Incognito Window

    Open Simply Send in a private/incognito window to rule out any browser extensions. Incognito mode disables most extensions by default, including translation tools.

    Other Common Causes

    Stale Browser Cache

    After a platform update, your browser may be using an outdated version of the app files, causing a conflict.

    Hard reload: Ctrl+Shift+R (Windows) · ⌘+Shift+R (Mac)

    Browser Extension Conflicts

    Certain extensions (ad blockers, accessibility tools, grammar checkers) may modify the page DOM in ways that conflict with the app. Try disabling extensions one by one or test in incognito mode.

    Poor Network Conditions

    A slow or interrupted connection can cause app resources to load partially. Try refreshing after ensuring a stable internet connection.

    Outdated Browser Version

    Simply Send uses modern browser APIs. An out-of-date browser may not support them correctly. Ensure you are running a current version of Chrome, Edge, Firefox, or Safari.

    Quick Recovery Checklist

    • Disable browser translation on this page (most likely cause)
    • Reload the page and repeat the steps that caused the crash
    • Hard-reload (Ctrl+Shift+R / ⌘+Shift+R) to clear the cached app bundle
    • Open in incognito mode to disable all extensions
    • Try a different browser (Chrome, Firefox, Edge, Safari)
    • Ensure your internet connection is stable
    • Check if your browser is up to date

    Still Crashing? Report the Issue

    If the crash persists after trying all the steps above, please let us know. The more details you provide about exactly what you were doing when the crash happened, the faster we can identify and fix it.

    When reporting, please include:

    • The page or feature you were using (e.g. Domain Management, Integrations)
    • The exact action you took just before the crash
    • Your browser and version (e.g. Chrome 124, Safari 17)
    • Whether browser translation was active at the time
    • A screenshot of the error screen if possible
    Report This Issue