Solved Failed to bind port

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Connor Gavitt

New Member
Jul 29, 2019
1,091
-1
0
I have 2 servers running on my VPS 1 vanilla and the other FTB. The survival server works fine on port 8080 (mcmyadmin web port 8081) but the FTB server in a separate folder gets this error just after activating all the mods "2013-07-10 04:46:55 [INFO] Starting Minecraft server on *:25565
2013-07-10 04:46:55 [WARNING] **** FAILED TO BIND TO PORT!
2013-07-10 04:46:55 [WARNING] The exception was: java.net.BindException: Address already in use
2013-07-10 04:46:55 [WARNING] Perhaps a server is already running on that port?"

Before setting up the seconds server this worked fine and all the configs are the same. But when I do "netstat" the port 25565 doesn't even show up.
"Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 37.252.124.207:25566 108-200-185-144.light:52089 ESTABLISHED
tcp 0 224 37.252.124.207:ssh 108-200-185-144.light:51776 ESTABLISHED
tcp 0 0 37.252.124.207:tproxy 108-200-185-144.light:51344 ESTABLISHED
tcp 0 0 37.252.124.207:25566 108-200-185-144.light:52091 ESTABLISHED
tcp 0 0 37.252.124.207:ssh 108-200-185-144.light:51669 ESTABLISHED
tcp 0 0 37.252.124.207:tproxy 108-200-185-144.light:51346 ESTABLISHED
tcp 0 0 37.252.124.207:46344 phonicuk.com:https ESTABLISHED
tcp 38 0 ::ffff:37.252.124.207:33059 ec2-54-243-72-116.com:https CLOSE_WAIT
tcp 38 0 ::ffff:37.252.124.207:58169 ec2-107-20-198-150.co:https CLOSE_WAIT
tcp 71030 0 ::ffff:37.252.124.207:37484 ::ffff:199.27.76.133:https ESTABLISHED
tcp 38 0 ::ffff:37.252.124.207:58170 ec2-107-20-198-150.co:https CLOSE_WAIT
tcp 71030 0 ::ffff:37.252.124.207:37483 ::ffff:199.27.76.133:https ESTABLISHED
tcp 38 0 ::ffff:37.252.124.207:33060 ec2-54-243-72-116.com:https CLOSE_WAIT
How do I get this fixed and running?

-edit- iptables disabled and this still happens
 

cjm721

New Member
Jul 29, 2019
734
0
1
open up system monitor and kill the extra java process. You have a server running in the background.
 

Connor Gavitt

New Member
Jul 29, 2019
1,091
-1
0
I listed the java processes but I can't tell what is wrong and the same thing is still happening. (1526 is the other server and it is working great)

# pgrep -fl java
1266 java
1500 java
1526 /usr/bin/java -Dfile.encoding=utf-8 -client -Xmx2000M -jar minecraft_server.jar nogui
1698 java
1857 java
1991 java
2000 java
2161 java
2189 java
2302 java
2415 /usr/bin/java -Dfile.encoding=utf-8 -Djline.terminal=jline.UnsupportedTerminal -client -Xmx6192M -jar FTB-Beta-A.jar nogui -d yyyy-MM-dd HH:mm:ss -nojline
 

iMontouch

New Member
Jul 29, 2019
147
0
0
Not sure if I got this right, but is it possible that you configured *only* the mcmyadmin port?

Could you go to the 2nd servers "server.properties" file and change the port to 25566 or something else? Maybe this will fix it.
 

Connor Gavitt

New Member
Jul 29, 2019
1,091
-1
0
for the first server I have port 25565, mcmyadmin 25566
for the seconds server the one that works I have it on 8080 and mcmyadmin port 8081
 

Connor Gavitt

New Member
Jul 29, 2019
1,091
-1
0
I started it again and listed the java process,

3252 /usr/bin/java -Dfile.encoding=utf-8 -Djline.terminal=jline.UnsupportedTerminal -client -Xmx6192M -jar FTB-Beta-A.jar nogui -d yyyy-MM-dd HH:mm:ss -nojline
3294 /usr/bin/java -Dfile.encoding=utf-8 -Djline.terminal=jline.UnsupportedTerminal -client -Xmx6192M -jar FTB-Beta-A.jar nogui -d yyyy-MM-dd HH:mm:ss -nojline
but every time I shut one of them down it just starts back up again
 

Connor Gavitt

New Member
Jul 29, 2019
1,091
-1
0
Ok now I got a even greater problem it seems, I changed the port to 25567 and it started great but now people can't connect because there getting id mismatches. So I restarted and now when people try to join they crash. Not the server their clients. Would somehow getting this to work on the 25565 port fix this and what is going on?
 

Connor Gavitt

New Member
Jul 29, 2019
1,091
-1
0
Ok I fixed the port issue I changed it to 25567 then back to 25565 and it works and I should post a new thread for the id mismatch issue.
 

DieselPowered

New Member
Jul 29, 2019
10
0
0
i had about the same issue.

so, i was trying to make a ftb monster server to play on whith my friends and such, it worked fine for a while and it had worked for all my servers to this point, but then it just stopped working for some reason.
either it just says in the console failed to bind to port or when others try to connect it says connection refused: connect.

so i thought i would try to fix the bind to port problem.
i have found the problem, it was that bitTorrent where using the same port as my server adn i thought:
sure lets just look up how to fix that then (btw, if i change the port inside bitTorrent the server fucks up)
but i didnt find anything at all.
so if any1 that reads this knows what i should do plz tell me

thanks !