Fix service connections

A skin lookup can fail because of DNS, TLS, blocked HTTPS, an upstream error, or rate limits. Record the actual error before changing firewall rules.

Narrow down the service

1. Run /sr status on the affected instance.
2. Try one known player name.
3. Try one valid skin URL if URL generation is the problem.
4. Save the matching console error.

/sr status checks account UUID and profile services. It does not check every MineSkin route, recommendations, website uploads, or your database.

If account names work but URLs fail, investigate the URL generation service and key. A green status result does not prove URL generation works.

Check local configuration

Keep advanced.noConnections: false for normal online operation. A true value prevents new external lookups, URL generation, and update checks.

Check the machine's clock and Java trust store if the error concerns TLS. Do not disable certificate validation to hide a TLS problem.

Outbound access

The server needs DNS resolution and outbound HTTPS on port 443. Allow response traffic for established connections. Skin services do not need a new inbound server port.

Use the network reference to identify the host for the failed feature. API hosts and download redirects can change between releases.

Ask the host to check connections from the actual Minecraft server environment. A successful request from your laptop does not prove the server has access.

Rate limits

Wait before repeated attempts. Keep normal cache durations. Lowering storage.skinExpiresAfter or storage.uuidExpiresAfter increases requests.

api.mojangBatchWindowSeconds controls Mojang batching. It does not increase MineSkin upload limits.

Protect proxy backends

Backend protection is a separate inbound rule. Permit connections only from your proxy or trusted network. Legacy forwarding cannot authenticate an arbitrary direct connection.

Use PaperMC's backend security guide. Keep authentication on the public proxy consistent with your server policy.

Next

Read MineSkin integration for URL generation errors. If the cause remains unclear, collect support diagnostics.