Skip to content
Docs
strackt.io Open app

When a server can't be detached

Why strackt won't detach a server that is still passing visitors on to environments you moved elsewhere, and what you can do about it.

When a server can't be detached

When you move an environment to another server, the original server can keep receiving that environment's visitors and passing them on to its new home. While a server is still doing that for any environment, strackt won't detach it: once detached, strackt no longer manages it, and every environment that depends on it would go offline with no warning.

This page explains when that happens and what you can do. For what detaching involves in general, see Detached servers.

How it looks

On the server's Settings page, the Detach server row shows a disabled Detach button with a message like this, naming each environment involved:

This server still passes visitors on to Shop (production), which now run on another server, so detaching it would take them offline. Wait for any move in progress to finish, or move them back to this server or delete them, then try detaching again. To keep them where they are, contact support.

If the situation changes while the detach dialog is open, submitting it returns the same message. Nothing on the server has changed, and your environments keep serving as before.

Why a server keeps passing visitors on

There are two situations that hold a detach back:

  • A move is switching over right now. While a move from this server is cutting over or finishing, visitors can still be arriving here. Detaching mid-switch would cut the environment off halfway.
  • An environment moved to a server without its own public address. Your visitors can't reach that server directly, so after the move this server stays in front of the environment and keeps passing its visitors on — for as long as the environment lives there.

What you can do

  • Wait for a move in progress to finish. Open the environment's page and watch the Server card until the move completes, then try detaching again. If the environment's new server has its own public address, this server stops passing visitors on once the move completes. See Move an environment to another server for the stages of a move.
  • Move the environment back onto this server. On the environment's page, use Move to another server on the Server card and choose this server. Once the environment is back here, visitors reach it directly and nothing depends on passing them on. The environment then stays on this server, including after you detach it.
  • Delete the environment if you no longer need it. In the application's Settings, Delete environment removes the environment and its configuration. This can't be undone, so only use it for an environment you're finished with.
  • Contact support for anything else. Moving the environment on to a third server doesn't release this one, and neither does giving the environment's server a public address later. If you want to keep the environment where it is and still detach this server, or you can't tell which environment is involved, contact support and we'll help you release it safely.

Each of these clears one reason. If more than one environment depends on this server, deal with each of them, then try detaching again.

What to do next

Was this helpful?