Published: July 30, 2026 · Reading focus: troubleshooting
When a skin does not change, avoid deleting everything first. A short diagnostic order—console, command permission, simple named skin, network access, proxy mode and cache—usually isolates the problem faster.
Read the startup log
Confirm SkinsRestorer loaded successfully. A plugin listed in a folder is not proof that it is active. Look for Java errors, missing dependencies, unsupported mappings or a message that the plugin disabled itself.
Test a simple named skin
Use a known player-name skin before testing URLs or custom files. If a named skin works, the core plugin is active and the problem is more likely URL validation, permissions or upstream generation.
Check permissions
Test as a normal player and as an administrator. A missing parent permission can deny a child action. If the console command works but the player command does not, focus on permission setup.
Useful command examples
Minimal named-skin test.
/skin NotchRefresh the current skin from its source.
/skin updateReapply a target skin when the admin command is supported and permitted.
/sr applyskin <player>Check URL requirements
For `/skin url`, use a direct public PNG, standard dimensions and quotation marks. Check configured domain restrictions and distinguish invalid-input errors from temporary rate limits.
Check firewall and DNS
The server must reach required skin services. Hosting firewalls, DNS failures or blocked domains can prevent new lookups. Use the hosting panel or provider support to verify outbound access rather than disabling security broadly.
Check proxy mode
On Velocity or BungeeCord networks, inspect proxy and backend logs. Verify forwarding, centralized configuration and database reachability. A standalone backend test does not prove the proxy path works.
Refresh without destroying data
Use update or reapply commands, then perform a controlled restart. Back up before clearing cache or dropping records. If only one client sees the old skin, compare with another client to separate server and client rendering issues.
Related SkinsRestorer guides
- SkinsRestorer Safe Download and Update Checklist
- SkinsRestorer Performance, Cache and Database Setup
- How to Install SkinsRestorer on Paper or Spigot
This guide is an independent resource. It does not replace the documentation shipped with the exact build you install. Return to the SkinsRestorer guide library or review the download safety notice.