compatibility guide

SkinsRestorer Proxy Setup for Velocity and BungeeCord

Configure SkinsRestorer proxy mode for Velocity or BungeeCord with forwarding, backend communication, shared data, status checks and migration safety.

SkinsRestorer Proxy Setup for Velocity and BungeeCord original feature illustration

Published: July 30, 2026 · Reading focus: compatibility

A proxy network should not be configured like several unrelated single servers. SkinsRestorer proxy mode centralizes commands, configuration and skin data so a player can move between backend servers without losing consistency.

Use the proxy installation path

Install the build and components required by the official proxy instructions. The proxy handles the central command and API flow. Backend servers still need the documented integration so they can receive and apply skin information.

Configure player forwarding

Velocity or BungeeCord player information forwarding must be correct before debugging SkinsRestorer. If identities are not forwarded consistently, commands, UUID mapping and server switching can appear unreliable.

Keep configuration consistent

Proxy documentation requires coordinated configuration between the proxy and backend servers. Make changes in the intended central location and avoid leaving stale copies with conflicting proxy-mode settings.

Useful command examples

Inspect detected mode and current integration status.

/sr status

Test command forwarding through the proxy.

/skin <name>

Confirm GUI access remains available across backends.

/skins

Plan shared storage

A MySQL database can provide consistent skin data across multiple machines. Use one dedicated database, strong credentials, backups and network access limited to the servers that need it.

Verify server switching

Test a skin change on one backend, switch to another backend, reconnect and repeat with a normal player account. This proves more than a single operator test on the lobby.

Use status and logs

Run the status command supported by your build and inspect both proxy and backend logs. A backend-only error may not explain a forwarding failure, while a proxy-only log may not show an application problem.

Migrate without data loss

Back up local skin data and the database before enabling proxy mode or changing storage. Move one staging copy first, verify player history and defaults, then schedule the production change with a rollback window.

Related SkinsRestorer guides

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.