Collect diagnostics for support

A useful report lets another person reproduce the same result. Collect evidence from the instance where the failure occurs.

Record the reproduction

Include:

• SkinsRestorer, server/proxy, Minecraft, and Java versions.
• Standalone or proxy setup, including the affected backend.
• The exact command or API operation.
• The complete error and expected result.
• Whether reconnecting or switching servers changes the result.
• Relevant plugins, mods, and storage type.

Create a diagnostic report

Run /sr dump from the affected instance's console. The command uploads a diagnostic report and returns a link.

The report contains configuration, platform and plugin information, and environment details. The implementation excludes database configuration and the MineSkin API key. It does not include your recent console log.

Review the report before sharing it. Other configuration or environment details can identify your setup. Do not publish unrelated credentials.

Capture recent logs

1. Enable dev.debug: true in the active configuration.
2. Run /sr reload, or restart if reload is unavailable.
3. Reproduce the problem once.
4. Copy the log from before the command through the full error.
5. Set dev.debug back to false.
6. Apply the configuration change again.

Include the full exception, rather than the final line alone. For a startup error, include the startup log too.

Ask for help

Use SkinsRestorer support with the report link, recent log, and reproduction. For a reproducible bug, open an issue.

For a documentation correction, use the page's GitHub edit link or feedback form. State the page, the step, and the result that differs.