Connect to editor

Access the code editor directly from your browser to edit files on remote servers.

Open the editor

The editor opens through a work session. You request a session with the Code editor feature, and once it’s approved you launch the editor from the session.

  1. On a server card or detail page, click Connect (or open Sessions and create a new session).
  2. In the request, include the Code editor feature, then submit. See Request a session.
  3. Once the session is Active, open its Session tab and click Editor on the server you want to edit.
  4. The editor opens in a new browser tab.

You can also start from My active sessions on the dashboard.

To come back to an editor you already opened, reload its tab, open its address again, or click Reconnect on the session’s Resume tab. See Editor sessions.

Requirements

  • Server is commissioned and Online
  • The server has the Code editor setting turned on. If it is off, that server’s Editor action explains why it cannot open. See Tunnel and code editor.
  • You have an Active work session that includes the Code editor feature for the server
  • You belong to a group assigned to the server (or are a workspace administrator)

Account selection

The editor connects as the account you chose under Connect as when you requested the session. By default that’s your own account: your Alpacon username is used as the remote user. For privileged actions, use sudo with MFA.

The editor is not available on Windows servers.

For the account choices and who can use an account other than their own, see Account selection.

MFA for an account other than your own

When your workspace requires MFA for the editor, launching it from a session that runs as an account other than your own asks you to verify first. Connecting as your own account doesn’t.

  1. Click Editor on the server’s row
  2. A notification appears indicating MFA is required
  3. You are redirected to the MFA authentication page
  4. Complete authentication (TOTP, email, phone, or WebAuthn)
  5. After successful verification, you are automatically redirected back and the editor opens

Verification stays valid for the period your workspace sets, so launching the editor again within that period doesn’t ask you to verify again.

First-time connection

The first time you connect to a server via the editor, the editor environment is automatically installed. This process may take a few minutes.

Connection steps:

  1. Creating tunnel: Alpacon opens a connection to the server
  2. Preparing editor: the editor is being installed or prepared on the server
  3. Starting editor: the editor is starting up

Once it’s ready, the editor opens.

Subsequent connections to the same server will be faster as the environment is already installed.

Troubleshooting

The editor shows Connection error:

  • Read the reason on the screen. If the editor has closed or the work session is no longer active, launch the editor again from an active session
  • Verify the server is connected and online
  • Click Retry to attempt reconnection
  • Click Back to servers to return to the server list

The editor shows Editor connection lost or Network connection lost:

  • Click Reconnect. If the editor is still running, you return to it; if it has closed, the Connection error screen shows why. See Connection lost

The editor shows a “Bad Gateway” page:

  • The editor closed after about an hour (by default) with no browser tab connected to it. Terminate it from the work session’s Resume tab and launch a new one. See Close an editor

The editor is stuck on Preparing editor:

  • First-time installation may take a few minutes
  • If installation fails, click Retry

MFA authentication fails:

  • Ensure you have enrolled an MFA method accepted by the workspace
  • Check that your MFA device is available
  • Contact workspace administrator if issues persist
Last updated: