> ## Documentation Index
> Fetch the complete documentation index at: https://docs.purpify.host/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot a server that will not start

> Use the Purpify console and recent server changes to diagnose startup failures, crashes, and restart loops.

When a server will not start, find the first useful console error and undo the most recent change. World uploads, add-ons, configuration edits, version changes, and an unaccepted EULA are common causes.

## Find the first useful error

Open the Purpify console and start the server once. Read the output from the start of that attempt. The last line may only report that the process stopped; the useful error often appears several lines earlier.

Copy the error before changing anything. Remove passwords, tokens, private addresses, and player information before sharing it.

## Undo the latest change

Use the branch that matches what changed immediately before the failure:

<AccordionGroup>
  <Accordion title="The EULA has not been accepted">
    Open the server in the Purpify panel and select **Accept EULA**. Start the server again and watch the console until startup completes.
  </Accordion>

  <Accordion title="You uploaded a world">
    Confirm that the world folder directly contains `level.dat` and that the configured world name exactly matches the folder. Restore the previous world when the uploaded world is damaged or incompatible.
  </Accordion>

  <Accordion title="You installed or updated an add-on">
    Restore the backup made before installation. Then follow [Troubleshoot Bedrock add-on errors](/troubleshooting/bedrock-addon-errors) to verify packs, dependencies, experiments, and versions.
  </Accordion>

  <Accordion title="You installed or updated a plugin">
    Leave the server stopped and follow [Troubleshoot Java plugin errors](/troubleshooting/plugin-errors). Check the first named plugin, its dependencies, and compatibility.
  </Accordion>

  <Accordion title="You changed mods or the mod loader">
    Compare the Minecraft version, loader family, loader version, mods, and dependencies. Follow [Troubleshoot Java mod-loader mismatches](/troubleshooting/mod-loader-errors).
  </Accordion>

  <Accordion title="You edited a configuration file">
    Restore the last known working file. Check the edited value's spelling, allowed format, and quotation marks before applying the change again.
  </Accordion>

  <Accordion title="You changed the server version">
    Restore a backup created before the version change. Confirm that the world and add-ons support the target version before trying again.
  </Accordion>

  <Accordion title="Nothing changed">
    Check the [Purpify service status](https://uptime.purpify.host), [disk usage](/troubleshooting/disk-space), and resource usage, then retry one normal start. Avoid repeated restart loops because they can overwrite useful logs.
  </Accordion>
</AccordionGroup>

## Restore service safely

<Steps>
  <Step title="Stop automatic restarts">
    Leave the server stopped while you inspect files and logs.
  </Step>

  <Step title="Preserve evidence">
    Save the relevant console output and note the exact time of the failed start.
  </Step>

  <Step title="Restore the last working state">
    Restore a known-good backup or reverse only the latest change.
  </Step>

  <Step title="Start once and test">
    Watch the complete startup. When the server remains running, join it and verify the affected feature.
  </Step>
</Steps>

## Information to send support

Send the server name or account-visible server ID, failure time and time zone, complete relevant console error, and the last change made. Never send your account password.