Bot Connected but No Chat or Killfeed on Rust Console: What's Actually Broken

Connected but silent is not the same as offline

There are three ways a Rust Console bot goes wrong, and they need three different fixes. It can be offline, where the socket never opened or dropped and stayed down. It can be flapping, where it connects, drops, reconnects, and never holds steady. And it can be silent, where the connection genuinely reports alive but nothing flows through it. People lump all three together and reach for the same reconnect button, which is why the silent case is the one that eats an evening.

If your bot never connected in the first place, that is a WebRCON problem, and the fix lives in the first-connection troubleshooter, not here. If it connects and keeps dropping every few minutes, that is a bot that keeps disconnecting, which is a stability issue rather than a silent one. This post is about the specific case where the status stays green and the feeds stay empty.

Silent has exactly two root causes. Either the event stream behind the socket is dead, so nothing is reaching the bot at all, or the events are reaching it fine and getting dropped into the wrong channel or blocked by a permission. Those two look identical from the outside. The next section tells them apart in under a minute.

The one test that separates a dead stream from a bad channel

You do not have to guess. You need to know one thing: is anything at all flowing through the connection right now. Open your server on your console and run a quick two-way check.

Send a harmless command from the bot that you can see land in game, like a global broadcast, and watch your own screen for it. Then type a line in in-game chat yourself and watch whether it shows up in your relay channel. While you do that, glance at whether the bot's live player count moves when someone joins or leaves.

If your broadcast appears in game and the player count tracks reality, the socket is alive and two-way. Your events are flowing, so the problem is routing or permissions, and you can skip straight to the channel checks below. If nothing you send reaches the game, no chat crosses over, and the count is frozen, the stream is dead behind a socket that is lying about being healthy. That is a stale connection, and it is the next section.

Nothing gets through: a stale socket

A stale socket is a connection that reports open while the server on the other end has stopped pushing events to it. The classic trigger on console is a host reboot. When Facepunch ships a patch, G-Portal auto-updates and reboots your server, and a bot that was connected before the reboot can hold a half-open socket that never re-subscribed to the live stream. The status light stays green because the socket technically still exists. Nothing comes through because the thing feeding it restarted underneath it. This is the same mechanism behind the bot going quiet after a restart.

The fix is one clean reconnect. Toggle the connection off and back on, or restart the bot's link to the server, so it opens a fresh socket and re-subscribes to the event stream from scratch. A healthy reconnect brings chat, killfeed, and joins back together, because they all ride the same stream.

One warning: do not hammer the reconnect button. Rust briefly rate-limits and can lock RCON after repeated failed attempts, so spamming reconnects makes the silence last longer, not shorter. Give it a few seconds between tries. If a single clean reconnect brings everything back, you had a stale socket and you are done.

Joins show but the killfeed is empty: routing and permissions

If your two-way test passed and events are clearly flowing, but one feed is missing while others work, you have a routing or permission problem in Discord. The most common version is a live join feed sitting next to an empty killfeed. That is not the server withholding kills. It is the killfeed pointed somewhere the bot cannot post.

Work through these in order. Confirm the killfeed channel still exists and its channel ID matches what the bot has, because deleting a channel and making a new one with the same name gives it a brand new ID. Confirm the bot has View Channel, Send Messages, and Embed Links in that exact channel, since most killfeeds post as embeds and a missing Embed Links permission makes the post fail silently with no error you will ever see. Check for a channel-level permission override, not just the server role, because a category can quietly block the bot in one channel while every other feed works fine. Rule out slow mode and a muted bot while you are there.

This is worth getting right once, because a clean killfeed is the backbone of a good server. If you want the full setup, the way rewards attach to kills, and the channel layout that keeps it readable, the Rust Console killfeed bot guide covers it end to end.

The chat relay is a separate switch

Chat and killfeed ride the same stream, but they are usually two different toggles pointed at two different channels. So it is completely normal to have a working killfeed and a silent chat relay at the same time. If kills show up but player chat never crosses into Discord, the relay itself is the thing to check, not the connection.

Confirm the relay is turned on, mapped to a real channel that still exists, and that the bot has the same three permissions there: View Channel, Send Messages, and Embed Links. Remember that a relay often runs one direction by default, console chat into Discord, so if you were expecting your Discord messages to appear in game and set nothing up for that, the quiet is just an unset option, not a fault.

Make sure you are watching the right server

This one catches owners who run more than one server or who moved hosts recently. If the bot is connected to a different server than the one on your screen, everything looks healthy because it genuinely is connected. It is just watching a server you are not standing on. No amount of channel fixing will help, because the events you are waiting for are happening somewhere the bot is not looking.

Check that the bot's connection points at the exact server you are playing on. On a direct WebRCON host like G-Portal that means the IP and RCON port; on a one-click account link it means the host account and the specific server you picked. If you migrated hosts, or spun up a wipe on a new instance, the old connection details will happily keep a green light on the wrong box. And if it never connected at all, that is a different story, usually the game port used where the RCON port belongs, which is a connection fault rather than a silent one.

How to stop the feed from going quiet again

The root problem behind most silent bots is simple: a socket can report connected while the stream behind it is dead, and a lot of bots only watch the socket. They see green, they call it healthy, and they never notice that no events have arrived in twenty minutes. So every time your host reboots for a patch, you get another quiet evening until you spot it and reconnect by hand.

The fix is a bot that watches the event flow, not just the connection. It should reconnect and re-subscribe on its own after a host reboot, and it should treat a stream that has gone silent as a fault worth acting on, not a healthy state. Vantic does exactly that: it reconnects automatically after a G-Portal patch reboot and brings your killfeed and chat back without you touching anything, so connected always means events are actually flowing. That is the difference between a status light and a feed you can trust.

Frequently asked questions

Keep reading

the Rust Console killfeed bot guide · when the bot goes quiet after a restart · fixing a bot that keeps disconnecting · the WebRCON first-connection troubleshooter · connecting a G-Portal Rust Console server