Skip to content
Contact us
  • There are no suggestions because the search field is empty.

How to check for 500 Errors in our Hands-On Lessons

Learn how to troubleshoot 500 Internal Server Errors in Security Journey Hands-On Lessons by reviewing Sandbox Output, rerunning tests, and identifying code-related issues.

Overview

A 500 Internal Server Error in a Security Journey Hands-On Lesson is most commonly caused by a syntax or compilation issue in a code submission. This guide explains how to confirm the cause and get the information you need to resolve it.

Symptoms

You see one or more of the following:

  • A 500 error when using the sandbox web application (e.g., login, search, submitting a form).

  • Your lesson appears to fail after clicking Save Code & Run Tests.

  • The sandbox behaves unexpectedly after a code change.

Most Common Cause

✅ Syntax or compilation errors in the code submission.

These errors often generate stack traces or output messages that can be seen in the Sandbox Output panel.

Resolution Steps (Recommended Workflow)

1) Re-run the tests after saving code

  1. Go to the Code Editor tab.

  2. Make any needed updates.

  3. Click Save Code & Run Tests.

This updates the code running in the your sandbox.

2) Reproduce the error in the sandbox application

  1. Open the sandbox web app (the lesson environment).

  2. Perform the action that triggers the error
    Examples:

    • Log in

    • Run a search

    • Submit a vulnerable input

    • Navigate to the failing feature

This helps confirm whether the 500 error is tied to the current code behavior.

3) Check Sandbox Output for errors

  1. Locate the Sandbox Output area (typically at the bottom of the screen).

  2. Open it and look for:

    • Stack traces

    • Error messages

    • stdout/stderr output

    • Debug print output

This is the primary place to confirm code-related causes of 500 errors.

4) Add print/debug statements (if needed)

If you aren't seeing enough detail:

  1. Add basic output statements (ex: print/log statements) in their code.

  2. Run the sandbox again.

  3. Re-check Sandbox Output for those messages.

This can help isolate what code path is causing the failure. If you need further guidance on how to get output. Check out this article: Tips for Getting Sandbox Output.

Customer Support Contact (for learners)

If the learner is stuck and needs direct assistance, they can contact Customer Support using the chat bubble in the bottom right of the screen.