To begin with, can you please provide more detailed reproduction steps? At the moment, it’s difficult to understand what exact steps you’ve taken and where the problem may lie.
Also, unfortunately, I’m unable to view images. Could you please describe your issue or provide a direct text transcript of any error messages you’re experiencing?
To start diagnosing the issue, could you do a quick test to check if the server port is listening? You can do this by going to your command prompt and typing:
ampinstmgr ports [YOUR INSTANCE NAME]
Please replace [YOUR INSTANCE NAME] with your actual instance name.
This will let us know if the server is active and ready to accept connections.
[Info] AMP Instance Manager v2.4.6.6 built 05/10/2023 11:57
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] Port usage for ServerSvet01 (ServerSvet)
[Info] Instance is currently not running.
[Info] LISTENING 8081 TCP (Core.Webserver.Port)
[Info] CLOSED 28015 UDP (RustModule.Rust.Port)
[Info] CLOSED 28016 UDP (RustModule.Rust.QueryPort)
[Info] LISTENING 5678 TCP (RustModule.Rust.RconPort)
[Info] CLOSED 28082 TCP (RustModule.Rust.AppPlusPort)
[Warning] Some of the ports required by this instance are currently in use, which will prevent this instance from functioning correctly.
The output indicates that the instance is currently not running and some of the required ports are not open (28015, 28016, 28082). This may be the root of your connectivity issues.
You can try to start your instance by running:
ampinstmgr start ServerSvet
After you run the command, please check again the status of the ports by running:
ampinstmgr ports ServerSvet
Additionally, make sure there is no other software on your machine using those ports and that your firewall is not blocking these ports.
[Info] AMP Instance Manager v2.4.6.6 built 05/10/2023 11:57
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] Starting Instance: ‘ServerSvet01’
[Error] This instance can only be started by ADS (AMP’s main web interface) - it cannot be started via the command line.
[Info] This instance failed to start. Run ‘ampinstmgr LastLog ServerSvet01’ to view it’s most recent log.
Apollo - there’s a bug on Windows where instances sometimes show as offline even when they’re running. The RCON port is open but the game port isn’t. I suspect being Rust that the server is simply taking a really long time to start as it often does for the first time.
Thanks for pointing that out. It is indeed a known issue with Rust and other ports-intensive games on AMP.
Luckily, you can find your instance's logs, which may provide more details. In command prompt, run:
ampinstmgr lastlog ServerSvet01
Could you also try connecting to the server? Rust and some other games don't fully open their ports until the first player tries to join. When you attempt this, please let me know what happens or if you get any error messages.
Thanks for the info, but as I mentioned earlier, I am unable to view images. Can you please describe what is shown in the image or share the context provided in it? More specifically, it would be helpful to know what you see in the AMP server status page.
However, since your previous post mentioned an issue with the 'ServerSvet01' instance, this might indicate that there is a misunderstanding between the instance status and the game server status.
A 'running' instance only signifies that the AMP application controlling your game server is operational. It doesn't necessarily mean that the game server itself is working. On the AMP interface, the actual game server status is normally indicated separately.
If you were able to see the console output of your Rust server in AMP, what does it show there?
[AntiCheatClient] EOS_AntiCheatClient_BeginSession: A session is already active.
Found 0 server query results, attempting direct connect…
Connecting: 193.165.142.26:28082 (Raknet)
Connecting: 193.165.142.26:28082 (Steamworks)
It looks like Rust's AntiCheat system is saying a session is already active, which shouldn't be preventing you from connecting. The potential issue here might be that you're trying to connect using port 28082.
Port 28082 is typically the Application Plus port; for the game itself, you usually need to use the game port, which in your case should be 28015. So, once more, please try to connect using:
client.connect 193.165.142.26:28015
Let's see if this helps with your connection issue.
client.connect 193.165.142.26:28015
Found 0 server query results, attempting direct connect…
Connecting: 193.165.142.26:28015 (Raknet)
Connecting: 193.165.142.26:28015 (Steamworks)
Disconnected (Disconnected) - returning to main menu
got title filename: D:\SteamLibrary\steamapps\common\Rust\temp\c17427ec2c1144d2f72ba09ac0397e26.png
Playing Video D:/SteamLibrary/steamapps/common/Rust/RustClient_Data/StreamingAssets/MenuVideo/attackhelicopter.mp4
client.connect 193.165.142.26:28015
Found 0 server query results, attempting direct connect…
Connecting: 193.165.142.26:28015 (Raknet)
Connecting: 193.165.142.26:28015 (Steamworks)
Disconnected (Disconnected) - returning to main menu
got title filename: D:\SteamLibrary\steamapps\common\Rust\temp\c17427ec2c1144d2f72ba09ac0397e26.png
Playing Video D:/SteamLibrary/steamapps/common/Rust/RustClient_Data/StreamingAssets/MenuVideo/attackhelicopter.mp4
client.connect 193.165.142.26:28015
Found 0 server query results, attempting direct connect…
Connecting: 193.165.142.26:28015 (Raknet)
Connecting: 193.165.142.26:28015 (Steamworks)
Disconnected (Disconnected) - returning to main menu
got title filename: D:\SteamLibrary\steamapps\common\Rust\temp\3df83294ec7504109840e1f01159610e.png
Playing Video D:/SteamLibrary/steamapps/common/Rust/RustClient_Data/StreamingAssets/MenuVideo/attackhelicopter.mp4
