Free tools Windows power users keep installed
One-click scans. No signup required.
To pair Rust+ with a server you run, set a reachable companion-app port in server.cfg, set the server’s public IP, restart, and then pair from inside Rust. The required sequence is: configure app.port (10,000 or higher), configure app.publicip with an IP address only, make that TCP port reachable from the internet, restart the server, choose Esc → Rust+ → Pair with Server, and approve the pairing in the phone app.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Rust servers with free DDoS protection and up to three free backups a day.
What Rust+ pairing actually requires
Rust+ is the companion app connection for a Rust server. The app does not pair through the normal game connection port alone. Your server also runs a companion service that listens on an app port. The Rust+ backend must be able to reach that port over the internet before the phone can complete pairing.
As an Amazon Associate I earn from qualifying purchases.
There are four separate conditions to satisfy:
- The server must be running and joinable in Rust.
app.portmust be set to a port accepted by the Rust+ backend. The official Rust Wiki specifies 10,000 or higher.- The companion port must be reachable from the internet over TCP. On a home server, this means router forwarding as well as a host firewall rule. On rented hosting, it usually means using the port assigned in the control panel.
- The server must advertise the correct public address through
app.publicip, then be restarted after configuration changes.
Pairing is a two-stage action: first authorize the server from the in-game menu, then accept it in the Rust+ phone app. Completing only one of those stages does not finish the pairing.
Choose the correct companion port
The official default calculation
When you have not selected a custom app port, the official default is calculated from your server ports: add 67 to the game port or the RCon port, whichever produces the larger value. With the unchanged default game and RCon ports, that calculation results in 28082.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
| Item | Value or rule | What it means |
|---|---|---|
Minimum custom app.port |
10,000 | Ports below this threshold are not accepted for reachability by the Rust+ backend, according to the official Rust Wiki. |
| Default calculation | Game port + 67, or RCon port + 67, whichever is larger | The companion service chooses the larger resulting number when no custom port is supplied. |
| Typical unchanged defaults | 28082 | This is the calculated companion port when the standard game and RCon ports have not been changed. |
| Protocol to expose | TCP | The companion listener must be reachable over TCP from the public internet. |
Do not assume that 28082 is correct for every installation. Changing either the game or RCon port changes the default calculation, and rented server providers may assign a different app port. The definitive value is the one shown by app.info on the running server or by the provider’s App Port field.
Hosted server versus a server at home
| Where the server runs | How to determine the port | Network work you control |
|---|---|---|
| Rented or managed host | Read the host panel’s App Port field or run app.info in the server console. |
Use the assigned port and follow the host’s firewall or port-allocation controls. Do not substitute 28082 unless the panel or console shows it. |
| Self-hosted at home | Choose an unused port of at least 10,000, or confirm the calculated port with app.info. |
Forward that TCP port from the router to the server’s private address and allow it through the server and router firewalls. |
| Container deployment | Check the container’s published port and the value reported by the server. The didstopia Rust server image uses 28082 by default and exposes an override through RUST_APP_PORT. |
Publish the same TCP port through the container runtime, host firewall, and router if the machine is behind a home gateway. |
A port can be open locally and still be unreachable from outside your network. Pairing depends on the public path all the way from the Rust+ service to your machine.
Recommended Free Tools
Configure server.cfg
Set app.port
Open the server’s server.cfg and add or edit the companion-port setting. Use a free TCP port at 10,000 or above. For example:
app.port 28082The number in this example is appropriate only when it is actually available and matches the port you intend to expose. If another service already occupies it, select another qualifying port and use that same number in every place: the configuration file, the host panel or container mapping, the router forward, and the firewall rule.
Set app.publicip when the advertised address is wrong
app.publicip tells the companion service which public address the app should use. Enter an IP address only; do not append a colon and port number. A valid form is:
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
app.publicip 203.0.113.25The address must be the public IP through which the server is reachable, not the machine’s private address such as a 192.168.x.x or 10.x.x.x address. If the server has multiple network interfaces, a VPN, or another unusual route, an incorrect automatically detected address can make the app look for the wrong endpoint. In that situation, set app.publicip explicitly.
Use app.listenip only for unusual networking
app.listenip controls the local interface on which the companion service listens. Most installations do not need it. If your machine has unusual routing or multiple interfaces and the service is binding to the wrong one, set it to the server’s public IP as directed by the official Rust Wiki. Do not use app.listenip as a replacement for the router forward or firewall rule; it changes the local bind address, not the public network path.
Keep the three values logically separate
app.portis the TCP port number.app.publicipis the public IP address, with no port appended.app.listenipis an optional local listening-address override for special network layouts.
Putting a port into app.publicip, choosing a value below 10,000, or changing the file without restarting are common reasons a correct-looking configuration has no effect.
Verify what the running server is using
After the server is running, open its server console and run:
app.infoThe command reports the companion port in use. Treat that output as authoritative for the current process. It catches situations where a startup parameter, host template, container environment variable, or configuration edit caused the server to use a different port than expected.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Before troubleshooting the app, confirm all of the following:
- The displayed app port is at least 10,000.
- It matches the port opened in the host panel, router, container mapping, and firewall.
- The server is fully started and can be joined normally from the Rust client.
- The public IP configured in
app.publicipis the address your internet connection actually presents to the outside world.
Open the companion port to the internet
Self-hosted server behind a router
- Give the Rust server machine a stable private address, either with a static configuration or a DHCP reservation. A forwarding rule aimed at a changing private address will eventually point to the wrong computer.
- Create a router port-forward rule for the exact TCP number shown by
app.info. Forward the external port to the same port on the Rust server’s private address unless your network design deliberately uses a different internal mapping. - Add an inbound TCP rule to the operating system or hardware firewall on the server machine.
- If you run a separate firewall appliance, cloud security group, or container host firewall, allow the port there as well.
- Save the network changes and test from a network outside the home LAN. A test made from inside the same network can succeed because of local routing while the public path remains closed.
The official requirement is that the TCP port on which the companion server listens be reachable over the internet. Port forwarding is therefore an additional requirement for a typical home installation, not a substitute for app.port.
Rented or managed server
Managed hosts often reserve an app port for each instance. Find the panel’s App Port value instead of calculating a number from the standard defaults. If the panel does not display it, run app.info in the server console and ask the host to confirm that the reported TCP port is externally reachable. Some providers prevent customers from changing this value; in that case, use the assigned port consistently rather than forcing a custom one.
Container deployment
A container adds another mapping layer. The value inside the Rust process, the published host port, and the externally opened port must line up. The didstopia Rust server image documents 28082 as its default and supports overriding it with RUST_APP_PORT. If you override that environment variable, publish the replacement TCP port through the container runtime and expose the same external port on the host network. A mapping that exists only inside the container is not publicly reachable.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRestart after configuration or network changes
Changes to the app port and public IP take effect only after a server restart. Stop the server cleanly, allow the process to exit, and start it again using the normal launch method for your host, service, or container. Once it is back online, run app.info again rather than relying on an old console line.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Restarting also prevents a misleading test in which the configuration file contains the new value but the running process still owns the old port. If you changed a provider-side allocation, restart after the panel reports the new assignment.
Pair from Rust and the phone app
Start with a normal game connection
Join the server in Rust first. The server should be running and joinable before you attempt pairing. If you cannot enter the game server, resolve that availability problem before investigating Rust+; the companion workflow depends on a live server.
Authorize the server in the game client
- While connected to your server, press Esc.
- Open Rust+ from the pause menu.
- Select Pair with Server.
This action initiates the pairing request from the game session. If the menu uses different wording after a game update, look for the Rust+ screen’s server-pairing action; the exact labels are version-sensitive.
Approve the request on the phone
- Watch for the Rust+ push notification and accept it, or open the Rust+ app directly.
- If the server is listed, choose Pair Server.
- Complete the confirmation shown by the app.
After approval, the server should appear as a paired server in the app. Keep the game server online while completing both stages. If the app does not list it, return to the network and port checks rather than repeatedly pressing the pairing control.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot Rust+ on a self-hosted server
The “Pair with Server” option is missing
- Confirm you are connected to the intended Rust server, not at the title screen or in a different server session.
- Verify the server is fully started and joinable. The pairing control may not be useful until the game session is connected to a live server.
- Check whether the Rust client or server build changed the menu labels. The documented path is Esc, Rust+, then Pair with Server, but labels can change between versions.
- Restart the server after adding the app settings, reconnect in Rust, and check the menu again.
The server is not visible in the phone app
- Run
app.infoand record the active companion port. - Compare that number with
app.port, the host panel or container mapping, the router forward, and every firewall rule. - Confirm the number is 10,000 or higher and that the rule is TCP rather than only UDP.
- Check
app.publicip. It must contain the public IP only and must not point to a private LAN address. - Test from outside the local network. Internal tests can bypass the public route.
- Make sure the server is still joinable in Rust, then restart it if any value was corrected.
The app finds the server but pairing fails
Discovery and completion still depend on a stable public route. Verify that the public IP has not changed, especially on a home internet connection, and that the router forward still targets the current private address of the server machine. Check that the port shown by the newly restarted process is the one exposed externally. A firewall rule allowing a previous custom port will not allow a newly selected one.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
If you recently changed the app port, the Rust+ app may retain the old server record. One community troubleshooting report recommends deleting the server entry in the phone app and pairing it again after the port change. This is a recovery step rather than a substitute for opening the new port.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Pairing worked until the server moved or the port changed
A changed public address or companion port can invalidate the app’s saved endpoint. Recheck app.info, update app.publicip if the public address changed, update forwarding and firewall rules, restart, and then remove and re-pair the server in the phone app if the old entry does not reconnect.
The server works locally but not from the internet
This pattern points to the network edge rather than the in-game pairing menu. The companion process may be listening correctly while the router, host firewall, container publication, or provider allocation blocks inbound TCP traffic. Verify each layer in order: process, host port, operating-system firewall, router or security group, then external reachability. Do not conclude that the port is open because a local client can join the game server.
Common configuration mistakes
| Mistake | Why it breaks pairing | Correction |
|---|---|---|
| Using a port below 10,000 | The official Rust+ backend requirement is 10,000 or higher. | Select a qualifying unused port and expose that exact TCP port. |
| Assuming 28082 on every server | The default is calculated from game/RCon ports, and hosts may assign another value. | Use the host panel or app.info. |
Writing IP:port in app.publicip |
The setting expects an IP address, not a combined endpoint. | Put only the public IP in app.publicip; keep the port in app.port. |
Editing server.cfg without restarting |
The running process keeps its previous values. | Restart, then verify with app.info. |
| Forwarding UDP only | The companion listener must be reachable over TCP. | Add or correct the TCP rule. |
| Forwarding to a changing private address | The router eventually sends traffic to the wrong machine. | Reserve a stable LAN address for the server. |
| Opening the port only inside a container | Internal container reachability does not publish the service publicly. | Publish the port on the host and open it through every network layer. |
A reliable pre-pair checklist
- Rust server starts without configuration errors.
- You can join the server normally in Rust.
app.portis present and is at least 10,000.app.publicip, if needed, contains the correct public IP only.app.listenipis used only when the server has an unusual interface or route.app.infoconfirms the port you believe you opened.- The exact port is allowed as inbound TCP in the operating-system firewall.
- A home router or other network edge forwards the port to the server’s stable private address.
- A host panel, security group, or container runtime is not blocking or remapping the port unexpectedly.
- The server was restarted after every configuration or port change.
- You are using Esc → Rust+ → Pair with Server in a live game session.
- The phone app is open and ready to accept the pairing request.
What to verify after a successful pairing
Record the app port reported by app.info, the public-IP setting used, and the private address targeted by your forward. This small record makes future maintenance easier when a host changes allocations, a router lease changes, or you migrate the server to another machine. If the public IP changes, update the setting and restart before attempting to pair again.
For a self-hosted setup, keep the router rule and firewall rule tied to the same stable destination. For a hosted setup, check the provider panel whenever the instance is recreated or moved. For a container, keep the environment variable, published port, and external firewall rule synchronized.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteVersion and availability caveat
The port requirement and configuration names above follow the official Rust Wiki guidance available for this article. Rust server builds and the Rust+ app can change menu labels or default-port behavior, so check the current official documentation if your installation shows different labels or if app.info reports a different default. The operational rule remains the same: use the port reported by the running server, make that TCP port publicly reachable, restart after edits, and complete authorization in both the game and phone app.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
