Server names are bugged?
I have a cluster of 12 ark ascended servers. I used the same ports as my old ark evolved servers. That worked fine but the names did not update. After several weeks with no name update I deleted the names and tried to readd the servers but I cant even get them to show up because the website has wrong data for these. I have changed the names and see correct ip addresss linked with ports I have never used. These ports are in the range of my port forwards but are not correct. When a server is added the log and RCON works on the intended port even though the name is a random crapshoot of all my instances.
I have tried adding the servers back by ip and port and some it will take with the wrong names others I get:
"Query Error We were unable to query the server at the given IP and query port."
I doubt its the firewall or port forward because I have ranges specified so if one works in that range they should all work and they were all working before. I also tried dropping the windows firewall to no effect. This appears to be a battlemetrics issue but I am unsure how to get past it. I cant have the names shifting constantly when I am not changing anything on the back end, it sort of renders the site and subscription useless.
Currently I have deleted all my profiles and am waiting per tech support, but, when I search for the names on battlemetrics it is always a wrong port and often one I have never used so not sure how that happens? When I brows in the game the server names are all listed correctly and its not like the names or ports are changing. I can find and join the servers just fine locally and others can both find and join from the internet. I feel like or at least it seems like whatever logic is used to add ipaddress and ports to the battlemetrics database, the port part is supper buggy and needs a fix.
Anyone have any ideas? I am happy to try whatever.
11 Replies
PS Ping never has worked on this site that I can tell and the browser port for this game seems to be the same as the game port and not the steam browser port as one might expect. At least thats the only value RCON setup will accept and the testing appears green on that port
Have you clustered the server ports ontop of each other?
I am unsure what you mean exactly but they are a contiguous run for example
ARK_01 game port 7777-7778 UDP, RCON port TCP/UDP 7779, Steam browser port UDP 27015
ARK_02 game port 7780-7781 UDP, RCON port 7782, Steam browser port UDP 27016
and so on. Hopefuly that helps.
yeah, that can cause issue's,
Your better off leaving gaps between server ports.
For example, Steam query ports for most games actually use 2x ports.
So that could explain why their is mixed names occuring & query failures.
The way i always set my squad servers was
Game 7778 +1 (7779)
Query 27016 +1 (27017)
Rcon 10801
Next server would be + 6 ports
So it would be
Game 7784 +1 (7785)
Query 27022 +1 (27017)
Rcon 10807
This way their was no way of servers cross mixing.
Nice! I will give it go and let you know if that works. I also wondered if forwarding a block of ports would somehow jumble the ports so I changed my forwards for server one and two to just thoes servers and left the rest on the adjusted range. My thinking here was maybe it comes in on 7777 but like 7783 in the same block is the return port or something like that, IDK. I dont reallyt have any reason to think that is the case and it has not made any difference so far. I will update on the port change soon
yeah, there really is no reason to stack servers ontop of each other when you have thousands of ports & you aren't going to be filling 1 IP with hundreds of servers.
For me it was convienient when setting up and checking ports but if it causes issues, thats a reason to break my convention
yep,
i just use to open blocks on my firewall for ports & let my DDOS protection deal with any issues (i had a Always-Active Protection though so everything was scanned coming into my server)
So id open like 7770 - 8700
27010-28000
10800-11000
That way i didn't need to worry about just kicking another server up without having to re-do all firewalls again.
ok, so I queued my first and last server to launch as these are pretty far apart and on separate port forwards. Server 01 was found with the correct ports assigned and adoped but with the wrong name. The I searched for the second server (#12) and it was found with the correct RCON port but the game port was 01's game port +1 instead of the actual port which is very far away.... but it added the server. It now shows the correct names but the #12 game port is wrong and the correct port errors out. I am looking at the startup ports and that is not correct. No idea??? Maybe I need to block the +1 ports?
Ok it looks like an Ark Ascended issue. I am looking closer now but it seems the server is just defaulting to game port 7777 and whatever number is higher if that is taken. I am trying a different launch script to see if I can change that but unless RCON is somehow overriding the game port I think its ark that is bugged. I verified the wrong game port is listening with : netstat -aon but still not sure why it wont take the ports assigned at startup. No matter why, it looks like whatever instance loads first will get port 7777 unless that is already taken
Hmm, thats a goood bug.
Definately try assigning them on start up parameters
I did do the startup assignment and the gameuser ini file as well but it seems to ignore both
It was originaly assigned through the startup but....looks like it wont take.