After today's update, I'm seeing less servers from South America and more from... Australia. :/
Servers are not showing on server list
- 1
- 2
and my servers are now visable :| strange...
Same problem here,I just bought some server from company. And when i start my server in control panel tc admin. My server doesnt show in community list/modded, i've waiting for 1 day but my server still doesnt show.
It's definitely something wrong with how the ingame server list finds servers/how facepunch filters servers. I've experienced this myself, roll the dice, keep moving locations.
Even Rustafied had this problem at one point, but they get help from facepunch quickly of course.
Even Rustafied had this problem at one point, but they get help from facepunch quickly of course.
did you see this commit from FP?
Maybe this will help...
increased server browser timeout limit to 90 secondsbtw i have changed my host and now is much better, but still not all see my servers ;/
This may be an issue with Steamworks and binding to the correct ip address on Linux operating systems.
In this setup you have the following
Dedicated Server ip x.x.x.1
Rust Server #1 ip x.x.x.2 on the Dedicated Server
Rust Server #2 ip x.x.x.3 on the Dedicated Server
What happened on my linux box was that the server browser was picking up the dedicated host's ip address (x.x.x.1) even though I specified the Rust server ip address (x.x.x.2) in the startup script. Supposedly this is some bug in steamworks, i'm not quite sure. This caused none of my servers to show in the server browser as ip addresses were mismatched. This can be tested for by running a freshly installed vanilla server under your dedicated server's ip address and seeing if it shows up in the server browser.
In this setup you have the following
Dedicated Server ip x.x.x.1
Rust Server #1 ip x.x.x.2 on the Dedicated Server
Rust Server #2 ip x.x.x.3 on the Dedicated Server
What happened on my linux box was that the server browser was picking up the dedicated host's ip address (x.x.x.1) even though I specified the Rust server ip address (x.x.x.2) in the startup script. Supposedly this is some bug in steamworks, i'm not quite sure. This caused none of my servers to show in the server browser as ip addresses were mismatched. This can be tested for by running a freshly installed vanilla server under your dedicated server's ip address and seeing if it shows up in the server browser.
FowlkinThis may be an issue with Steamworks and binding to the correct ip address on Linux operating systems.
In this setup you have the following
Dedicated Server ip x.x.x.1
Rust Server #1 ip x.x.x.2 on the Dedicated Server
Rust Server #2 ip x.x.x.3 on the Dedicated Server
What happened on my linux box was that the server browser was picking up the dedicated host's ip address (x.x.x.1) even though I specified the Rust server ip address (x.x.x.2) in the startup script. Supposedly this is some bug in steamworks, i'm not quite sure. This caused none of my servers to show in the server browser as ip addresses were mismatched. This can be tested for by running a freshly installed vanilla server under your dedicated server's ip address and seeing if it shows up in the server browser.
That's a different issue. Servers (including windows) shows correctly in history and favourites tab, not in community/modded. But once location is changed, they appear again.
They did not appear when changed. I did indeed try reinstalling fresh servers under those addresses and installing those servers under differing IP addresses. Completely vanilla installs would not show until specifying networking name spaces. This issue first appeared for me after changing the dedicated machine's OS from OpenVZ 7 to CentOS 7. The big change was loss of virtualization which isolated those ip addresses.
Anyone found any solution?
after excavator update,my server still doesnt show in list community or modded.underllineAnyone found any solution?
I found out that my problem (after the Excavator update) was because I had a low value set under Steam > Settings > In-Game > In-Game server browser: Max pings per minute. Raising the value to the default 5000 fixed it for me.
- 1
- 2