Rust+ Not Working? 9 Fixes for Pairing, Connection & Notifications

First, the 30-second checklist

Before any deep fix, confirm these four things — they solve the large majority of cases:

1. You are connected to the server in-game at the moment you press the pairing button. Rust+ pairs the current server, not a server from the history list.
2. The server actually has Rust+ enabled. If pressing Esc shows no Rust+ button, or pairing never sends a notification, the server has it turned off. Nothing client-side fixes that.
3. The Rust+ mobile app is installed and signed in on a phone with a working internet connection (not the same machine).
4. You confirmed the pairing notification quickly — it expires after a short window. If you missed it, just press the pairing button again.

Symptom → cause → fix

Find your exact symptom in the table, then jump to the matching fix below.

What you see	Most likely cause	Fix
No Rust+ button in the Esc menu	Server has Rust+ disabled	Fix 1
Pairing sends no notification	Not in-game on the server, or port blocked	Fix 2
"Not paired" / server missing in app	Pairing didn't complete	Fix 3
Connects then drops (1006 error)	Expired token after wipe/restart	Fix 4
Worked yesterday, dead today	Server wiped or rebooted	Fix 4
Random disconnects under heavy use	Rust+ API rate limit	Fix 5
No push notifications / alarms silent	Phone notification or battery settings	Fix 6
Can't sign in to Rust+	Steam/Facepunch auth hiccup	Fix 7
Everything flaky on mobile only	Mobile push + sleep limitations	Fix 8

Fix 1 — The server has Rust+ disabled

Rust+ is opt-in per server. Vanilla and most community servers enable it, but some modded or locked-down hosts turn it off. If there is no Rust+ button in the in-game Esc menu, or pairing never produces a phone notification, this is almost certainly why. There is no client fix — the server owner has to enable the companion service. You can confirm by trying a different server (an official Facepunch server always has it on): if Rust+ pairs there, your original server simply has it off.

Fix 2 — Pairing sends no notification

Pairing only works while you are actively connected to that server in-game. The flow is: join the server → press Esc → click the Rust+ button (top-right of the menu) → a notification arrives in the Rust+ mobile app → tap Pair. If nothing arrives:

• Make sure the phone has internet and the Rust+ app is open or backgrounded (not force-closed).
• Check the phone's notification permissions for Rust+ (see Fix 6).
• Some restrictive server firewalls block the companion port — if every other step is correct and it still fails on one specific server, that host is the cause.

Fix 3 — "Not paired" or the server is missing in the app

If the pairing seemed to go through but the server doesn't show up, the handshake didn't complete. Re-pair: rejoin the server in-game, press Esc → Rust+, and confirm the new notification. Pairing is per player and per server, so each server you play needs its own pairing once.

Fix 4 — Connects then disconnects (the 1006 error)

A websocket 1006 close or a "connection lost" loop almost always means your pairing token is no longer valid. The usual trigger is a server wipe or restart, which invalidates old tokens. The fix is simply to re-pair from the in-game Rust+ button to mint a fresh token. This is the single most common "it worked yesterday" cause.

Fix 5 — Random disconnects under heavy use

The Rust+ Companion API has a built-in rate limit (a token bucket). If a tool — or several tools at once — polls it too aggressively, the server temporarily throttles you and connections drop. Wait about a minute, then reconnect. A well-behaved client respects the limit; if you run multiple Rust+ tools against the same pairing simultaneously, expect occasional throttling.

Fix 6 — Notifications and smart alarms are silent

Rust+ push relies on your phone delivering notifications reliably, which mobile operating systems fight against to save battery. Check all of these:

• Notification permission is enabled for the Rust+ app.
• Battery optimization is disabled for Rust+ (Android "unrestricted" / iOS background app refresh on). Aggressive battery savers silently kill background push.
• The smart alarm/device is actually paired to your Rust+ and wired correctly in-game.

If push is just unreliable on your phone, this is the strongest reason to move to a desktop client (Fix 8).

Fix 7 — Can't sign in to Rust+

Rust+ authenticates through Steam/Facepunch. A login that hangs or loops is usually a transient auth hiccup: close the app fully, confirm you're logged into Steam, and reopen. On desktop clients that use Steam OpenID, the same applies — retry the Steam sign-in and make sure your browser isn't blocking the redirect.

Fix 8 — If it's only flaky on mobile, move to the desktop

A large share of "Rust+ not working" reports are really "mobile push and the sleeping phone screen are unreliable." The companion data is fine — the phone is the weak link. A Rust+ desktop app connects to the exact same official API from your PC, so there's no battery optimization, no notification throttling, and no screen sleep. MapMonster keeps a live map, team positions, events, and vending-machine data on screen and reconnects on its own. You still pair once with the phone, then it takes over.

Fix 9 — When nothing works: rule it in or out fast

Two quick tests isolate almost any remaining case:

1. Test the server: pair Rust+ on a different server (an official one). If that works, your original server has Rust+ off or restricted.
2. Test the client: open the same pairing in a desktop client like MapMonster. If the desktop client shows live data but your phone doesn't, it's a mobile push/sleep problem (Fix 6/8), not the API.

Most people who land here after fighting the mobile app end up just running the desktop overlay — it sidesteps the two flakiest links (the phone screen and mobile push) entirely.

Download MapMonster for Windows →