rust-server: Disconnected: connection attempt failed

Describe the bug I am using all defaults a part from port mappings and I cannot connect to my server even though the server is online and appearing on my Steam server list

To Reproduce

this is my port mapping:


{
	ContainerPort: 28015,
	HostPort: 27015,
},
{
	ContainerPort: 28015,
	HostPort: 27001,
	Protocol: "udp",
},
{
	ContainerPort: 28016,
	HostPort: 27002,
},
{
	ContainerPort: 8080,
	HostPort:      27003,
},

Also I cannot connect to RCON getting 1006 error with password docker as default

Expected behavior Should connect

Environment (please complete the following information):

Host OS: Amazon Linux 2 4.14.181-140.257.amzn2.x86_64
Docker version 19.03.6-ce, build 369ce74

Additional context The whole system is running on ECS

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 19 (2 by maintainers)

Most upvoted comments

@danielsand ok, thanks I will check this out again. BTW I have found this as well:

https://shockbyte.com/billing/knowledgebase/138/Rust-Server-Not-Showing-in-CommunityorModded-List.html#:~:text=Update your Rust server - If,the server will not appear.&text=Clear the Steam cache - To," and "config" folder.

Shorten the server name - The server display name (hostname) can cause the server to not show in the Rust server list if the name is too long or contains special characters. Try shortening the server name, or resetting it entirely and ensuring you only use letters and spaces in the name.

In my case it had special chars, but I did not test it yet

MatteoInfi on Jul 5, 2020

@danielsand I have tried the same system in localhost and it does the same. So I exclude it is a problem coming from ECS

I have noticed that after 12/24 hours it actually works, I am not sure why though, maybe it takes 12/24 for steam to get the address from non standard ports?

@MatteoInfi

possbile

my problem is gone now - but i have also discovered a DNS issues on my side which prevent my server from getting listed and conncted to.

i have seen in facepunch’s changelog something interesting

Change List 230 Thursday, 4 June 2020 " Added pairing with the companion app (make sure app.port isn’t firewalled!)"

so its working for me now - but i dont know what exactly was the problem.

danielsand on Jul 5, 2020