7DPanel

English

简体中文

English

简体中文

Appearance

Troubleshooting ​

The panel does not open ​

Confirm the game server is running, the 7DPanel Mod loaded, and the deployed package contains wwwroot/index.html. Use the host and port from data/config.json; the default client URL is http://<server-host>:8088/. A + in listenUrl is a listener wildcard, not a browser address. Check the game server log and host firewall if the URL still fails.

Sign-in fails or a session expires ​

Use the username and password currently stored in the installed Mod's data/config.json. If you changed them, restart the server. A failed refresh or an HTTP 401 clears the browser session; sign in again. An HTTP 403 means the current request was rejected by authorization rather than a connection failure.

Steam login is unavailable ​

  • If the button is disabled with an address warning, set publicBaseUrl to the browser origin shown by the page, restart the game server, and refresh. Changing only the frontend address does not change the callback.
  • If no usable Steam option appears, check steamLoginEnabled, game registration, and the explicit public origin. Password login can still be used.
  • If verification succeeds but access is denied, confirm the player has joined the current save and has an individual effective permission level of 0. Group membership is insufficient.
  • If external verification fails, check outbound HTTPS connectivity to Steam and any httpProxyUrl configured on the game host. A configured but unreachable proxy does not fall back to direct access.

Behind a reverse proxy, keep the start and callback on the same browser origin and forward /oauth unchanged. After a restart, begin a new login attempt; unfinished attempts do not survive it. See Panel connection settings.

A game action reports initialization ​

The API can answer before the game finishes loading. Wait for the server to become ready, then refresh the page. The Overview helps distinguish a starting server from a failed data panel.

New data is missing ​

Check the active world and save, plus any page filters. Player history is scoped to the current world and save; the Backups record list may include previous ones. Chat history can lag behind a just-sent message because persistence is asynchronous. Use the page's refresh action before concluding data was lost.

A backup cannot be restored from the panel ​

This is expected: 7DPanel records online copies for manual restoration only. Follow Backups and stop the game server before replacing native save files.

A Shop product is missing or a purchase is uncertain ​

For missing products, check the shop switch, product enablement, filters, and whether its native definitions remain loaded after Mod changes. The management catalog retains unavailable definitions for repair. For delivery problems, open the purchase details and compare the Economy charge, action outcomes, and attempt evidence. Timeouts and partial delivery can mean an effect already applied; follow Shop instead of repeatedly buying or redelivering.

One player's inventory cannot be loaded ​

A corrupt saved inventory is reported for that player without preventing unrelated queries. Check the game's log and the player's native save files, and preserve backups before repair. A profile reset deletes data and has no restore endpoint; it is not a routine refresh action.

Reconnect after a frontend/Mod update to receive the current game interface. Open the chat input before clicking links in chat output. Check publicBaseUrl, the /player/* frontend fallback, and /api and /oauth proxy routes. New code requests require enabled 7DPanel Chat and a usable public origin; the player must be online. The login page reports the effective command and offers retry if its login-options query fails. Request a fresh code after expiry or reuse; the six-character code lasts two minutes and is single-use. See Player center.

Buying or claiming a daily reward is disabled ​

Read the reason beside the action and refresh the page. Check Economy enablement, daily reward enablement, account-query errors, balance, product cooldown, daily allowance, and whether the reward was already claimed in chat. Both actions require being online. After a lost purchase response, resolve the retained pending request using the same retry flow; do not start another purchase to work around it.

Travel history is empty or unavailable ​

Clear filters and check the current world and save. Only attempts recorded after deployment of the matching backend appear; console and other-Mod teleports are excluded. If the history request returns 404, deploy a matching frontend/backend package. Empty history does not prove that no travel occurred. Accepted records do not confirm arrival; see Teleportation.