Wisp Panel Is Changing Resource IDs: What You Need to Do?

If you run a game hosting operation on Wisp Panel, especially if you use WHMCS or any custom automation, there is a date you need to know about: July 1st, 2026. After that date, legacy numeral resource IDs will stop working, and anything still using them will start throwing 500 and 404 errors.

If you have external integrations set up, now is a good time to get them updated.

What is Wisp Panel?

For anyone new to it: Wisp Panel is a commercial game server management panel built for hosting businesses. It lets you provision and manage game servers for clients through a web dashboard. Minecraft, FiveM, Rust, ARK, and many others are supported out of the box.

It integrates tightly with WHMCS for billing and automated provisioning, uses Docker to keep game servers isolated from each other, and gives both admins and clients a clean interface to work from. It sits in a similar space to Pterodactyl but is aimed more at hosting businesses that need a polished, ready-to-go solution.

What is changing

Wisp Panel has been working on infrastructure improvements, and part of that involved changing how resources are identified across the platform.

Before this change, resources used simple numeric IDs. Your nest might be 5, your egg might be 12, your location might be 3. Easy to read, but not great for a system that needs to scale reliably.

The new format uses prefixed string IDs. That same egg is now something like egg_01ktXXXXXXXX. Nests use nest_01kt..., locations use loc_01kt..., and so on.

This migration has already happened on the panel side. Right now both formats work. The old numeric IDs are still live as "legacy IDs" while everyone gets time to update. On July 1st, the legacy IDs are being switched off for good.

Who needs to do something

Most Wisp Panel users will not need to change anything at all. The migration is handled on the panel side, and regular server owners or end users will not notice anything different.

You need to take action if:

• You use WHMCS for client billing and automated server provisioning
• You use third-party hosting modules that reference Nest, Egg, Location, or Node IDs
• You have custom scripts or integrations that call the Wisp API and reference these resources by ID

If you manage everything through the admin dashboard and have no external systems connected to the panel, you are all good.

What you need to update

1. Update the WHMCS module

The older WHMCS module was built around numeric IDs and the v1 API. It will not work once legacy support ends.

The updated module is available on GitHub: github.com/wisp-gg/whmcs

Download the latest version and replace the modules/servers/wisp folder in your WHMCS install with the updated one. No database changes are needed and no re-provisioning of existing services is required. WHMCS tracks services by the external ID set on the panel side, and the updated module handles the new string format natively.

2. Update your product configurations

Each product in WHMCS has Module Settings that reference panel resources by ID, specifically the Nest ID, Egg ID, and Location ID. All of these need to be updated to their new string values.

To find the new IDs, go to the relevant resource page in your Wisp admin panel under Nests, Eggs, or Locations. Each migrated resource still displays its old numeral ID as a Legacy ID right next to the new string ID. So if your egg was previously 12, you can find it in the panel, grab the new egg_01kt... value, and update your product config.

Any configurable options or custom fields that store a Nest, Egg, or Location ID need the same update.

3. Check any other external integrations

If you have custom billing modules, deployment scripts, or other third-party tools that reference these IDs, go through them before July 1st. Both formats are still working right now, so you have time to test everything before the cutover.

Use the transition window

Both ID formats are resolving right now. That means you can update your product configs one at a time, test provisioning end-to-end, and confirm things are working before any clients are affected.

That window closes on July 1st.

If you have a busy WHMCS install with multiple products and eggs, leaving this to the last minute is a bad idea. A few hours of work now will save you from a stressful situation in a few weeks.

Why Wisp made this change

The Wisp team has shared that this is part of ongoing infrastructure work to improve platform performance. Moving from sequential numeric IDs to prefixed string IDs is a common step when scaling a platform. It makes IDs portable across environments, avoids collisions when data is migrated, and removes the predictability that comes with plain sequential numbers.

For most users it is invisible. For hosting businesses with external integrations, it means a one-time migration before a fixed date.

Quick summary

If you have questions about your specific setup, the Wisp Panel team is available through their support ticket system on the Wisp Discord server.

The transition window is open right now and is there exactly so this update goes smoothly. Get it done before the deadline and July 1st will be a completely uneventful day.