CreateBoundSocket: ::bind couldn't find an open port between 27015 and 27015

[Ghostwish]

Port is open on the router, no extra ShooterGameServer.exes running, etc etc.

What gives, Wildcard?

[Ghostwish]

Booted it up this morning, updated the server, launched. Same issue.

[TomHud™]

usually get that if u already got your server open and u try to boot a fresh version

[Ghostwish]

Originally posted by Tomhud™:

usually get that if u already got your server open and u try to boot a fresh version

Read before ya post.

[TomHud™]

Originally posted by Ghostwish:

Originally posted by Tomhud™:

usually get that if u already got your server open and u try to boot a fresh version

Read before ya post.

i read it and i had that error many times.
Reset your computer.
Infact dont reset solve it on your own - its such a simple one to fix.

check this :

https://steamcommunity.com/app/346110/discussions/0/615086038687363524/

[ZánÐêr]

on your server check to see if something else is using that port. You can do this by opening a cmd prompt and running

Netstat -a -n -o

This will bring up a list of what is using what port. If something else is using that port, either change the Ark server port you use or change what is using that port.

[Ghostwish]

@Tomhud Actually you're still wrong. "no extra ShooterGameServer.exes running".

@Zan Thanks, let me give that a try now.

[Ghostwish]

@ZanDer Curious. It shows 27015 open, and unused, but I could not find 7777 anywhere on the list. Let me do some fiddling and get back.

[ZánÐêr]

you may want to also check your servers firewall ( create a bypass rule for 27015 & 7777 ) or just temporarily turn it off to test.

[Ghostwish]

@Zan Well, tried a number of things, mainly changing the ports that the manager is using to launch the server, but only to limited results. When I change off of port 27015, and move it to another port (which I forwarded through the firewall) I get, instead, 'unable to query server' when attempting to join. Others who joined my server got a mod mismatch error. I'm preforming updates all around, but, given how wonky ARK's error messages are, I'm not holding my breath.

Edit: It's a no go.

[Ghostwish]

Well, I gave it another try this morning after updating, and it's the same issue. I'm giving it up for the ghost at this point. Sorry to anyone else who has this problem in the future.