Simply create a new WebSocket request and type in the Rust server's IP address and companion server port into the 'Server URL' field. You can use a tool like Postman to test connections to the companion server. The most straight forward way to test is by pairing with the app itself - but if you have many servers there's an easier way. If everything is still broken you can submit feedback using this form. If you get errors about companion server registration or push notifications aren't working then make sure your server can access over the internet. If the IP address that the app connects to is incorrect, you can set it app.publicip to the value you need. You can check the connection settings the server is currently using with the app.info command. If you have a more complicated networking setup where you need to specify which NIC to listen on then you'll need to set the app.listenip convar to your Rust server's public IP address. You will need to restart your Rust server for the port change to take effect. This port must be 10000 or higher for it to be successfully reached by our Rust+ backend. If you need to switch it to something else, you can specify the port to use in the app.port convar. You can use the app.info command on your server to show what port the companion server is using. If you haven't changed any ports that means it will be 28082. The default port is the game port + 67, or the RCon port + 67, whichever is the larger number. Port forward, open it, add firewall rules for it, done. Making it workįor most people, the only requirement for the companion server to work is to make the TCP port the companion server listens on accessible over the internet. They will see it loading for a while before it says the server is offline. If something is wrong with it then nobody will be able to view your server in Rust+, even if they pair with it. The Companion Server is what Rust+ uses to communicate with Rust servers.

Offlinetv rust server ip