RUST PULSEWiki
Reference

Troubleshooting

Common issues across all Rust Pulse services and how to resolve them.

I paired but no servers show up on the dashboard

  1. The FCM listener reconciles every ~30s. Wait a minute and refresh.
  2. Check the Credentials Helper still has a green "connected" status. The FCM session can disconnect when your laptop sleeps.
  3. Visit your dashboard's Setup tab — if the helper status is "credentials missing", re-run the helper.
  4. If the dashboard says "credentials installed but no pairing" check that you actually paired in-game (ESC → Rust+ → Pair with Server). Pairing failure is silent in Rust+ — sometimes the click registers, sometimes it doesn't.

Bot doesn't reply to team chat commands

  • Confirm the bot is enabled in Settings → Bot.
  • The bot needs Bot enabled AND at least one team member must have been online at some point this session for the relay to subscribe.
  • For premium-only servers, confirm the owner's subscription is active (Operator+).

Discord events post in the wrong channel

  • Open dashboard → Discord tab → review channel routing.
  • Each event family has its own channel pick. The bot uses what you configured here, not channel names.

!translate says "not configured"

!pulse says "Pulse AI not configured"

  • GROQ_API_KEY is missing from the API's env.
  • Free tier from console.groq.com.

Overlay shows "Premium required" after signing in

  • Owner: confirm your subscription is ACTIVE and tier is OPERATOR or higher.
  • Guest: confirm the host's subscription is eligible and that you've been invited as a guest on the specific server.

Relay constantly reconnecting

  • Facepunch rate-limits Rust+ connections per Steam ID. With many active sessions you can hit the cap.
  • Solution: disable always-online on servers you don't actively care about.

"Code expired" when activating the helper

  • Codes expire 10 minutes after issue. Generate a fresh one from the dashboard.

Browser blocks the API endpoint

  • The API requires its session cookie. Cross-domain requests from third-party tools need credentials: 'include' on fetch.
  • The CORS allowlist is FRONTEND_URL + ADMIN_ORIGIN. Custom origins are not permitted in v1.

Admin returns 503 on every endpoint

  • ADMIN_STEAM_IDS is empty on the API env. By design — admin is disabled until you add at least one Steam ID.
  • Add your Steam64 to ADMIN_STEAM_IDS (comma-separated for multiple admins), restart the API.

Need help