Relay connection problems in Revolution Macro

Relays can fail to connect your Revolution Macro accounts because of configuration or network problems. If a relay times out, a join code fails, or your alts ignore Main, the relay setup may be blocking the connection. This guide covers common fixes that may resolve those problems.

Before you start

For multi-account tools to work, every instance of Revolution Macro needs to be connected to each other. When all your accounts are connected, each user will be displayed in Settings → Networking under the People tab. Your relay must be properly configured before starting Vic Hop, Tad Sync, RBC Gather, or other multi-account based tools.

For the full relay setup tutorial, see Connect accounts with relay.

dial tcp i/o timeout / Can’t connect alt to relay

Cause: The client cannot reach the host relay. Hosting Local and Cloud at once on the same account, or the wrong relay type in Advanced → Mode, is the most common conflict.

Fix:

1. On the host, stop any active relay before switching type. Open Advanced → Mode and choose Local for same-network connects, or Cloud when accounts are on different networks.
2. Confirm the host shows Active and each client joined so People lists everyone connected. Follow Connect accounts with relay if Start or join is not done yet.
3. If the host never appears under Relays, click + → LAN Address and enter the host LAN IPv4. Read that address with Find the host LAN IP. Use 127.0.0.1 only when every Revolution window is on that same computer.
4. Allow Revolution through the OS firewall on the host when using Local Relay.

If that still fails

If Local Start fails with A relay is already running on your computer. You can only host a single relay at a time., stop the other Local relay on that PC first. A failed connect will show a dialog that starts with Failed to connect to.

Join code does not work / Cloud relay join fails

Cause: The join code expired or was mistyped, or the client is not signed in for Cloud. Join Policy may block the client until the host approves.

Fix:

1. On the host, confirm Cloud is Active and copy a fresh Join Code. Stop any Local relay on that account before starting Cloud. See Connect across networks (Cloud) for Start and Join Code.
2. On each client, sign in, click + → Join Code, paste the fresh code, and click Join. An invalid code shows Enter a valid 6-character join code. Signing out prompts Sign in to join a cloud relay.
3. If Join Policy is not Open, approve the pending request on the host under Pending. Clients may see Waiting for host approval… until you Admit or Trust them.

If that still fails

If the code still fails, the host can regenerate a fresh Join Code. Stop cloud relay disconnects all members. For Join Policy setup, see Connect accounts with relay.

Tad Sync enabled but alts ignore Main

Cause: Main and Tad Alt are not on the same Active relay, or Role is wrong on Tools → Tad Sync → General.

Fix:

1. Put every account on the same relay (People shows connected) under Settings → Networking.
2. Set Role to Main on the booster account and Tad Alt on each follower (Tools → Tad Sync → General).
3. Turn Enabled on for each account that should participate.

For tool setup beyond relay connection, see Set up Tad Sync. If Vic Hop Searchers never pull Main in and People is empty, see Vic Hop failures.

Known limitations

• Local Relay and Cloud Relay cannot both be Active on the same account.
• Only one Local Relay can bind port 1234 per PC.
• Auto-Start and Auto-Connect are mutually exclusive. Turning one on turns the other off.
• When not signed in, you cannot host or join Cloud Relay. Local relays still work.

If you’re still stuck

Note whether you use Local Relay or Cloud Relay, both OS platforms, and whether People ever showed connected. Then:

1. Open Status, set Log Level to 4, and click the clipboard icon (Copy Logs).
2. Include your Revolution version from Settings → Credits.

Related

Connect accounts with relay

Set up Tad Sync

Vic Hop failures