Repository navigation
Troubleshooting
Marvin Honé edited this page Nov 3, 2026
·
1 revision
First make sure you use the newest plugin version. The Plugin Changelog lists what changed.
The Dashboard shows Not connected, and players get "The SkinCreator service is currently unavailable".
- Check
Server_Id,Licence_IdandServer_Secretinplugins/SkinCreator/config.yml. The easiest way is the Copy config button in the Dashboard (your server → Plugin & setup). Restart the server afterwards. - The plugin logs an error at startup if a value is missing or invalid. Look for
SkinCreatorin the server log. - If you lost the Server Secret or aren't sure it is correct, regenerate it in the Dashboard and enter the new one.
- Plugin versions 1.0.0 and 1.0.1 can't connect anymore. Update the plugin.
- Leave
Backend_UrlandFrontend_Urlempty. - Your server must be able to reach
api.skin-creator.com(port 443).
- licence expired: The licence of this server has expired. Renew it or select another licence in the server settings.
- Otherwise a limit of your plan may be exceeded, e.g. too many servers or IPs. See Plans and Limits.
- In networks (BungeeCord, Velocity): If SkinsRestorer is installed on the proxy, it can overwrite the skins when players switch servers. Remove it from the proxy. SkinCreator must be installed on every backend server.
- Other skin plugins can overwrite the skins as well. Remove them or turn off their skin features.
- Spigot and Bukkit: If a player sees the new skin only after rejoining, the server log contains a warning. Please send it to us.
- Saving a skin takes a moment, because it is signed by MineSkin. If it often fails or is slow, add your own MineSkin API key.
- Is the pack enabled on this server? See Server Settings.
- Is the part enabled, and does it fit the player's model (Classic/Slim)?
- Does the player have all required permissions? After changing permissions, the player has to run
/skincreator editagain.
The server has a default skin with Block vanilla/minecraft.net skin reset turned on.
Set Debug_Logging: true in the config.yml, restart the server, reproduce the problem and send us the server log via an issue, Discord or info@skin-creator.com. Turn debug logging off again afterwards.