Using it

Domain, HTTPS and reverse proxy

The simplest setup is Nginx, Caddy or Cloudflare in front of the plugin, which gives you your own domain and HTTPS.

  1. Set web.bind-address to "127.0.0.1" so only the proxy can reach the plugin.
  2. Set web.behind-proxy: true so the visitor IP for rate limiting comes from X-Forwarded-For.
  3. Set web.public-url to your public address, for example https://boards.yourserver.com. This is the link used in game and in shared links.
  4. Run /sb reload.

To serve the site under an existing domain, set web.base-path (for example "/stats") and proxy that path to the plugin.

The plugin can also serve HTTPS itself from a Java keystore (web.ssl.enabled, keystore, keystore-password). Most owners should use a proxy instead and leave this off.

No public-url set?

The in-game link is built from the server IP, the web port and the base path, for example http://1.2.3.4:8123/. If server-ip is not set in server.properties it falls back to 127.0.0.1, so set web.public-url if your links look wrong.