Proxy mode and the backend API

A backend in proxy mode receives skins from the proxy. This is separate from exposing the Java API to plugins on that backend.

Ordinary proxy-managed skins

Install SkinsRestorer on the proxy and every backend. Configure profile forwarding. Leave server.proxyMode.detection at AUTO on each backend.

You do not need MySQL or PostgreSQL just because you have multiple backends. The proxy can own file storage and forward skins normally.

If backend plugins do not call the API, you can disable backend API access:

server:
  proxyMode:
    detection: AUTO
    api: false

Restart the backend, then complete the server-switch check.

A backend plugin needs the API

Set server.proxyMode.api: true. Configure the proxy and each API-enabled backend with the same MySQL or PostgreSQL database and table prefix.

File storage does not support this backend API mode. The provider can remain unavailable even though ordinary forwarded skins work.

Follow the backend API guide, then inspect database initialization logs.

Automatic detection fails

First correct the platform's forwarding configuration. If detection still fails on a known proxy backend, set server.proxyMode.detection: ENABLED there and restart.

Use DISABLED only for a genuinely standalone server or an intentional independent installation. Forcing a backend into standalone mode can produce competing skin behavior.

Where to run diagnostics

Proxy-mode backends provide /sr status and /sr dump for local diagnostics. Run storage administration and normal skin commands on the proxy.

For forwarding setup, use Velocity or BungeeCord. For the architecture, read proxy ownership.