---
title: Run challenge instances
description: Start, connect to, and manage your team's challenge instance.
---

Some challenges don't ship as downloads: they run as a live environment your team starts on demand. Those challenges have a **Challenge Instance** section on their page: *"This challenge requires a deployment instance. Create one to get started."*

Instances are per-team: everyone on your team shares the same instance, its connection details, and its flag.

## Start an instance

Click **Create Instance**. The card shows the instance's status while it comes up:

- **pending** and **provisioning**: the environment is being prepared; the page checks for updates every few seconds.
- **running**: ready to use; connection details appear (see below).
- **failed**: the session could not be prepared. The card reads *"Something went wrong while preparing this challenge session. Please try again or contact an organizer."* with a **Try again** button.

Instances can only be started while the event is live: before the start you'll get *"The competition hasn't started yet."*, after the freeze *"The competition is frozen; instances cannot be started."*, and on team events you need a team first (*"Create or join a team before starting challenge instances."*).

## Connect to it

Once the instance is **running**, each exposed port gets its own entry under **Connect**, labeled with its service name and port whenever a challenge exposes more than one port. Connect to the one the description points you at.

- **Web ports** show a link. Clicking it opens the challenge over `https://` in a new tab.
- **TCP ports** show a ready-to-copy `athena-proxy add <hostname>` command. [athena-proxy](https://downloads.athena-ctf.com) is a small local program that gives you a plain `127.0.0.1` address your usual tools connect to. Start `athena-proxy run` and leave it running, then `add` each hostname and it prints the local address to point `nc`, `pwntools` or a debugger at. The hostname is printed alongside as well, for anyone who prefers to drive a TLS client at port 443 themselves.

Your hostnames don't change when an instance expires or is redeployed, so a target you registered once keeps working for the rest of the event.

## Watch the expiry

Instances don't run forever: the card shows **Expires in** with a live countdown (`42:15`, or `1:04:09` when there's more than an hour left) ticking down toward zero, at which point it reads **Expired**. Once it does, the status shows **expired** and the card reads *"This instance has expired. Redeploy to start a new session."* Your progress inside the environment is gone, but redeploying gives you a fresh copy, and on dynamic-flag challenges **your team's flag stays the same across redeploys**, so an expiry never costs you a flag you'd already found.

## One instance at a time

Your team can have **one active instance across all challenges**. Starting an instance on a different challenge doesn't error; it **replaces** the current one, terminating the old instance automatically so the new challenge's environment can take its place. That applies across the whole team, so the session you end is often a teammate's. Coordinate before you launch.

Clicking create again on the *same* challenge redeploys that challenge's instance, but only once it has failed, expired, or been terminated. A healthy running instance can't be redeployed over.

## Terminate and redeploy

- While an instance is provisioning or running, **Terminate Instance** shuts it down, after a confirmation: *"This stops your running session. You can redeploy a new instance afterwards."* When the instance was started by a teammate, the confirmation names them instead and warns that closing it stops **their** session.
- A **failed**, **terminated**, or **expired** instance offers **Redeploy Instance** (or **Try again**) to start a new session. Those are the only states you can redeploy from. To replace a healthy running instance you terminate it yourself first, then create it again.

## When the challenge is locked

If starting an instance refuses with *"This challenge is temporarily locked."*, the organizers have taken the challenge out of play. Any instance you had running is shut down and does not come back, so you start a fresh one after the unlock. See [When a challenge is locked](/players/how-to/when-a-challenge-is-locked).

## After you solve

Once your team solves the challenge, you can't start or redeploy instances for it anymore: the card shows *"You've already solved this challenge, so no deployment instance is needed."*, and an expired or terminated instance can no longer be redeployed. An instance that's still running keeps running until it expires or you terminate it, but since a redeploy is off the table, grab anything you still need from the environment **before** it winds down.
