Wespner Game Panel for Visual Studio Code

Sign in with your Wespner Game Panel account, watch and drive your game servers' consoles, edit server files and startup settings, and manage backups and databases directly in VS Code. Available in the same thirteen languages as the panel, following VS Code's display language.

Install

In VS Code, open the Extensions view, search for Wespner Game Panel and click Install, or open the extension's page in the Visual Studio Marketplace. It needs VS Code 1.95 or newer, and VS Code keeps it up to date.

For an editor that does not use the Visual Studio Marketplace, download the extension in the Wespner Game Panel: open Account → Connected apps and click Download the extension in the Visual Studio Code card. Then choose Extensions view → ⋯ → Install from VSIX… and pick the downloaded file. When a new version comes out, download it from the same page again and install it the same way.

Sign in

Open the Wespner view in the Activity Bar and click Sign in. Your browser opens the panel's login and consent page; after Approve access you are redirected back into VS Code. The redirect uses your editor's own URI scheme (vscode://, vscode-insiders://, cursor://, …), and the panel accepts those schemes for its OAuth clients (by default the ones of VS Code, VS Code Insiders, VSCodium, Cursor and Windsurf). Until you approve, a notification waits for the browser. Cancel it to stop the sign-in, which otherwise gives up after five minutes.

The first sign-in brings two questions from VS Code itself:

• "Do you want Code to open the external website?" before your browser opens the panel. Choose Open, or Configure Trusted Domains to trust the panel's address for good. If you cancel it, the sign-in stops with "Sign-in failed: Sign-in needs the panel's page in your browser. Allow VS Code to open it, then try again."
• "Allow 'Wespner Game Panel' extension to open this URI?" when the browser hands the sign-in back to VS Code. Tick Do not ask me again for this extension and choose Open, so later sign-ins come straight back.

The extension never sees your password — it holds an OAuth token stored in VS Code's secret storage, refreshed automatically, and listed in the panel under Account → Connected apps with your editor's name, where you can disconnect it at any time. Sign out from the view's title bar revokes it too.

What you can do

• Servers — every server you own or are a subuser of, with its live state (running, offline, starting, stopping, installing, installation failed, suspended, transferring, restoring a backup, node under maintenance). The power state is checked every 20 seconds or so while the view is visible and follows an open console at once. Refresh Servers in the view's title bar reloads the list and checks every state again at once; the last known states stay while it loads. Start, stop, restart and kill from the context menu (kill asks first), send a single console command, or open the server in the panel.
• Backups — expand a server for its Backups section, the panel's Backups page in the tree: every backup with its size and age, a spinner while it is being created, and how many of the backups your plan allows are in use ("2 of 5"). Hover a backup for its times, size, checksum and ignored files. Create Backup… on the section asks for an optional name, the files and folders to leave out and, if you may unlock it again, whether to lock it. On a backup, Download… saves it where you choose, with progress and Cancel; Restore… brings the server's files back to that backup, optionally deleting all files first; Lock protects it from deletion; Unlock… and Delete… ask first. A backup being created and a restore you started refresh themselves while you watch, and a notification says when a backup is ready or failed and when a restore has finished. What you see and may do follows your panel permissions.
• Databases — expand a server for its Databases section, the panel's Databases page in the tree: every database with its endpoint (host:port) and its storage use, and how many of the databases your plan allows are in use ("1 of 2"). A database turns yellow, then red, as it nears its storage limit, and shows a lock once it is full. Hover a database for its endpoint, user, allowed connection sources and storage. Create Database… on the section asks for a name and for where connections may come from (leave it empty to allow any address). The name may use the letters A–Z without accents, digits, _ and -, at least 3 characters; the panel puts s<id>_ in front of it (the prompt shows yours), and the two together may have at most 48 characters. On a database, Copy… puts its endpoint, user, password, JDBC string or mysql command on the clipboard; Rotate Password… gives it a new password after warning that applications using the old one stop connecting; Delete… removes it with all its backups once you type its full name, s<id>_ included. A new or rotated password is offered once, in the notification's Copy Password, and Copy… fetches it from the panel only when you pick it: the extension never stores a password. Expand a database for its backups, newest first. Back Up… on the database asks for an optional name and, if you may unlock it again, whether to lock the backup. On a backup, Download… saves it as a .sql.gz file, with progress and Cancel; Restore… overwrites the database with it, and Wipe the database and restore empties the database first (otherwise the tables the backup does not contain are kept); Lock, Unlock… and Delete… work as for file backups. A backup being made and a restore you started refresh themselves while you watch, and a notification says when a backup is ready or failed, with the reason, and when a restore has finished. What you see and may do follows your panel permissions.
• Startup — expand a server for its Startup section, the panel's Startup page in the tree: the startup command with its variables filled in (Copy puts it on the clipboard), the Docker image (Change Docker Image… picks another of the egg's images) and the egg's variables (click one, or Edit…: a pick of the allowed values, Yes / No, or a box that checks the egg's rules before the panel does and shows the panel's answer in place). A change takes effect the next time the server starts. What you see and may change follows your panel permissions, a read-only variable carries a lock, and when a server is installing, suspended, transferring, restoring a backup or on a node under maintenance, or its installation failed, the section says so instead. Refresh on the section loads it again (on such a server it first checks whether the server is back), and Collapse All in the view's title bar folds every server.
• Console — Open Console shows a live terminal per server: output as it happens, a command line with history (↑ / ↓), power buttons and CPU / memory / disk / uptime. Uses the same websocket as the panel; what you may do follows your panel permissions. Console tabs come back after a window reload and connect again by themselves; in a window that starts signed out a tab says "Sign in to Wespner Game Panel to continue." and connects once you sign in. The power buttons and the command line are named for screen readers.
• Files — Open Server Files adds the server as a workspace folder (wespner://<server id>/). With a folder already open you choose between this window, which becomes a multi-root workspace and reloads, and a new window. Browse, open, edit, save, create, rename and delete with VS Code's own Explorer and editor. Files above 4 MiB are transferred through the server's node directly, so large configs and logs open and save too (the node's upload limit, 100 MB by default, applies on save). The 4 MiB threshold is only an optimisation: when the panel still refuses a file as too large, the extension falls back to the node automatically. Right-click files or folders and choose Compress… to pack them into a .tar.gz on the server; right-click an archive for Extract Here (overwrites files of the same name, after asking) or Extract to Folder (a new folder named after the archive). Both run on the server, so nothing is downloaded.

Settings

Both are user settings: they apply to every window, not per workspace.

Remote development

In a remote window (Remote SSH, WSL, Dev Containers) the extension runs on the remote side, next to your workspace, so that machine must be able to reach the panel and your servers' nodes. The browser still opens on your own computer: the redirect comes back through VS Code's URI handler on your local machine and is forwarded to the remote extension host. VS Code for the Web (vscode.dev) cannot run the extension.

A backup you download in a remote window is handed to your browser, so it lands on your own computer, not on the remote machine. VS Code may ask before it opens the link: allow it, or the download does not start.

Note: sign-in in remote windows has not been tested yet. If it does not complete there, open a support ticket with the log from the output channel (see below).

Troubleshooting

• "Sign in to see your servers." after changing wespner.panelUrl. Each panel has its own sign-in. Reload the window when VS Code offers it, then sign in to the new panel.
• "The panel could not be reached." This computer got no answer from the panel at all. Check your internet connection, a VPN or proxy, and the address in wespner.panelUrl. The log (see below) names the reason, for example a name that does not resolve or a refused connection.
• "Use only the letters A to Z without accents, digits, underscores and dashes." when you create a database. Use the letters A–Z without accents, digits, _ and -, at least 3 characters: a database with any other character in its name could not be backed up, so the extension does not create it. The panel puts s<id>_ in front of the name (the prompt shows yours, for example s12_), and the two together may have at most 48 characters, so the longest name you may type is 48 minus the length of that prefix.
• Every action asks you to sign in although the view shows you signed in. Use Sign out in the view's title bar, then Sign in again. Signing in from the error message reuses the stored token, signing out drops it, so the next sign-in gets a new one.
• "The panel is rate limiting requests. Try again in … s." The panel limits how many requests an account may make per minute. Wait the time shown, then try again. The servers view paces its own checks to stay under that limit, and a server whose check fails keeps its last known state.
• The panel says two-factor authentication is required. Click Open Panel, set up two-factor authentication on your account, then try again.
• Logs: View → Output, then pick Wespner Game Panel in the list. It shows the panel in use and what failed, with the reason and a timestamp: the checks in the background (server states, the server list), the actions you ran and the sign-in. Attach it when you open a support ticket.

Licence

This extension is proprietary software for customers of the Wespner Game Panel; see the LICENSE file shipped with the extension. The open-source components bundled into it (xterm.js, its fit addon and ws) are listed with their MIT notices in the THIRD_PARTY_NOTICES.md file next to it.