1. Community
  2. Game Support
  3. Rust
Installing Rust:IO failed, address already in useSolved
Posted 6 years ago
Last updated 6 years ago
#1
When I updated yesterday my RustIO worked on port 28015, but since then my provider advised I add "server.port 28086" into my config file to fix another issue. Since then it will not install and It's stating address is already in use. Is there something I need to change to get it to connect to my server and the map working again or is this something Dcode is going to have to fix? I need it to connect to the 28086 port not the default port.

(12:00:31) | Updating Rust:IO ...
(12:00:32) | Rust:IO: Update complete
(12:00:32) | Installing Rust:IO ...
(12:00:32) | Rust:IO> Setting up Rust:IO 2.3.7240.2887 ...
(12:00:32) | Rust:IO> Creating directories ...
(12:00:32) | Rust:IO> Applying config ...
(12:00:32) | Rust:IO> Initializing database ...
(12:00:32) | Rust:IO> Generating map image (this may take a while) ...
(12:00:39) | Rust:IO> Generation complete
--------- Summary --------
Render       :  4405.930ms
Postprocess  :  3230.674ms
  Shadows    :    85.195ms
  FXAA       :  3123.638ms
Encoding     :    28.399ms
Other        :     5.984ms
--------------------------
Total        :  7670.987ms
(12:00:39) | Rust:IO> Starting HTTP server on 104.238.229.214:28086 ...
(12:00:39) | Installing Rust:IO failed: Exception has been thrown by the target of an invocation.
(12:00:39) | Caused by: Address already in use
(12:00:39) | Calling 'OnTick' on 'RustIO v2.16.0' took 7742ms [GARBAGE COLLECT]
(12:00:39) | Rust:IO> External IP address obtained from lookup: 104.238.229.214
Posted 6 years ago
Last updated 6 years ago
#2
That error would only show if something else is using that same port with the TCP protocol on that same IP address. It's likely another server is already using it.
Posted 6 years ago
Last updated 6 years ago
#3
I can connect to my server via that IP address, but it just won't show the map for it which is odd. This only started happening like this when my provider told me add the line server.port 28086 to my server.cfg since the update reset it back to the default for some reason.
Posted 6 years ago
Last updated 6 years ago
#4
Right, but is anyone else sharing that IP address?
Posted 6 years ago
Last updated 6 years ago
#5
5c2d88ae4ea06.jpg Wulf
Right, but is anyone else sharing that IP address?

I was told by my provider that I'm the only one using that connection combination, and they're advising I uninstall it for now. I think we'll probably just have to wait for @dcode to update it again.

Posted 6 years ago
Last updated 6 years ago
#6
From my experience this usually happens when RCON is configured to use the exact same port, so Rust:IO cannot bind to it. Try to make sure those ports do not clash, for example by using 28087 for RCON.
Posted 6 years ago
Last updated 6 years ago
#7
5b3be1821209b.jpg dcode
From my experience this usually happens when RCON is configured to use the exact same port, so Rust:IO cannot bind to it. Try to make sure those ports do not clash, for example by using 28087 for RCON.

The thing is my RCon port is 28088 but the server port was set to 28086 in the server.cfg. After changing it to 28085 in the server.cfg it started working again upon restart. I don't get why it wouldn't work for port 28086...My provider was of no help in the matter, so I said screw it and changed it one number down to see if it'd work and of course it did...I am still baffled why 28086 didn't work at all when it was fine and should have been working all along.

 

Locked automatically