@Tails1 I completely disabled my firewall and it didn't work. And I'm using bitdefender.
@Necromancer I got my ipv4 and I put it in my port forwarding and the port was still closed. I also tried to put the same ip I used at my port forwarding in server properties but the port was still closed.
and at ip place in server properties type you ip which u put while portforwarding that's all it will not give problem anymore
The server-ip field in server.properties is only there so multihomed systems can restrict binding. It is not required that you put something there otherwise, and in fact, is better that you do not. Too many times people put the wrong thing there and it hoses it up and the server won't start.
Hi, I've tried everything and my ports won't open.
1. I've already port forwarded.
2. I've disabled my antivirus.
3. I made a exception in windows firewall for tcp and udp for inbound and outbound.
Can someone please help me?
Post screenshots of your portforwarding.
Sorry for taking so long, sure
Did you make sure that local IP is static and didn't change?
nope, I didn't make a static IP. And I didn't change
Well then the router might've assigned a new local IP to your PC, recheck your portforwarding.
Nope, my router didn't assign a new local ip to my PC.
Did you open the port in the firewall?
No need to censor that IP by the way, it's a private network IP. Totally useless to anyone not on your local network.
Yup I opened the port in the firewall
Temporarily completely disable your firewall and try again. And which anti-virus are we talking about here?
What ip you put in port forwarding dont put the online ip
Process for ip:
1) Open cmd
2) in cmd type ipconfig
3) there will be a line called ipv4 there will be the ip
4) put the ip at the place where website ask for ip
that's all
if i am right then this process will work and if you get this again problem then see that you have put both tcp and udp
and if u see both then use both or it will give error that's all you have to do after then also it give error
check server properties both port in server properties should be 25565 and at ip place in server properties type
you ip which u put while portforwarding that's all it will not give problem anymore
@Tails1 I completely disabled my firewall and it didn't work. And I'm using bitdefender.
@Necromancer I got my ipv4 and I put it in my port forwarding and the port was still closed. I also tried to put the same ip I used at my port forwarding in server properties but the port was still closed.
You don't need UDP unless you run query.
That's standard, but not a requirement.
The server-ip field in server.properties is only there so multihomed systems can restrict binding. It is not required that you put something there otherwise, and in fact, is better that you do not. Too many times people put the wrong thing there and it hoses it up and the server won't start.