Debugging and Logs

SkinsRestorer provides commands and logs that show errors and connection problems.

Debug mode

Enable debug logging to record API requests and internal actions.

dev:
  debug: true

Then restart the server or reload the plugin:

/sr reload

Debug mode records:

• All API requests to Mojang/MineSkin/SkinsRestorer endpoints
• Skin data processing steps
• Cache hits and misses
• Plugin messaging channel communication

Using /sr dump

Run /sr dump to collect support information:

/sr dump

The command uploads:

• Server and plugin version information
• Your configuration (sensitive data redacted)
• Recent relevant log entries
• Installed plugins list
• System information

The command returns a URL such as https://bytebin.lucko.me/xxxxx. Send this URL to support.

Using /sr status

Use this command to show the connection status of required API endpoints:

/sr status

The command shows:

• eclipse.skinsrestorer.net - UUID and profile lookups
• axolotl.skinsrestorer.net - MineSkin URL decryption
• cool-skins.skinsrestorer.net - Recommended skins
• Mojang API endpoints
• MineSkin API (if configured)

If an endpoint is unavailable, use the firewall guide.

Understanding log messages

Startup messages

Healthy startup:

[SkinsRestorer] +==================+
[SkinsRestorer] |   SkinsRestorer  |
[SkinsRestorer] |------------------|
[SkinsRestorer] |    Server Mode   |
[SkinsRestorer] +==================+

or for proxy networks:

[SkinsRestorer] |    Proxy Mode    |

Warning messages:

[SkinsRestorer] Proxy mode files are deprecated, please use the config file instead.

This warning means that old .txt configuration files exist. Move their values to config.yml.

Common log errors

Connection errors:

[SkinsRestorer] Failed to connect to eclipse.skinsrestorer.net

Make sure that the firewall permits the required connections.

Rate limit errors:

[SkinsRestorer] Rate limited by Mojang API

SkinsRestorer sends this request again automatically.

Database errors:

[SkinsRestorer] Failed to connect to database

Make sure that MySQL is available and the credentials are correct.

Log file locations

Filtering logs for SkinsRestorer

Use the command for your operating system to find SkinsRestorer messages.

Linux/Mac:

grep -i skinsrestorer logs/latest.log

Windows PowerShell:

Select-String -Path logs/latest.log -Pattern "skinsrestorer" -CaseSensitive:$false

Common debugging scenarios

Skin not applying

1. Enable debug mode.
2. Run /skin <playerName>.
3. Find these messages in the log:
   • "Fetching skin data for...": The API request started
   • "Received skin data...": SkinsRestorer received the data
   • "Applying skin to...": SkinsRestorer started to apply the skin
   • Any error messages

Proxy mode issues

1. Find "Proxy Mode" or "Server Mode" in the startup log.
2. Run /sr status.
3. Make sure that security plugins permit SkinsRestorer plugin messages.

API connectivity issues

1. Run /sr status.
2. If an endpoint is unavailable, examine:
   • Firewall rules
   • DNS resolution
   • Proxy/VPN interference

Getting support

When you ask for help:

1. Run /sr dump and include the link.
2. Describe the expected result and the actual result.
3. Include the error messages from the log.
4. Include the server platform and version.

Support channels:

• Discord
• GitHub Issues