Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Steam Client: View -> Game Servers -> + (the + is a button to add server by IP).
IP:Port or IP:Queryport like 127.0.0.1:27000
Hitting refresh will make the server show stats with correct port. I think it is Queryport to enter, then it will show up as a server on Port once added - but problem, try both.
Do NOT try enter via Steam, start the game, go to Join, wait for time out, select favorites and Refresh. Now you should see the server and be able to join.
If Server does not show in Steam on either port, I would start with the server firewall.
If Server shows in Steam but not in game, check mods (Start single player game with the right mods, enter world, check all mods work, or do it a few times, looking for any signs of the small bar showing mod loading, then a couple times more after not seeing bar (yes stupid, but I can't find a way to verify the mods are 100% downloaded). Then FTP the mods to the server).
The firewall is removed from the equation because I'm trying to connect to it locally. "open <IP>:<PORT>?<PASSWORD>"
When I add the server as a favorite through steam it *DOES* show the server's name and version correctly.
The linux container has no software/ip tables based firewall - at all. The only firewall in the mix is a FortiGate 140D that has a wide-open rule between the server and internal networks.
The firewall is 100% not the issue.
Just to as a check on things, the in game server list system is known to be unreliable and incapable of comprehensively listing the 50,000+ unofficial servers that can be played.
Go to the battlemetrics website and see if your specific server shows up on their listing system. If it does (and can be connected to) then it just may be the in game system's commonly known issue in this regard. Keep in mind that if you just fired up the server it may not necessarily show up just yet on that site either as it takes a little bit for the site's queries to detect it.
Even though I'm not trying to connect through the net, I have the following forwarded to the internet:
- UDP/TCP 27018
- UDP 7778-7779
For testing purposes I have the firewall wide open between my machine and the container.
And again, the linux container does NOT have iptables/a software firewall.
Nothing on the site, my other servers (7 days for instance) are showing up.
The server has been running for about 16 hours.
Is this how you try to join? A console command? To my knowledge it does not work. Use the described timeout - Favorites - Refresh approach.
*EDIT* Forgot, as far as I know you do need the ports for servers open to Steam for verifications, as seem to have, but also verify you didn't go outside the open range for Port and Queryport.
Due to my lack of knowledge in this area, I ran it through an AI and this is what it came up with:
-----------------------------------------------------------------------------------------------
The provided code appears to be a Bash script for running an ARK: Survival Evolved server. However, there is a small issue with the command that might cause unexpected behavior. The parameters for the ARK server command should be separated by spaces rather than question marks. Here's the corrected version:
#!/bin/bash
sessionname="OtakusCorner"
port="7778"
queryport="27018"
rconport="32330"
serveradminpassword="<someotherpassword>"
serverpassword="<someotherpassword>"
maxplayers="50"
ark "./ShooterGame/Binaries/Linux/ShooterGameServer" "TheIsland?listen?SessionName=$sessionname?MaxPlayers=$maxplayers?QueryPort=$queryport?RCONPort=$rconport?Port=$port?ServerPassword=$serverpassword?ServerAdminPassword=$serveradminpassword" -server -log -servergamelog -ActiveEvent=NewYearEvent
Added were quotes around the path to the ShooterGameServer executable and the parameters passed to it. This is to ensure that the entire path and each parameter are treated as a single argument.
-----------------------------------------------------------------------------------------------
Whether this helps in any capacity or not I do no know but may be worth a try with it or you running it through an ai to check for anomalies yourself.
This is how I'm testing, in no way do I intend to deploy the server this way.
Also adding the server to the server list and going in-game to find the server doesn't work either. I did add the internal address, do I need to add my own public IP and try?
I wanted to use the console command instead of all the favorites crap when first launching a server for friends, but it did not work. Favorites in game was the only way that worked ALWAYS and for EVERYONE. But you MUST do the Favorite-Refresh.
Once it is listed as a Favorite in Steam. You open the game, go to Join. This provides a list or No Results Found (possible after a long timeout). After this has happened, you select Favorites in lower left, then you click the Refresh button. If this doesn't make the server show in the new list. Then maybe see below.
port="7778"
queryport="27018"
It does not seem to be the issue since Steam finds and loads the stats for the server, but I do not use variables and quotes, I forgot what bash to with the quotes, but the ports part of my startup is ..Aberration_P?Port=7778?QueryPort=27018?GameMod..
(ports copied to yours, note they are integers not strings)
I'll try anything at this point. One minor correction for your AI, is that I'm passing all of that to a screen session, I left that off the command by accident - I've modified the original post to reflect this. In a moment I'll give the AI's suggestion a shot.
Steam might do verification stuff based on the public IP, while your router tries route you to the private IP.
This may also impact the server list in game, as well breaking the console command in your specific case. I am afraid I do not have the knowledge of Steams workings to have any real idea on what is the best way here. All servers I run for anyone currently are located at server farms, not locally with anyone.
I also ran the other part above through the AI's diagnostic just to see if it also turned up anything else and it commented on the above like this:
----------------------------------------------------------------------------------------------
The log you provided seems to indicate that the server has started successfully, and there are no critical errors. However, there are a few points worth noting:
SteamSocketsOpenSource errors:
[2024.01.16-01.53.20:522][]SteamSocketsOpenSource: gethostname failed ()
[2024.01.16-01.53.20:522][]gethostbyname failed ()
These errors suggest that there might be an issue with resolving the host name. It could be due to networking or DNS configuration. It may not directly affect the server's functionality, but it's something to be aware of. Check your network and DNS settings to ensure they are configured correctly.
BattlEye Anti-Cheat:
[2024.01.16-01.53.39:060][]Server Initializing with BattlEye Anti-Cheat Protection. If you do not wish to use BattlEye, please launch with -NoBattlEye
[2024.01.16-01.53.39:061][]BattlEye successfully started.
The server is using BattlEye Anti-Cheat protection. If you ever encounter issues related to BattlEye, consider launching the server with the -NoBattlEye option, as suggested in the log.
New Year's Event:
[2024.01.16-01.58.21:312][]Server attempting to run the New Year's event
[2024.01.16-01.58.21:313][]Server is not set to official or running NewYearEvent argument
It appears that the server is attempting to run the New Year's event, but there's a condition check indicating that the server is not set to official or running the NewYearEvent argument. Ensure that your server settings and command line arguments are configured correctly if you intend to run the New Year's event.
Overall, the log looks good, and the server seems to be functioning as expected.
-----------------------------------------------------------------------------------------------